Fossil SCM
Corrections to the multi-repository server documentation. Ticket [72c7d223d5258].
Commit
b951baa5c90cc54f090ae441e7b5a5a660c198ef
Parent
0aee050f320050b…
1 file changed
+8
-3
+8
-3
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -15,11 +15,13 @@ | ||
| 15 | 15 | <p> |
| 16 | 16 | Both of these commands start a Fossil server on port 8080 on the local machine, |
| 17 | 17 | which can be accessed with the URL: <tt>http://localhost:8080/</tt> using any |
| 18 | 18 | handy web browser. The difference between the two commands is that "ui", in |
| 19 | 19 | addition to starting the Fossil server, also starts a web browser and points it |
| 20 | -to the URL mentioned above. | |
| 20 | +to the URL mentioned above. On the other hand, the "ui" command binds to | |
| 21 | +the loopback IP address only (127.0.0.1) so that the "ui" command cannot be | |
| 22 | +used to serve content to a different machine. | |
| 21 | 23 | </p> |
| 22 | 24 | <p> |
| 23 | 25 | NOTES: |
| 24 | 26 | <ol> |
| 25 | 27 | <li>The option "--port NNN" will start the server on port "NNN" instead of 8080. |
| @@ -70,19 +72,22 @@ | ||
| 70 | 72 | </p> |
| 71 | 73 | </blockquote> |
| 72 | 74 | |
| 73 | 75 | <h3>Serving multiple repositories with one script</h3><blockquote> |
| 74 | 76 | <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'): | |
| 77 | +This scenario is almost identical to the previous one. However, here we will assume you have multiple repositories, in one directory. | |
| 78 | +(Call the directory 'fossils'). All repositories served, in this case, must | |
| 79 | +use the ".fossil" filename suffix. | |
| 80 | +As before, create a script (again, 'repo'): | |
| 76 | 81 | <blockquote><tt> |
| 77 | 82 | #!/path-to/fossil<br> |
| 78 | 83 | directory: /path-to-repo/fossils<br> |
| 79 | 84 | notfound: http://url-to-go-to-if-repo-not-found/ |
| 80 | 85 | </tt></blockquote> |
| 81 | 86 | </p> |
| 82 | 87 | <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. | |
| 88 | +Once deployed, a URL like: <tt>http://mydomain.org/cgi-bin/repo/XYZ</tt> will serve up the repository "fossils/XYX.fossil" (if it exists). This makes serving multiple projects on one server pretty painless. | |
| 84 | 89 | </p> |
| 85 | 90 | </blockquote> |
| 86 | 91 | |
| 87 | 92 | <h2>Securing a repository with SSL</h2><blockquote> |
| 88 | 93 | <p> |
| 89 | 94 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -15,11 +15,13 @@ | |
| 15 | <p> |
| 16 | Both of these commands start a Fossil server on port 8080 on the local machine, |
| 17 | which can be accessed with the URL: <tt>http://localhost:8080/</tt> using any |
| 18 | handy web browser. The difference between the two commands is that "ui", in |
| 19 | addition to starting the Fossil server, also starts a web browser and points it |
| 20 | to the URL mentioned above. |
| 21 | </p> |
| 22 | <p> |
| 23 | NOTES: |
| 24 | <ol> |
| 25 | <li>The option "--port NNN" will start the server on port "NNN" instead of 8080. |
| @@ -70,19 +72,22 @@ | |
| 70 | </p> |
| 71 | </blockquote> |
| 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 | </p> |
| 85 | </blockquote> |
| 86 | |
| 87 | <h2>Securing a repository with SSL</h2><blockquote> |
| 88 | <p> |
| 89 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -15,11 +15,13 @@ | |
| 15 | <p> |
| 16 | Both of these commands start a Fossil server on port 8080 on the local machine, |
| 17 | which can be accessed with the URL: <tt>http://localhost:8080/</tt> using any |
| 18 | handy web browser. The difference between the two commands is that "ui", in |
| 19 | addition to starting the Fossil server, also starts a web browser and points it |
| 20 | to the URL mentioned above. On the other hand, the "ui" command binds to |
| 21 | the loopback IP address only (127.0.0.1) so that the "ui" command cannot be |
| 22 | used to serve content to a different machine. |
| 23 | </p> |
| 24 | <p> |
| 25 | NOTES: |
| 26 | <ol> |
| 27 | <li>The option "--port NNN" will start the server on port "NNN" instead of 8080. |
| @@ -70,19 +72,22 @@ | |
| 72 | </p> |
| 73 | </blockquote> |
| 74 | |
| 75 | <h3>Serving multiple repositories with one script</h3><blockquote> |
| 76 | <p> |
| 77 | This scenario is almost identical to the previous one. However, here we will assume you have multiple repositories, in one directory. |
| 78 | (Call the directory 'fossils'). All repositories served, in this case, must |
| 79 | use the ".fossil" filename suffix. |
| 80 | As before, create a script (again, 'repo'): |
| 81 | <blockquote><tt> |
| 82 | #!/path-to/fossil<br> |
| 83 | directory: /path-to-repo/fossils<br> |
| 84 | notfound: http://url-to-go-to-if-repo-not-found/ |
| 85 | </tt></blockquote> |
| 86 | </p> |
| 87 | <p> |
| 88 | Once deployed, a URL like: <tt>http://mydomain.org/cgi-bin/repo/XYZ</tt> will serve up the repository "fossils/XYX.fossil" (if it exists). This makes serving multiple projects on one server pretty painless. |
| 89 | </p> |
| 90 | </blockquote> |
| 91 | |
| 92 | <h2>Securing a repository with SSL</h2><blockquote> |
| 93 | <p> |
| 94 |