Fossil SCM
Expanded the discussion of the difference between "fossil ui" and "fossil server" in www/server.wiki.
Commit
67e30333d14e0932170e4a2a344157de6033ac1670f1ca6764516ffafff6a4ce
Parent
3406f0eb2da2779…
1 file changed
+11
-6
+11
-6
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -45,22 +45,27 @@ | ||
| 45 | 45 | <li><b>fossil server</b> <i>REPOSITORY</i> |
| 46 | 46 | <li><b>fossil ui</b> <i>REPOSITORY</i> |
| 47 | 47 | </ul> |
| 48 | 48 | |
| 49 | 49 | The <i>REPOSITORY</i> argument is either the name of the repository file, or |
| 50 | -a directory containing many repositories. | |
| 50 | +a directory containing many repositories named <tt>*.fossil</tt>. | |
| 51 | 51 | Both of these commands start a Fossil server, usually on TCP port 8080, though |
| 52 | 52 | a higher numbered port might also be used if 8080 is already occupied. You can |
| 53 | 53 | access these using URLs of the form <b>http://localhost:8080/</b>, or if |
| 54 | 54 | <i>REPOSITORY</i> is a directory, URLs of the form |
| 55 | 55 | <b>http://localhost:8080/</b><i>repo</i><b>/</b> where <i>repo</i> is the base |
| 56 | 56 | name of the repository file without the ".fossil" suffix. |
| 57 | -The difference between "ui" and "server" is that "ui" will | |
| 58 | -also start a web browser and point it | |
| 59 | -to the URL mentioned above, and the "ui" command binds to | |
| 60 | -the loopback IP address (127.0.0.1) only so that the "ui" command cannot be | |
| 61 | -used to serve content to a different machine. | |
| 57 | + | |
| 58 | +There are several key differences between "ui" and "server": | |
| 59 | + | |
| 60 | +<ul> | |
| 61 | + <li>"ui" always binds the server to the loopback IP address | |
| 62 | + (127.0.0.1) so that it cannot serve to other machines. | |
| 63 | + <li>anyone who visits this URL is treated as the all-powerful Setup | |
| 64 | + user, which is why the first difference exists. | |
| 65 | + <li>"ui" launches a local web browser pointed at this URL. | |
| 66 | +</ul> | |
| 62 | 67 | |
| 63 | 68 | If one of the commands above is run from within an open checkout, |
| 64 | 69 | then the <i>REPOSITORY</i> argument can be omitted and the checkout is used as |
| 65 | 70 | the repository. |
| 66 | 71 | |
| 67 | 72 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -45,22 +45,27 @@ | |
| 45 | <li><b>fossil server</b> <i>REPOSITORY</i> |
| 46 | <li><b>fossil ui</b> <i>REPOSITORY</i> |
| 47 | </ul> |
| 48 | |
| 49 | The <i>REPOSITORY</i> argument is either the name of the repository file, or |
| 50 | a directory containing many repositories. |
| 51 | Both of these commands start a Fossil server, usually on TCP port 8080, though |
| 52 | a higher numbered port might also be used if 8080 is already occupied. You can |
| 53 | access these using URLs of the form <b>http://localhost:8080/</b>, or if |
| 54 | <i>REPOSITORY</i> is a directory, URLs of the form |
| 55 | <b>http://localhost:8080/</b><i>repo</i><b>/</b> where <i>repo</i> is the base |
| 56 | name of the repository file without the ".fossil" suffix. |
| 57 | The difference between "ui" and "server" is that "ui" will |
| 58 | also start a web browser and point it |
| 59 | to the URL mentioned above, and the "ui" command binds to |
| 60 | the loopback IP address (127.0.0.1) only so that the "ui" command cannot be |
| 61 | used to serve content to a different machine. |
| 62 | |
| 63 | If one of the commands above is run from within an open checkout, |
| 64 | then the <i>REPOSITORY</i> argument can be omitted and the checkout is used as |
| 65 | the repository. |
| 66 | |
| 67 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -45,22 +45,27 @@ | |
| 45 | <li><b>fossil server</b> <i>REPOSITORY</i> |
| 46 | <li><b>fossil ui</b> <i>REPOSITORY</i> |
| 47 | </ul> |
| 48 | |
| 49 | The <i>REPOSITORY</i> argument is either the name of the repository file, or |
| 50 | a directory containing many repositories named <tt>*.fossil</tt>. |
| 51 | Both of these commands start a Fossil server, usually on TCP port 8080, though |
| 52 | a higher numbered port might also be used if 8080 is already occupied. You can |
| 53 | access these using URLs of the form <b>http://localhost:8080/</b>, or if |
| 54 | <i>REPOSITORY</i> is a directory, URLs of the form |
| 55 | <b>http://localhost:8080/</b><i>repo</i><b>/</b> where <i>repo</i> is the base |
| 56 | name of the repository file without the ".fossil" suffix. |
| 57 | |
| 58 | There are several key differences between "ui" and "server": |
| 59 | |
| 60 | <ul> |
| 61 | <li>"ui" always binds the server to the loopback IP address |
| 62 | (127.0.0.1) so that it cannot serve to other machines. |
| 63 | <li>anyone who visits this URL is treated as the all-powerful Setup |
| 64 | user, which is why the first difference exists. |
| 65 | <li>"ui" launches a local web browser pointed at this URL. |
| 66 | </ul> |
| 67 | |
| 68 | If one of the commands above is run from within an open checkout, |
| 69 | then the <i>REPOSITORY</i> argument can be omitted and the checkout is used as |
| 70 | the repository. |
| 71 | |
| 72 |