Fossil SCM
corrected formatting of example cgi scripts in server documentation
Commit
ea667800169d9aa962adae39eda3113d0dff1c45
Parent
e3fb8dc36cf9354…
1 file changed
+3
-3
+3
-3
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -56,11 +56,11 @@ | ||
| 56 | 56 | |
| 57 | 57 | <h3>One script per repository</h3><blockquote> |
| 58 | 58 | <p> |
| 59 | 59 | Create a script (let's call it 'repo') in your CGI directory which has content like this: |
| 60 | 60 | <blockquote><tt> |
| 61 | -#!/path-to/fossil | |
| 61 | +#!/path-to/fossil<br> | |
| 62 | 62 | repository: /path-to-repo/repository |
| 63 | 63 | </tt></blockquote> |
| 64 | 64 | </p> |
| 65 | 65 | <p> |
| 66 | 66 | It may be necessary to set permissions properly, or to modify an ".htaccess" file or other server-specific things like that. Consult with your server provider if you need that sort of assistance. |
| @@ -72,12 +72,12 @@ | ||
| 72 | 72 | |
| 73 | 73 | <h3>Serving multiple repositories with one script</h3><blockquote> |
| 74 | 74 | <p> |
| 75 | 75 | This scenario is almost identical to the previous one. However, here we will assume you have multiple repositories, in one directory (call it 'fossils'). So as before, create a script (again, 'repo'): |
| 76 | 76 | <blockquote><tt> |
| 77 | -#!/path-to/fossil | |
| 78 | -directory: /path-to-repo/fossils | |
| 77 | +#!/path-to/fossil<br> | |
| 78 | +directory: /path-to-repo/fossils<br> | |
| 79 | 79 | notfound: http://url-to-go-to-if-repo-not-found/ |
| 80 | 80 | </tt></blockquote> |
| 81 | 81 | </p> |
| 82 | 82 | <p> |
| 83 | 83 | Once deployed, a URL like: <tt>http://mydomain.org/cgi-bin/repo/XYZ</tt> will serve up the repository "fossils/XYX" (if it exists). This makes serving multiple projects on one server pretty painless. |
| 84 | 84 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -56,11 +56,11 @@ | |
| 56 | |
| 57 | <h3>One script per repository</h3><blockquote> |
| 58 | <p> |
| 59 | Create a script (let's call it 'repo') in your CGI directory which has content like this: |
| 60 | <blockquote><tt> |
| 61 | #!/path-to/fossil |
| 62 | repository: /path-to-repo/repository |
| 63 | </tt></blockquote> |
| 64 | </p> |
| 65 | <p> |
| 66 | It may be necessary to set permissions properly, or to modify an ".htaccess" file or other server-specific things like that. Consult with your server provider if you need that sort of assistance. |
| @@ -72,12 +72,12 @@ | |
| 72 | |
| 73 | <h3>Serving multiple repositories with one script</h3><blockquote> |
| 74 | <p> |
| 75 | This scenario is almost identical to the previous one. However, here we will assume you have multiple repositories, in one directory (call it 'fossils'). So as before, create a script (again, 'repo'): |
| 76 | <blockquote><tt> |
| 77 | #!/path-to/fossil |
| 78 | directory: /path-to-repo/fossils |
| 79 | notfound: http://url-to-go-to-if-repo-not-found/ |
| 80 | </tt></blockquote> |
| 81 | </p> |
| 82 | <p> |
| 83 | Once deployed, a URL like: <tt>http://mydomain.org/cgi-bin/repo/XYZ</tt> will serve up the repository "fossils/XYX" (if it exists). This makes serving multiple projects on one server pretty painless. |
| 84 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -56,11 +56,11 @@ | |
| 56 | |
| 57 | <h3>One script per repository</h3><blockquote> |
| 58 | <p> |
| 59 | Create a script (let's call it 'repo') in your CGI directory which has content like this: |
| 60 | <blockquote><tt> |
| 61 | #!/path-to/fossil<br> |
| 62 | repository: /path-to-repo/repository |
| 63 | </tt></blockquote> |
| 64 | </p> |
| 65 | <p> |
| 66 | It may be necessary to set permissions properly, or to modify an ".htaccess" file or other server-specific things like that. Consult with your server provider if you need that sort of assistance. |
| @@ -72,12 +72,12 @@ | |
| 72 | |
| 73 | <h3>Serving multiple repositories with one script</h3><blockquote> |
| 74 | <p> |
| 75 | This scenario is almost identical to the previous one. However, here we will assume you have multiple repositories, in one directory (call it 'fossils'). So as before, create a script (again, 'repo'): |
| 76 | <blockquote><tt> |
| 77 | #!/path-to/fossil<br> |
| 78 | directory: /path-to-repo/fossils<br> |
| 79 | notfound: http://url-to-go-to-if-repo-not-found/ |
| 80 | </tt></blockquote> |
| 81 | </p> |
| 82 | <p> |
| 83 | Once deployed, a URL like: <tt>http://mydomain.org/cgi-bin/repo/XYZ</tt> will serve up the repository "fossils/XYX" (if it exists). This makes serving multiple projects on one server pretty painless. |
| 84 |