Fossil SCM
Small tweaks to the new "Serving as a Standalone Server on Windows" article.
Commit
3995a3c7ae8f362d985884044a830285490de6d35ebc9fbf03a572151a5a9184
Parent
9d4a478241c5511…
1 file changed
+13
-9
+13
-9
| --- www/server/windows/none.md | ||
| +++ www/server/windows/none.md | ||
| @@ -5,25 +5,26 @@ | ||
| 5 | 5 | |
| 6 | 6 | ...but only while `fossil.exe` is actually running, which is the source |
| 7 | 7 | of much trouble on Windows. This problem has two halves: |
| 8 | 8 | |
| 9 | 9 | |
| 10 | -## No App Startup without Desktop | |
| 10 | +## No App Startup Without Desktop | |
| 11 | 11 | |
| 12 | 12 | The easy methods for starting a program in Windows at system start all |
| 13 | -require an interactive desktop. There is no way to start an arbitrary | |
| 13 | +require an interactive desktop. There is no *easy* way to start an arbitrary | |
| 14 | 14 | program on Windows at boot before anyone has logged in. In Unix |
| 15 | -terms, Windows has no simple equivalent to the `/etc/rc.local` file. | |
| 15 | +terms, Windows has no simple equivalent to [the `/etc/rc.local` file][rcl]. | |
| 16 | 16 | |
| 17 | 17 | You can partially get around the first problem by setting your `fossil |
| 18 | 18 | server` call up as one of the user’s interactive startup items. Windows |
| 19 | 19 | 10 has its own [idiosyncratic way of doing this][si10], and in older |
| 20 | 20 | systems you have [several alternatives to this][si7]. Regardless of the |
| 21 | 21 | actual mechanism, these will cause the Fossil standalone HTTP server to |
| 22 | 22 | start on an *interactive desktop login* only. While you’re sitting at |
| 23 | 23 | the Windows login screen, the Fossil server is *down*. |
| 24 | 24 | |
| 25 | +[rcl]: http://nixdoc.net/man-pages/FreeBSD/man8/rc.local.8.html | |
| 25 | 26 | [si10]: https://www.tenforums.com/tutorials/2944-add-delete-enable-disable-startup-items-windows-10-a.html |
| 26 | 27 | [si7]: https://www.wikihow.com/Change-Startup-Programs-in-Windows-7 |
| 27 | 28 | |
| 28 | 29 | |
| 29 | 30 | |
| @@ -31,12 +32,12 @@ | ||
| 31 | 32 | |
| 32 | 33 | Windows also lacks a direct equivalent of the Bourne shell’s “`&`” control operator to |
| 33 | 34 | run a program in the background, which you can give in Unix’s `rc.local` |
| 34 | 35 | file, which is just a normal Bourne shell script. |
| 35 | 36 | |
| 36 | -I don’t mean “background” in the sense of “has no user interface,” I | |
| 37 | -mean in the sense “not attached to any user’s login session.” When the | |
| 37 | +By “background,” I mean | |
| 38 | +“not attached to any interactive user’s login session.” When the | |
| 38 | 39 | `rc.local` script exits in Unix, any program it backgrounded *stays |
| 39 | 40 | running*. There is no simple and direct equivalent to this mechanism in |
| 40 | 41 | Windows. |
| 41 | 42 | |
| 42 | 43 | If you set `fossil server` to run on interactive login, as above, it |
| @@ -49,17 +50,20 @@ | ||
| 49 | 50 | machine interactively. |
| 50 | 51 | |
| 51 | 52 | |
| 52 | 53 | ## Better Solutions |
| 53 | 54 | |
| 54 | -I can only recommend setting `fossil server` up on Windows this way when | |
| 55 | +Because of these problems, we only recommend setting `fossil server` up | |
| 56 | +on Windows this way when | |
| 55 | 57 | you’re a solo developer or you work in a small office where everyone |
| 56 | 58 | arrives more or less at the same time each day, and everyone goes home |
| 57 | 59 | about the same time each day, so that one user can keep the Fossil |
| 58 | 60 | server up through the working day. |
| 59 | 61 | |
| 60 | -If your needs go at all beyond this, you want proper “server” behavior, | |
| 61 | -in which case I strongly recommend that you [register Fossil as a | |
| 62 | -Windows service](./service.md) instead, then possibly put it behind [an | |
| 62 | +If your needs go at all beyond this, you should expect proper “server” | |
| 63 | +behavior, which you can get on Windows by [registering Fossil as a | |
| 64 | +Windows service](./service.md), which solves the interactive startup and | |
| 65 | +shutdown problems above, at a bit of complexity over the Startup Items | |
| 66 | +method. You may also want to consider putting that service behind [an | |
| 63 | 67 | IIS front-end proxy](./iis.md) to add additional web serving features. |
| 64 | 68 | |
| 65 | 69 | *[Return to the top-level Fossil server article.](../)* |
| 66 | 70 |
| --- www/server/windows/none.md | |
| +++ www/server/windows/none.md | |
| @@ -5,25 +5,26 @@ | |
| 5 | |
| 6 | ...but only while `fossil.exe` is actually running, which is the source |
| 7 | of much trouble on Windows. This problem has two halves: |
| 8 | |
| 9 | |
| 10 | ## No App Startup without Desktop |
| 11 | |
| 12 | The easy methods for starting a program in Windows at system start all |
| 13 | require an interactive desktop. There is no way to start an arbitrary |
| 14 | program on Windows at boot before anyone has logged in. In Unix |
| 15 | terms, Windows has no simple equivalent to the `/etc/rc.local` file. |
| 16 | |
| 17 | You can partially get around the first problem by setting your `fossil |
| 18 | server` call up as one of the user’s interactive startup items. Windows |
| 19 | 10 has its own [idiosyncratic way of doing this][si10], and in older |
| 20 | systems you have [several alternatives to this][si7]. Regardless of the |
| 21 | actual mechanism, these will cause the Fossil standalone HTTP server to |
| 22 | start on an *interactive desktop login* only. While you’re sitting at |
| 23 | the Windows login screen, the Fossil server is *down*. |
| 24 | |
| 25 | [si10]: https://www.tenforums.com/tutorials/2944-add-delete-enable-disable-startup-items-windows-10-a.html |
| 26 | [si7]: https://www.wikihow.com/Change-Startup-Programs-in-Windows-7 |
| 27 | |
| 28 | |
| 29 | |
| @@ -31,12 +32,12 @@ | |
| 31 | |
| 32 | Windows also lacks a direct equivalent of the Bourne shell’s “`&`” control operator to |
| 33 | run a program in the background, which you can give in Unix’s `rc.local` |
| 34 | file, which is just a normal Bourne shell script. |
| 35 | |
| 36 | I don’t mean “background” in the sense of “has no user interface,” I |
| 37 | mean in the sense “not attached to any user’s login session.” When the |
| 38 | `rc.local` script exits in Unix, any program it backgrounded *stays |
| 39 | running*. There is no simple and direct equivalent to this mechanism in |
| 40 | Windows. |
| 41 | |
| 42 | If you set `fossil server` to run on interactive login, as above, it |
| @@ -49,17 +50,20 @@ | |
| 49 | machine interactively. |
| 50 | |
| 51 | |
| 52 | ## Better Solutions |
| 53 | |
| 54 | I can only recommend setting `fossil server` up on Windows this way when |
| 55 | you’re a solo developer or you work in a small office where everyone |
| 56 | arrives more or less at the same time each day, and everyone goes home |
| 57 | about the same time each day, so that one user can keep the Fossil |
| 58 | server up through the working day. |
| 59 | |
| 60 | If your needs go at all beyond this, you want proper “server” behavior, |
| 61 | in which case I strongly recommend that you [register Fossil as a |
| 62 | Windows service](./service.md) instead, then possibly put it behind [an |
| 63 | IIS front-end proxy](./iis.md) to add additional web serving features. |
| 64 | |
| 65 | *[Return to the top-level Fossil server article.](../)* |
| 66 |
| --- www/server/windows/none.md | |
| +++ www/server/windows/none.md | |
| @@ -5,25 +5,26 @@ | |
| 5 | |
| 6 | ...but only while `fossil.exe` is actually running, which is the source |
| 7 | of much trouble on Windows. This problem has two halves: |
| 8 | |
| 9 | |
| 10 | ## No App Startup Without Desktop |
| 11 | |
| 12 | The easy methods for starting a program in Windows at system start all |
| 13 | require an interactive desktop. There is no *easy* way to start an arbitrary |
| 14 | program on Windows at boot before anyone has logged in. In Unix |
| 15 | terms, Windows has no simple equivalent to [the `/etc/rc.local` file][rcl]. |
| 16 | |
| 17 | You can partially get around the first problem by setting your `fossil |
| 18 | server` call up as one of the user’s interactive startup items. Windows |
| 19 | 10 has its own [idiosyncratic way of doing this][si10], and in older |
| 20 | systems you have [several alternatives to this][si7]. Regardless of the |
| 21 | actual mechanism, these will cause the Fossil standalone HTTP server to |
| 22 | start on an *interactive desktop login* only. While you’re sitting at |
| 23 | the Windows login screen, the Fossil server is *down*. |
| 24 | |
| 25 | [rcl]: http://nixdoc.net/man-pages/FreeBSD/man8/rc.local.8.html |
| 26 | [si10]: https://www.tenforums.com/tutorials/2944-add-delete-enable-disable-startup-items-windows-10-a.html |
| 27 | [si7]: https://www.wikihow.com/Change-Startup-Programs-in-Windows-7 |
| 28 | |
| 29 | |
| 30 | |
| @@ -31,12 +32,12 @@ | |
| 32 | |
| 33 | Windows also lacks a direct equivalent of the Bourne shell’s “`&`” control operator to |
| 34 | run a program in the background, which you can give in Unix’s `rc.local` |
| 35 | file, which is just a normal Bourne shell script. |
| 36 | |
| 37 | By “background,” I mean |
| 38 | “not attached to any interactive user’s login session.” When the |
| 39 | `rc.local` script exits in Unix, any program it backgrounded *stays |
| 40 | running*. There is no simple and direct equivalent to this mechanism in |
| 41 | Windows. |
| 42 | |
| 43 | If you set `fossil server` to run on interactive login, as above, it |
| @@ -49,17 +50,20 @@ | |
| 50 | machine interactively. |
| 51 | |
| 52 | |
| 53 | ## Better Solutions |
| 54 | |
| 55 | Because of these problems, we only recommend setting `fossil server` up |
| 56 | on Windows this way when |
| 57 | you’re a solo developer or you work in a small office where everyone |
| 58 | arrives more or less at the same time each day, and everyone goes home |
| 59 | about the same time each day, so that one user can keep the Fossil |
| 60 | server up through the working day. |
| 61 | |
| 62 | If your needs go at all beyond this, you should expect proper “server” |
| 63 | behavior, which you can get on Windows by [registering Fossil as a |
| 64 | Windows service](./service.md), which solves the interactive startup and |
| 65 | shutdown problems above, at a bit of complexity over the Startup Items |
| 66 | method. You may also want to consider putting that service behind [an |
| 67 | IIS front-end proxy](./iis.md) to add additional web serving features. |
| 68 | |
| 69 | *[Return to the top-level Fossil server article.](../)* |
| 70 |