Fossil SCM
removed USER stuff. Reorganized. i would have SWORN that i checked this in yesterday.
Commit
ab5ab46206457266274563fd0ca5cf9ef0cc5388
Parent
69650f2963ebabb…
1 file changed
+30
-28
+30
-28
| --- www/newrepo.wiki | ||
| +++ www/newrepo.wiki | ||
| @@ -15,21 +15,41 @@ | ||
| 15 | 15 | admin-user: stephan (no password set yet!) |
| 16 | 16 | baseline: 84e81a150535f031722f815d59c0c5e96ab7f122 |
| 17 | 17 | </verbatim> |
| 18 | 18 | |
| 19 | 19 | The numbers it spits out are unimportant (they are version |
| 20 | -numbers). It gets the admin-user name from your $USER environment | |
| 21 | -variable, so you can override this by setting that variable before | |
| 22 | -calling fossil, like so: | |
| 23 | - | |
| 24 | -<verbatim> | |
| 25 | -stephan@ludo:~/fossil$ USER=myAlias fossil new demo.fossil | |
| 26 | -</verbatim> | |
| 20 | +numbers). | |
| 27 | 21 | |
| 28 | 22 | Now we have an empty repository file named <tt>demo.fossil</tt>. |
| 29 | 23 | There is nothing magical about the extension <tt>.fossil</tt> - it's |
| 30 | 24 | just a convention. You may name your files anything you like. |
| 25 | + | |
| 26 | +The first thing we normally want to do is to run fossil as a local server so | |
| 27 | +that you can configure the access rights to the repo: | |
| 28 | + | |
| 29 | +<verbatim> | |
| 30 | +stephan@ludo:~/fossil$ fossil ui demo.fossil | |
| 31 | +</verbatim> | |
| 32 | + | |
| 33 | +The <tt>ui</tt> command starts up a server (with an optional <tt>-port | |
| 34 | +NUMBER</tt> argument) and launches a web browser pointing at the | |
| 35 | +fossil server. From there it takes just a few moments to configure the | |
| 36 | +repo. Most importantly, go to the Setup menu, then the Users link, and | |
| 37 | +set your account name and password, and grant your account all access | |
| 38 | +priviledges. (I also like to grant Clone access to the anonymous user, | |
| 39 | +but that's personal preference.) | |
| 40 | + | |
| 41 | +Once you are done, kill the fossil server (with Ctrl-C or equivalent) | |
| 42 | +and close the browser window. | |
| 43 | + | |
| 44 | +<blockquote> | |
| 45 | +Tip: it is not strictly required to configure a repository | |
| 46 | +this way, but if you are going to share a repo over the net then it | |
| 47 | +is highly recommended. If you are only going to work with the repo | |
| 48 | +locally, you can skip the configuration step and do it later if | |
| 49 | +you decide you want to share your repo. | |
| 50 | +</blockquote> | |
| 31 | 51 | |
| 32 | 52 | The next thing we need to do is <em>open</em> the repository. To do so |
| 33 | 53 | we create a working directory and then <tt>cd</tt> to it: |
| 34 | 54 | |
| 35 | 55 | <verbatim> |
| @@ -93,29 +113,11 @@ | ||
| 93 | 113 | Making your repository available over the web is trivial to do. We |
| 94 | 114 | assume you have some web space where you can store your fossil file |
| 95 | 115 | and run a CGI script. If not, then this option is not for you. If |
| 96 | 116 | you do, then here's how... |
| 97 | 117 | |
| 98 | -The first thing you need to do is run fossil as a local server so | |
| 99 | -that you can configure the access rights to your repo: | |
| 100 | - | |
| 101 | -<verbatim> | |
| 102 | -stephan@ludo:~/fossil/demo$ fossil ui | |
| 103 | -</verbatim> | |
| 104 | - | |
| 105 | -The <tt>ui</tt> command starts up a server (with an optional <tt>-port | |
| 106 | -NUMBER</tt> argument) and launches a web browser pointing at the | |
| 107 | -fossil server. From there it takes just a few moments to configure the | |
| 108 | -repo. Most importantly, go to the Setup menu, then the Users link, and | |
| 109 | -set your password and grant your account all access priviledges. (I | |
| 110 | -also like to grant Clone access to the anonymous user, but that's | |
| 111 | -personal preference.) | |
| 112 | - | |
| 113 | -Once you are done, kill the fossil server (with Ctrl-C or equivalent) | |
| 114 | -and close the browser window. | |
| 115 | - | |
| 116 | -Now copy the fossil repository file to your web server (it doesn't | |
| 118 | +Copy copy the fossil repository file to your web server (it doesn't | |
| 117 | 119 | matter where, really). |
| 118 | 120 | |
| 119 | 121 | In your <tt>cgi-bin</tt> (or equivalent) directory, create a file |
| 120 | 122 | which looks like this: |
| 121 | 123 | |
| @@ -136,16 +138,16 @@ | ||
| 136 | 138 | |
| 137 | 139 | To check out a copy of your remote repository, use the |
| 138 | 140 | <em>clone</em> command: |
| 139 | 141 | |
| 140 | 142 | <verbatim> |
| 141 | -stephan@ludo:~/fossil fossil clone \ | |
| 143 | +stephan@ludo:~/fossil$ fossil clone \ | |
| 142 | 144 | http://MyAccountName:[email protected]/cgi-bin/myrepo.cgi |
| 143 | 145 | </verbatim> |
| 144 | 146 | |
| 145 | 147 | Note that you should pass your fossil login name and password (as set |
| 146 | -in the local server mode) during the clone - that ensures that fossil | |
| 148 | +via local server mode) during the clone - that ensures that fossil | |
| 147 | 149 | won't ask you for it on each commit! |
| 148 | 150 | |
| 149 | 151 | A clone is a local copy of a remote repository, and can be opened just |
| 150 | 152 | like a local one (as shown above). It is treated identically to your |
| 151 | 153 | local repository, with one very important difference. When you commit |
| 152 | 154 |
| --- www/newrepo.wiki | |
| +++ www/newrepo.wiki | |
| @@ -15,21 +15,41 @@ | |
| 15 | admin-user: stephan (no password set yet!) |
| 16 | baseline: 84e81a150535f031722f815d59c0c5e96ab7f122 |
| 17 | </verbatim> |
| 18 | |
| 19 | The numbers it spits out are unimportant (they are version |
| 20 | numbers). It gets the admin-user name from your $USER environment |
| 21 | variable, so you can override this by setting that variable before |
| 22 | calling fossil, like so: |
| 23 | |
| 24 | <verbatim> |
| 25 | stephan@ludo:~/fossil$ USER=myAlias fossil new demo.fossil |
| 26 | </verbatim> |
| 27 | |
| 28 | Now we have an empty repository file named <tt>demo.fossil</tt>. |
| 29 | There is nothing magical about the extension <tt>.fossil</tt> - it's |
| 30 | just a convention. You may name your files anything you like. |
| 31 | |
| 32 | The next thing we need to do is <em>open</em> the repository. To do so |
| 33 | we create a working directory and then <tt>cd</tt> to it: |
| 34 | |
| 35 | <verbatim> |
| @@ -93,29 +113,11 @@ | |
| 93 | Making your repository available over the web is trivial to do. We |
| 94 | assume you have some web space where you can store your fossil file |
| 95 | and run a CGI script. If not, then this option is not for you. If |
| 96 | you do, then here's how... |
| 97 | |
| 98 | The first thing you need to do is run fossil as a local server so |
| 99 | that you can configure the access rights to your repo: |
| 100 | |
| 101 | <verbatim> |
| 102 | stephan@ludo:~/fossil/demo$ fossil ui |
| 103 | </verbatim> |
| 104 | |
| 105 | The <tt>ui</tt> command starts up a server (with an optional <tt>-port |
| 106 | NUMBER</tt> argument) and launches a web browser pointing at the |
| 107 | fossil server. From there it takes just a few moments to configure the |
| 108 | repo. Most importantly, go to the Setup menu, then the Users link, and |
| 109 | set your password and grant your account all access priviledges. (I |
| 110 | also like to grant Clone access to the anonymous user, but that's |
| 111 | personal preference.) |
| 112 | |
| 113 | Once you are done, kill the fossil server (with Ctrl-C or equivalent) |
| 114 | and close the browser window. |
| 115 | |
| 116 | Now copy the fossil repository file to your web server (it doesn't |
| 117 | matter where, really). |
| 118 | |
| 119 | In your <tt>cgi-bin</tt> (or equivalent) directory, create a file |
| 120 | which looks like this: |
| 121 | |
| @@ -136,16 +138,16 @@ | |
| 136 | |
| 137 | To check out a copy of your remote repository, use the |
| 138 | <em>clone</em> command: |
| 139 | |
| 140 | <verbatim> |
| 141 | stephan@ludo:~/fossil fossil clone \ |
| 142 | http://MyAccountName:[email protected]/cgi-bin/myrepo.cgi |
| 143 | </verbatim> |
| 144 | |
| 145 | Note that you should pass your fossil login name and password (as set |
| 146 | in the local server mode) during the clone - that ensures that fossil |
| 147 | won't ask you for it on each commit! |
| 148 | |
| 149 | A clone is a local copy of a remote repository, and can be opened just |
| 150 | like a local one (as shown above). It is treated identically to your |
| 151 | local repository, with one very important difference. When you commit |
| 152 |
| --- www/newrepo.wiki | |
| +++ www/newrepo.wiki | |
| @@ -15,21 +15,41 @@ | |
| 15 | admin-user: stephan (no password set yet!) |
| 16 | baseline: 84e81a150535f031722f815d59c0c5e96ab7f122 |
| 17 | </verbatim> |
| 18 | |
| 19 | The numbers it spits out are unimportant (they are version |
| 20 | numbers). |
| 21 | |
| 22 | Now we have an empty repository file named <tt>demo.fossil</tt>. |
| 23 | There is nothing magical about the extension <tt>.fossil</tt> - it's |
| 24 | just a convention. You may name your files anything you like. |
| 25 | |
| 26 | The first thing we normally want to do is to run fossil as a local server so |
| 27 | that you can configure the access rights to the repo: |
| 28 | |
| 29 | <verbatim> |
| 30 | stephan@ludo:~/fossil$ fossil ui demo.fossil |
| 31 | </verbatim> |
| 32 | |
| 33 | The <tt>ui</tt> command starts up a server (with an optional <tt>-port |
| 34 | NUMBER</tt> argument) and launches a web browser pointing at the |
| 35 | fossil server. From there it takes just a few moments to configure the |
| 36 | repo. Most importantly, go to the Setup menu, then the Users link, and |
| 37 | set your account name and password, and grant your account all access |
| 38 | priviledges. (I also like to grant Clone access to the anonymous user, |
| 39 | but that's personal preference.) |
| 40 | |
| 41 | Once you are done, kill the fossil server (with Ctrl-C or equivalent) |
| 42 | and close the browser window. |
| 43 | |
| 44 | <blockquote> |
| 45 | Tip: it is not strictly required to configure a repository |
| 46 | this way, but if you are going to share a repo over the net then it |
| 47 | is highly recommended. If you are only going to work with the repo |
| 48 | locally, you can skip the configuration step and do it later if |
| 49 | you decide you want to share your repo. |
| 50 | </blockquote> |
| 51 | |
| 52 | The next thing we need to do is <em>open</em> the repository. To do so |
| 53 | we create a working directory and then <tt>cd</tt> to it: |
| 54 | |
| 55 | <verbatim> |
| @@ -93,29 +113,11 @@ | |
| 113 | Making your repository available over the web is trivial to do. We |
| 114 | assume you have some web space where you can store your fossil file |
| 115 | and run a CGI script. If not, then this option is not for you. If |
| 116 | you do, then here's how... |
| 117 | |
| 118 | Copy copy the fossil repository file to your web server (it doesn't |
| 119 | matter where, really). |
| 120 | |
| 121 | In your <tt>cgi-bin</tt> (or equivalent) directory, create a file |
| 122 | which looks like this: |
| 123 | |
| @@ -136,16 +138,16 @@ | |
| 138 | |
| 139 | To check out a copy of your remote repository, use the |
| 140 | <em>clone</em> command: |
| 141 | |
| 142 | <verbatim> |
| 143 | stephan@ludo:~/fossil$ fossil clone \ |
| 144 | http://MyAccountName:[email protected]/cgi-bin/myrepo.cgi |
| 145 | </verbatim> |
| 146 | |
| 147 | Note that you should pass your fossil login name and password (as set |
| 148 | via local server mode) during the clone - that ensures that fossil |
| 149 | won't ask you for it on each commit! |
| 150 | |
| 151 | A clone is a local copy of a remote repository, and can be opened just |
| 152 | like a local one (as shown above). It is treated identically to your |
| 153 | local repository, with one very important difference. When you commit |
| 154 |