Fossil SCM
Small improvements to IIS + CGI doc
Commit
f7c839c1c6adc2b36471024df08837b7977757b5de687801265fc768a0759a36
Parent
9098ebba2d32218…
1 file changed
+12
-10
+12
-10
| --- www/server/windows/cgi.md | ||
| +++ www/server/windows/cgi.md | ||
| @@ -20,33 +20,35 @@ | ||
| 20 | 20 | Fossil service. |
| 21 | 21 | |
| 22 | 22 | You lose a lot of that benefit on Windows: |
| 23 | 23 | |
| 24 | 24 | 1. It only matters to start with on servers that are highly RAM |
| 25 | - constrained. (Rougly ≤ 128 MiB.) Our configuration steps below | |
| 25 | + constrained. (Roughly ≤ 128 MiB.) Our configuration steps below | |
| 26 | 26 | assume you’re using the Windows and IIS GUIs, which have RAM |
| 27 | 27 | requirements well in excess of this, making Fossil’s resource |
| 28 | - requirements a drop in the bucket next to them. On the test VM I | |
| 29 | - used to prepare these instructions, the Windows Server Manager kept | |
| 30 | - running the system out of RAM and crashing on the 1 GiB Azure | |
| 31 | - B1s VM I started out using. I had to upgrade the VM’s RAM to | |
| 32 | - 2 GiB just to get useful work done! | |
| 28 | + requirements a drop in the bucket next to them. On the [Azure | |
| 29 | + B1s][b1s] virtual machine I used to prepare these instructions, the | |
| 30 | + Windows Server Manager GUI kept filling the VM’s 1 GiB of RAM | |
| 31 | + during feature installation and crashing. I had to upgrade the VM’s | |
| 32 | + RAM to 2 GiB just to get useful work done! | |
| 33 | 33 | |
| 34 | 34 | 2. Process creation on Windows is [much more expensive][cp] than on the |
| 35 | 35 | other OSes Fossil runs on, so the benefits of firing up a Fossil |
| 36 | 36 | executable to process each HTTP request are partially swamped by the |
| 37 | 37 | overhead of doing so. |
| 38 | 38 | |
| 39 | 39 | Therefore, unless you’re willing to replace all of the GUI configuration |
| 40 | 40 | steps below with command line equivalents, or shut the GUI down entirely |
| 41 | -after configuring IIS, CGI is much less a compelling option on Windows. | |
| 41 | +after configuring IIS, CGI is a much less compelling option on Windows. | |
| 42 | 42 | |
| 43 | 43 | **WARNING:** The following tutorial appears to fail with the current |
| 44 | -(2019-08-17) version of Fossil, apparently due to an inability of Fossil | |
| 45 | -to detect that it’s being run in CGI mode. | |
| 44 | +(2019-08-17) version of Fossil, [apparently][fbug] due to an inability | |
| 45 | +of Fossil to detect that it’s being run in CGI mode. | |
| 46 | 46 | |
| 47 | -[cp]: https://stackoverflow.com/a/48244/142454 | |
| 47 | +[b1s]: https://azure.microsoft.com/en-us/blog/introducing-b-series-our-new-burstable-vm-size/ | |
| 48 | +[cp]: https://stackoverflow.com/a/48244/142454 | |
| 49 | +[fbug]: https://fossil-scm.org/forum/forumpost/de18dc32c0 | |
| 48 | 50 | |
| 49 | 51 | |
| 50 | 52 | ## Setup |
| 51 | 53 | |
| 52 | 54 | 1. Install the Fossil executable to `c:\inetpub\wwwroot\bin` on the web |
| 53 | 55 |
| --- www/server/windows/cgi.md | |
| +++ www/server/windows/cgi.md | |
| @@ -20,33 +20,35 @@ | |
| 20 | Fossil service. |
| 21 | |
| 22 | You lose a lot of that benefit on Windows: |
| 23 | |
| 24 | 1. It only matters to start with on servers that are highly RAM |
| 25 | constrained. (Rougly ≤ 128 MiB.) Our configuration steps below |
| 26 | assume you’re using the Windows and IIS GUIs, which have RAM |
| 27 | requirements well in excess of this, making Fossil’s resource |
| 28 | requirements a drop in the bucket next to them. On the test VM I |
| 29 | used to prepare these instructions, the Windows Server Manager kept |
| 30 | running the system out of RAM and crashing on the 1 GiB Azure |
| 31 | B1s VM I started out using. I had to upgrade the VM’s RAM to |
| 32 | 2 GiB just to get useful work done! |
| 33 | |
| 34 | 2. Process creation on Windows is [much more expensive][cp] than on the |
| 35 | other OSes Fossil runs on, so the benefits of firing up a Fossil |
| 36 | executable to process each HTTP request are partially swamped by the |
| 37 | overhead of doing so. |
| 38 | |
| 39 | Therefore, unless you’re willing to replace all of the GUI configuration |
| 40 | steps below with command line equivalents, or shut the GUI down entirely |
| 41 | after configuring IIS, CGI is much less a compelling option on Windows. |
| 42 | |
| 43 | **WARNING:** The following tutorial appears to fail with the current |
| 44 | (2019-08-17) version of Fossil, apparently due to an inability of Fossil |
| 45 | to detect that it’s being run in CGI mode. |
| 46 | |
| 47 | [cp]: https://stackoverflow.com/a/48244/142454 |
| 48 | |
| 49 | |
| 50 | ## Setup |
| 51 | |
| 52 | 1. Install the Fossil executable to `c:\inetpub\wwwroot\bin` on the web |
| 53 |
| --- www/server/windows/cgi.md | |
| +++ www/server/windows/cgi.md | |
| @@ -20,33 +20,35 @@ | |
| 20 | Fossil service. |
| 21 | |
| 22 | You lose a lot of that benefit on Windows: |
| 23 | |
| 24 | 1. It only matters to start with on servers that are highly RAM |
| 25 | constrained. (Roughly ≤ 128 MiB.) Our configuration steps below |
| 26 | assume you’re using the Windows and IIS GUIs, which have RAM |
| 27 | requirements well in excess of this, making Fossil’s resource |
| 28 | requirements a drop in the bucket next to them. On the [Azure |
| 29 | B1s][b1s] virtual machine I used to prepare these instructions, the |
| 30 | Windows Server Manager GUI kept filling the VM’s 1 GiB of RAM |
| 31 | during feature installation and crashing. I had to upgrade the VM’s |
| 32 | RAM to 2 GiB just to get useful work done! |
| 33 | |
| 34 | 2. Process creation on Windows is [much more expensive][cp] than on the |
| 35 | other OSes Fossil runs on, so the benefits of firing up a Fossil |
| 36 | executable to process each HTTP request are partially swamped by the |
| 37 | overhead of doing so. |
| 38 | |
| 39 | Therefore, unless you’re willing to replace all of the GUI configuration |
| 40 | steps below with command line equivalents, or shut the GUI down entirely |
| 41 | after configuring IIS, CGI is a much less compelling option on Windows. |
| 42 | |
| 43 | **WARNING:** The following tutorial appears to fail with the current |
| 44 | (2019-08-17) version of Fossil, [apparently][fbug] due to an inability |
| 45 | of Fossil to detect that it’s being run in CGI mode. |
| 46 | |
| 47 | [b1s]: https://azure.microsoft.com/en-us/blog/introducing-b-series-our-new-burstable-vm-size/ |
| 48 | [cp]: https://stackoverflow.com/a/48244/142454 |
| 49 | [fbug]: https://fossil-scm.org/forum/forumpost/de18dc32c0 |
| 50 | |
| 51 | |
| 52 | ## Setup |
| 53 | |
| 54 | 1. Install the Fossil executable to `c:\inetpub\wwwroot\bin` on the web |
| 55 |