Fossil SCM
Removed manual indents of code blocks in webui doc
Commit
9437518451e562134689e63da8f2a6baaf2ba8a5c3f5edd2d4967d0869625a93
Parent
006b61b0e5d4301…
1 file changed
+4
-4
+4
-4
| --- www/webui.wiki | ||
| +++ www/webui.wiki | ||
| @@ -153,12 +153,12 @@ | ||
| 153 | 153 | run Fossil as CGI, just put the |
| 154 | 154 | <b>sample-project.fossil</b> file in a directory where CGI scripts |
| 155 | 155 | have both read and write permission on the file and the directory that |
| 156 | 156 | contains the file, then add a CGI script that looks something like this: |
| 157 | 157 | |
| 158 | -<verbatim> #!/usr/local/bin/fossil | |
| 159 | - repository: /home/www/sample-project.fossil</verbatim> | |
| 158 | +<verbatim>#!/usr/local/bin/fossil | |
| 159 | +repository: /home/www/sample-project.fossil</verbatim> | |
| 160 | 160 | |
| 161 | 161 | Adjust the script above so that the paths are correct for your system, |
| 162 | 162 | of course, and also make sure the Fossil binary is installed on the server. |
| 163 | 163 | But that is <u>all</u> you have to do. You now have everything you need to host |
| 164 | 164 | a distributed software development project in less than five minutes using a |
| @@ -171,11 +171,11 @@ | ||
| 171 | 171 | server machine? |
| 172 | 172 | Not a problem. The Fossil interface can also be launched via inetd or |
| 173 | 173 | xinetd. An inetd configuration line sufficient to launch the Fossil |
| 174 | 174 | web interface looks like this: |
| 175 | 175 | |
| 176 | -<verbatim> 80 stream tcp nowait.1000 root /usr/local/bin/fossil \ | |
| 177 | - /usr/local/bin/fossil http /home/www/sample-project.fossil</verbatim> | |
| 176 | +<verbatim>80 stream tcp nowait.1000 root /usr/local/bin/fossil \ | |
| 177 | +/usr/local/bin/fossil http /home/www/sample-project.fossil</verbatim> | |
| 178 | 178 | |
| 179 | 179 | As always, you'll want to adjust the pathnames to whatever is appropriate |
| 180 | 180 | for your system. The xinetd setup uses a different syntax but follows |
| 181 | 181 | the same idea. |
| 182 | 182 |
| --- www/webui.wiki | |
| +++ www/webui.wiki | |
| @@ -153,12 +153,12 @@ | |
| 153 | run Fossil as CGI, just put the |
| 154 | <b>sample-project.fossil</b> file in a directory where CGI scripts |
| 155 | have both read and write permission on the file and the directory that |
| 156 | contains the file, then add a CGI script that looks something like this: |
| 157 | |
| 158 | <verbatim> #!/usr/local/bin/fossil |
| 159 | repository: /home/www/sample-project.fossil</verbatim> |
| 160 | |
| 161 | Adjust the script above so that the paths are correct for your system, |
| 162 | of course, and also make sure the Fossil binary is installed on the server. |
| 163 | But that is <u>all</u> you have to do. You now have everything you need to host |
| 164 | a distributed software development project in less than five minutes using a |
| @@ -171,11 +171,11 @@ | |
| 171 | server machine? |
| 172 | Not a problem. The Fossil interface can also be launched via inetd or |
| 173 | xinetd. An inetd configuration line sufficient to launch the Fossil |
| 174 | web interface looks like this: |
| 175 | |
| 176 | <verbatim> 80 stream tcp nowait.1000 root /usr/local/bin/fossil \ |
| 177 | /usr/local/bin/fossil http /home/www/sample-project.fossil</verbatim> |
| 178 | |
| 179 | As always, you'll want to adjust the pathnames to whatever is appropriate |
| 180 | for your system. The xinetd setup uses a different syntax but follows |
| 181 | the same idea. |
| 182 |
| --- www/webui.wiki | |
| +++ www/webui.wiki | |
| @@ -153,12 +153,12 @@ | |
| 153 | run Fossil as CGI, just put the |
| 154 | <b>sample-project.fossil</b> file in a directory where CGI scripts |
| 155 | have both read and write permission on the file and the directory that |
| 156 | contains the file, then add a CGI script that looks something like this: |
| 157 | |
| 158 | <verbatim>#!/usr/local/bin/fossil |
| 159 | repository: /home/www/sample-project.fossil</verbatim> |
| 160 | |
| 161 | Adjust the script above so that the paths are correct for your system, |
| 162 | of course, and also make sure the Fossil binary is installed on the server. |
| 163 | But that is <u>all</u> you have to do. You now have everything you need to host |
| 164 | a distributed software development project in less than five minutes using a |
| @@ -171,11 +171,11 @@ | |
| 171 | server machine? |
| 172 | Not a problem. The Fossil interface can also be launched via inetd or |
| 173 | xinetd. An inetd configuration line sufficient to launch the Fossil |
| 174 | web interface looks like this: |
| 175 | |
| 176 | <verbatim>80 stream tcp nowait.1000 root /usr/local/bin/fossil \ |
| 177 | /usr/local/bin/fossil http /home/www/sample-project.fossil</verbatim> |
| 178 | |
| 179 | As always, you'll want to adjust the pathnames to whatever is appropriate |
| 180 | for your system. The xinetd setup uses a different syntax but follows |
| 181 | the same idea. |
| 182 |