Fossil SCM

Updated Windows Service documentation to reflect new 64bit binaries for Fossil 2.10 for Windows.

ckennedy 2019-10-08 00:57 trunk
Commit cb13b611005b9f0a3be031c934a0cea7fc684f575a831f523e9196777b854162
--- www/server/windows/service.md
+++ www/server/windows/service.md
@@ -9,36 +9,37 @@
99
2. You have PowerShell 5.1 or above installed.
1010
1111
## Place Fossil on Server
1212
1313
However you obtained your copy of Fossil, it is recommended that you follow
14
-Windows conventions and place it within `\Program Files (x86)\FossilSCM`. Since
15
-Fossil is a 32bit binary, this is the proper location for the executable. This
14
+Windows conventions and place it within `\Program Files\FossilSCM`. Since
15
+Fossil 2.10 is a 64bit binary, this is the proper location for the executable. This
1616
way Fossil is in an expected location and you will have minimal issues with
1717
Windows interfering in your ability to run Fossil as a service. You will need
1818
Administrative rights to place fossil at the recommended location. You do NOT
1919
need to add this location to the path, though you may do so if you wish.
2020
2121
## Make Fossil a Windows Service
2222
2323
Luckily the hard work to use Fossil as a Windows Service has been done by the
2424
Fossil team. We simply have to install it with the proper command line options.
25
-As of Fossil 2.9 the built in `fossil winsrv` command is failing, so an
26
-alternative service install using PowerShell is documented here. The below
27
-should all be entered as a single line in an Administrative PowerShell console.
25
+Fossil on Windows has a command `fossil winsrv` to allow installing Fossil as a
26
+service on Windows, but the options are limited, so an alternative service
27
+install using PowerShell is documented here. The below should all be entered
28
+as a single line in an Administrative PowerShell console.
2829
2930
```PowerShell
30
-New-Service -Name fossil -DisplayName fossil -BinaryPathName '"C:\Program Files (x86)\FossilSCM\fossil.exe"
31
+New-Service -Name fossil -DisplayName fossil -BinaryPathName '"C:\Program Files\FossilSCM\fossil.exe"
3132
server --port 8080 --repolist "D:/Path/to/Repos"' -StartupType Automatic
3233
```
3334
34
-Please note the use of forward slashes in the paths passed to Fossil. Windows
35
-will accept either back slashes or forward slashes in path names, but Fossil has
36
-a preference for forward slashes. The use of `--repolist` will make this a
37
-multiple repository server. If you want to serve only a single repository,
38
-then leave off the `--repolist` parameter and provide the full path to the
39
-proper repository file. Other options are listed in the
35
+Please note the use of forward slashes in the repolist path passed to Fossil.
36
+Windows will accept either back slashes or forward slashes in path names, but
37
+Fossil has a preference for forward slashes. The use of `--repolist` will make
38
+this a multiple repository server. If you want to serve only a single
39
+repository, then leave off the `--repolist` parameter and provide the full path
40
+to the proper repository file. Other options are listed in the
4041
[fossil server](/help?cmd=server) documentation.
4142
4243
The service will be installed by default to use the Local Service account.
4344
Since Fossil only needs access to local files, this is fine and causes no
4445
issues. The service will not be running once installed. You will need to start
4546
--- www/server/windows/service.md
+++ www/server/windows/service.md
@@ -9,36 +9,37 @@
9 2. You have PowerShell 5.1 or above installed.
10
11 ## Place Fossil on Server
12
13 However you obtained your copy of Fossil, it is recommended that you follow
14 Windows conventions and place it within `\Program Files (x86)\FossilSCM`. Since
15 Fossil is a 32bit binary, this is the proper location for the executable. This
16 way Fossil is in an expected location and you will have minimal issues with
17 Windows interfering in your ability to run Fossil as a service. You will need
18 Administrative rights to place fossil at the recommended location. You do NOT
19 need to add this location to the path, though you may do so if you wish.
20
21 ## Make Fossil a Windows Service
22
23 Luckily the hard work to use Fossil as a Windows Service has been done by the
24 Fossil team. We simply have to install it with the proper command line options.
25 As of Fossil 2.9 the built in `fossil winsrv` command is failing, so an
26 alternative service install using PowerShell is documented here. The below
27 should all be entered as a single line in an Administrative PowerShell console.
 
28
29 ```PowerShell
30 New-Service -Name fossil -DisplayName fossil -BinaryPathName '"C:\Program Files (x86)\FossilSCM\fossil.exe"
31 server --port 8080 --repolist "D:/Path/to/Repos"' -StartupType Automatic
32 ```
33
34 Please note the use of forward slashes in the paths passed to Fossil. Windows
35 will accept either back slashes or forward slashes in path names, but Fossil has
36 a preference for forward slashes. The use of `--repolist` will make this a
37 multiple repository server. If you want to serve only a single repository,
38 then leave off the `--repolist` parameter and provide the full path to the
39 proper repository file. Other options are listed in the
40 [fossil server](/help?cmd=server) documentation.
41
42 The service will be installed by default to use the Local Service account.
43 Since Fossil only needs access to local files, this is fine and causes no
44 issues. The service will not be running once installed. You will need to start
45
--- www/server/windows/service.md
+++ www/server/windows/service.md
@@ -9,36 +9,37 @@
9 2. You have PowerShell 5.1 or above installed.
10
11 ## Place Fossil on Server
12
13 However you obtained your copy of Fossil, it is recommended that you follow
14 Windows conventions and place it within `\Program Files\FossilSCM`. Since
15 Fossil 2.10 is a 64bit binary, this is the proper location for the executable. This
16 way Fossil is in an expected location and you will have minimal issues with
17 Windows interfering in your ability to run Fossil as a service. You will need
18 Administrative rights to place fossil at the recommended location. You do NOT
19 need to add this location to the path, though you may do so if you wish.
20
21 ## Make Fossil a Windows Service
22
23 Luckily the hard work to use Fossil as a Windows Service has been done by the
24 Fossil team. We simply have to install it with the proper command line options.
25 Fossil on Windows has a command `fossil winsrv` to allow installing Fossil as a
26 service on Windows, but the options are limited, so an alternative service
27 install using PowerShell is documented here. The below should all be entered
28 as a single line in an Administrative PowerShell console.
29
30 ```PowerShell
31 New-Service -Name fossil -DisplayName fossil -BinaryPathName '"C:\Program Files\FossilSCM\fossil.exe"
32 server --port 8080 --repolist "D:/Path/to/Repos"' -StartupType Automatic
33 ```
34
35 Please note the use of forward slashes in the repolist path passed to Fossil.
36 Windows will accept either back slashes or forward slashes in path names, but
37 Fossil has a preference for forward slashes. The use of `--repolist` will make
38 this a multiple repository server. If you want to serve only a single
39 repository, then leave off the `--repolist` parameter and provide the full path
40 to the proper repository file. Other options are listed in the
41 [fossil server](/help?cmd=server) documentation.
42
43 The service will be installed by default to use the Local Service account.
44 Since Fossil only needs access to local files, this is fine and causes no
45 issues. The service will not be running once installed. You will need to start
46
--- www/server/windows/stunnel.md
+++ www/server/windows/stunnel.md
@@ -24,11 +24,11 @@
2424
Following most of [Fossil as a Windows Service](./service.md), you will need
2525
to change the command to install the Fossil Service to configure it properly for
2626
use with stunnel as an https proxy. Run the following instead:
2727
2828
```PowerShell
29
-New-Service -Name fossil-secure -DisplayName fossil-secure -BinaryPathName '"C:\Program Files (x86)\FossilSCM\fossil.exe"
29
+New-Service -Name fossil-secure -DisplayName fossil-secure -BinaryPathName '"C:\Program Files\FossilSCM\fossil.exe"
3030
server --localhost --port 9000 --https --repolist "D:/Path/to/Repos"' -StartupType Automatic
3131
3232
```
3333
3434
The use of `--localhost` means Fossil will only listen for traffic on the local
3535
--- www/server/windows/stunnel.md
+++ www/server/windows/stunnel.md
@@ -24,11 +24,11 @@
24 Following most of [Fossil as a Windows Service](./service.md), you will need
25 to change the command to install the Fossil Service to configure it properly for
26 use with stunnel as an https proxy. Run the following instead:
27
28 ```PowerShell
29 New-Service -Name fossil-secure -DisplayName fossil-secure -BinaryPathName '"C:\Program Files (x86)\FossilSCM\fossil.exe"
30 server --localhost --port 9000 --https --repolist "D:/Path/to/Repos"' -StartupType Automatic
31
32 ```
33
34 The use of `--localhost` means Fossil will only listen for traffic on the local
35
--- www/server/windows/stunnel.md
+++ www/server/windows/stunnel.md
@@ -24,11 +24,11 @@
24 Following most of [Fossil as a Windows Service](./service.md), you will need
25 to change the command to install the Fossil Service to configure it properly for
26 use with stunnel as an https proxy. Run the following instead:
27
28 ```PowerShell
29 New-Service -Name fossil-secure -DisplayName fossil-secure -BinaryPathName '"C:\Program Files\FossilSCM\fossil.exe"
30 server --localhost --port 9000 --https --repolist "D:/Path/to/Repos"' -StartupType Automatic
31
32 ```
33
34 The use of `--localhost` means Fossil will only listen for traffic on the local
35

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button