Fossil SCM

www/newrepo.wiki: remove user@machine references tin to reduce the noise level. Minor content touchups.

stephan 2024-02-04 10:06 trunk
Commit dc0e0543569ce26a53b5602292cc0404a84aeebe097dc1513459c83a00b723ab
Parent 221cf52bf516560…
1 file changed +22 -24
~ www/newrepo.wiki
M www/newrepo.wiki
+22 -24
--- www/newrepo.wiki
+++ www/newrepo.wiki
@@ -7,11 +7,11 @@
77
 sharing it over the web.
88
99
 The first thing we need to do is create a fossil repository file:
1010
1111
 <verbatim>
12
-stephan@ludo:~/fossil$ fossil new demo.fossil
12
+$ fossil new demo.fossil
1313
 project-id: 9d8ccff5671796ee04e60af6932aa7788f0a990a
1414
 server-id: 145fe7d71e3b513ac37ac283979d73e12ca04bfe
1515
 admin-user: stephan (initial password is ******)
1616
 </verbatim>
1717
@@ -24,11 +24,11 @@
2424
2525
 The first thing we normally want to do is to run fossil as a local server so
2626
 that you can configure the access rights to the repo:
2727
2828
 <verbatim>
29
-stephan@ludo:~/fossil$ fossil ui demo.fossil
29
+$ fossil ui demo.fossil
3030
 </verbatim>
3131
3232
 The <tt>ui</tt> command starts up a server (with an optional <tt>-port
3333
 NUMBER</tt> argument) and launches a web browser pointing at the
3434
 fossil server. From there it takes just a few moments to configure the
@@ -50,14 +50,13 @@
5050
5151
 The next thing we need to do is <em>open</em> the repository. To do so
5252
 we create a working directory and then <tt>cd</tt> to it:
5353
5454
 <verbatim>
55
-stephan@ludo:~/fossil$ mkdir demo
56
-stephan@ludo:~/fossil$ cd demo
57
-stephan@ludo:~/fossil/demo$ fossil open ../demo.fossil
58
-stephan@ludo:~/fossil/demo$
55
+$ mkdir demo
56
+$ cd demo
57
+$ fossil open ../demo.fossil
5958
 </verbatim>
6059
6160
 That creates a file called <tt>_FOSSIL_</tt> in the current
6261
 directory, and this file contains all kinds of fossil-related
6362
 information about your local repository. You can ignore it
@@ -67,36 +66,36 @@
6766
 The next thing we need to do is add files to our repository. As it
6867
 happens, we have a few C source files lying around, which we'll
6968
 simply copy into our working directory.
7069
7170
 <verbatim>
72
-stephan@ludo:~/fossil/demo$ cp ../csnip/*.{c,h} .
73
-stephan@ludo:~/fossil/demo$ ls
74
-clob.c clob.h clobz.c _FOSSIL_ mkdep.c test-clob.c
71
+$ cp ../csnip/*.{c,h} .
72
+$ ls
73
+clob.c clob.h clobz.c mkdep.c test-clob.c
7574
 tokenize_path.c tokenize_path.h vappendf.c vappendf.h
7675
 </verbatim>
7776
7877
 Fossil doesn't know about those files yet. Telling fossil about
7978
 a new file is a two-step process. First we <em>add</em> the file
8079
 to the repository, then we <em>commit</em> the file. This is a familiar
8180
 process for anyone who's worked with SCM systems before:
8281
8382
 <verbatim>
84
-stephan@ludo:~/fossil/demo$ fossil add *.{c,h}
85
-stephan@ludo:~/fossil/demo$ fossil commit -m "egg"
83
+$ fossil add *.{c,h}
84
+$ fossil commit -m "egg"
8685
 New_Version: d1296b4a08b9f8b943bb6c73698e51eed23f8f91
8786
 </verbatim>
8887
8988
 We now have a working repository! The file <tt>demo.fossil</tt>
9089
 is the central storage, and we can share it amongst an arbitrary
9190
 number of trees. As a silly example:
9291
9392
 <verbatim>
94
-stephan@ludo:~/fossil/demo$ cd ~/fossil
95
-stephan@ludo:~/fossil$ mkdir demo2
96
-stephan@ludo:~/fossil$ cd demo2
97
-stephan@ludo:~/fossil/demo2$ fossil open ../demo.fossil
93
+$ cd ~/fossil
94
+$ mkdir demo2
95
+$ cd demo2
96
+$ fossil open ../demo.fossil
9897
 ADD clob.c
9998
 ADD clob.h
10099
 ADD clobz.c
101100
 ADD mkdep.c
102101
 ADD test-clob.c
@@ -112,12 +111,12 @@
112111
 Making your repository available over the web is trivial to do. We
113112
 assume you have some web space where you can store your fossil file
114113
 and run a CGI script. If not, then this option is not for you. If
115114
 you do, then here's how...
116115
117
-Copy the fossil repository file to your web server (it doesn't
118
-matter where, really).
116
+Copy the fossil repository file to your web server (it doesn't matter
117
+where, really, but it "should" be unreachable by web browser traffic).
119118
120119
 In your <tt>cgi-bin</tt> (or equivalent) directory, create a file
121120
 which looks like this:
122121
123122
 <verbatim>
@@ -126,28 +125,27 @@
126125
 </verbatim>
127126
128127
 Make that script executable, and you're all ready to go:
129128
130129
 <verbatim>
131
-~/www/cgi-bin> chmod +x myrepo.cgi
130
+$ chmod +x ~/www/cgi-bin/myrepo.cgi
132131
 </verbatim>
133132
134133
 Now simply point your browser to
135
-<tt>http://my.domain/cgi-bin/myrepo.cgi</tt> and you should
134
+<tt>https://my.domain/cgi-bin/myrepo.cgi</tt> and you should
136135
 be able to manage the repository from there.
137136
138137
 To check out a copy of your remote repository, use the
139138
 <em>clone</em> command:
140139
141140
 <verbatim>
142
-stephan@ludo:~/fossil$ fossil clone \
143
- http://MyAccountName:[email protected]/cgi-bin/myrepo.cgi
141
+$ fossil clone \
142
+ https://MyAccountName:[email protected]/cgi-bin/myrepo.cgi
144143
 </verbatim>
145144
146
-Note that you should pass your fossil login name and password (as set
147
-via local server mode) during the clone - that ensures that fossil
148
-won't ask you for it on each commit!
145
+If you do not provide your password in the URL, fossil will
146
+interactively prompt you for it.
149147
150148
 A clone is a local copy of a remote repository, and can be opened just
151149
 like a local one (as shown above). It is treated identically to your
152150
 local repository, with one very important difference. When you commit
153151
 changes to a cloned remote repository, they will be pushed back to the
154152
--- www/newrepo.wiki
+++ www/newrepo.wiki
@@ -7,11 +7,11 @@
7 sharing it over the web.
8
9 The first thing we need to do is create a fossil repository file:
10
11 <verbatim>
12 stephan@ludo:~/fossil$ fossil new demo.fossil
13 project-id: 9d8ccff5671796ee04e60af6932aa7788f0a990a
14 server-id: 145fe7d71e3b513ac37ac283979d73e12ca04bfe
15 admin-user: stephan (initial password is ******)
16 </verbatim>
17
@@ -24,11 +24,11 @@
24
25 The first thing we normally want to do is to run fossil as a local server so
26 that you can configure the access rights to the repo:
27
28 <verbatim>
29 stephan@ludo:~/fossil$ fossil ui demo.fossil
30 </verbatim>
31
32 The <tt>ui</tt> command starts up a server (with an optional <tt>-port
33 NUMBER</tt> argument) and launches a web browser pointing at the
34 fossil server. From there it takes just a few moments to configure the
@@ -50,14 +50,13 @@
50
51 The next thing we need to do is <em>open</em> the repository. To do so
52 we create a working directory and then <tt>cd</tt> to it:
53
54 <verbatim>
55 stephan@ludo:~/fossil$ mkdir demo
56 stephan@ludo:~/fossil$ cd demo
57 stephan@ludo:~/fossil/demo$ fossil open ../demo.fossil
58 stephan@ludo:~/fossil/demo$
59 </verbatim>
60
61 That creates a file called <tt>_FOSSIL_</tt> in the current
62 directory, and this file contains all kinds of fossil-related
63 information about your local repository. You can ignore it
@@ -67,36 +66,36 @@
67 The next thing we need to do is add files to our repository. As it
68 happens, we have a few C source files lying around, which we'll
69 simply copy into our working directory.
70
71 <verbatim>
72 stephan@ludo:~/fossil/demo$ cp ../csnip/*.{c,h} .
73 stephan@ludo:~/fossil/demo$ ls
74 clob.c clob.h clobz.c _FOSSIL_ mkdep.c test-clob.c
75 tokenize_path.c tokenize_path.h vappendf.c vappendf.h
76 </verbatim>
77
78 Fossil doesn't know about those files yet. Telling fossil about
79 a new file is a two-step process. First we <em>add</em> the file
80 to the repository, then we <em>commit</em> the file. This is a familiar
81 process for anyone who's worked with SCM systems before:
82
83 <verbatim>
84 stephan@ludo:~/fossil/demo$ fossil add *.{c,h}
85 stephan@ludo:~/fossil/demo$ fossil commit -m "egg"
86 New_Version: d1296b4a08b9f8b943bb6c73698e51eed23f8f91
87 </verbatim>
88
89 We now have a working repository! The file <tt>demo.fossil</tt>
90 is the central storage, and we can share it amongst an arbitrary
91 number of trees. As a silly example:
92
93 <verbatim>
94 stephan@ludo:~/fossil/demo$ cd ~/fossil
95 stephan@ludo:~/fossil$ mkdir demo2
96 stephan@ludo:~/fossil$ cd demo2
97 stephan@ludo:~/fossil/demo2$ fossil open ../demo.fossil
98 ADD clob.c
99 ADD clob.h
100 ADD clobz.c
101 ADD mkdep.c
102 ADD test-clob.c
@@ -112,12 +111,12 @@
112 Making your repository available over the web is trivial to do. We
113 assume you have some web space where you can store your fossil file
114 and run a CGI script. If not, then this option is not for you. If
115 you do, then here's how...
116
117 Copy the fossil repository file to your web server (it doesn't
118 matter where, really).
119
120 In your <tt>cgi-bin</tt> (or equivalent) directory, create a file
121 which looks like this:
122
123 <verbatim>
@@ -126,28 +125,27 @@
126 </verbatim>
127
128 Make that script executable, and you're all ready to go:
129
130 <verbatim>
131 ~/www/cgi-bin> chmod +x myrepo.cgi
132 </verbatim>
133
134 Now simply point your browser to
135 <tt>http://my.domain/cgi-bin/myrepo.cgi</tt> and you should
136 be able to manage the repository from there.
137
138 To check out a copy of your remote repository, use the
139 <em>clone</em> command:
140
141 <verbatim>
142 stephan@ludo:~/fossil$ fossil clone \
143 http://MyAccountName:[email protected]/cgi-bin/myrepo.cgi
144 </verbatim>
145
146 Note that you should pass your fossil login name and password (as set
147 via local server mode) during the clone - that ensures that fossil
148 won't ask you for it on each commit!
149
150 A clone is a local copy of a remote repository, and can be opened just
151 like a local one (as shown above). It is treated identically to your
152 local repository, with one very important difference. When you commit
153 changes to a cloned remote repository, they will be pushed back to the
154
--- www/newrepo.wiki
+++ www/newrepo.wiki
@@ -7,11 +7,11 @@
7 sharing it over the web.
8
9 The first thing we need to do is create a fossil repository file:
10
11 <verbatim>
12 $ fossil new demo.fossil
13 project-id: 9d8ccff5671796ee04e60af6932aa7788f0a990a
14 server-id: 145fe7d71e3b513ac37ac283979d73e12ca04bfe
15 admin-user: stephan (initial password is ******)
16 </verbatim>
17
@@ -24,11 +24,11 @@
24
25 The first thing we normally want to do is to run fossil as a local server so
26 that you can configure the access rights to the repo:
27
28 <verbatim>
29 $ fossil ui demo.fossil
30 </verbatim>
31
32 The <tt>ui</tt> command starts up a server (with an optional <tt>-port
33 NUMBER</tt> argument) and launches a web browser pointing at the
34 fossil server. From there it takes just a few moments to configure the
@@ -50,14 +50,13 @@
50
51 The next thing we need to do is <em>open</em> the repository. To do so
52 we create a working directory and then <tt>cd</tt> to it:
53
54 <verbatim>
55 $ mkdir demo
56 $ cd demo
57 $ fossil open ../demo.fossil
 
58 </verbatim>
59
60 That creates a file called <tt>_FOSSIL_</tt> in the current
61 directory, and this file contains all kinds of fossil-related
62 information about your local repository. You can ignore it
@@ -67,36 +66,36 @@
66 The next thing we need to do is add files to our repository. As it
67 happens, we have a few C source files lying around, which we'll
68 simply copy into our working directory.
69
70 <verbatim>
71 $ cp ../csnip/*.{c,h} .
72 $ ls
73 clob.c clob.h clobz.c mkdep.c test-clob.c
74 tokenize_path.c tokenize_path.h vappendf.c vappendf.h
75 </verbatim>
76
77 Fossil doesn't know about those files yet. Telling fossil about
78 a new file is a two-step process. First we <em>add</em> the file
79 to the repository, then we <em>commit</em> the file. This is a familiar
80 process for anyone who's worked with SCM systems before:
81
82 <verbatim>
83 $ fossil add *.{c,h}
84 $ fossil commit -m "egg"
85 New_Version: d1296b4a08b9f8b943bb6c73698e51eed23f8f91
86 </verbatim>
87
88 We now have a working repository! The file <tt>demo.fossil</tt>
89 is the central storage, and we can share it amongst an arbitrary
90 number of trees. As a silly example:
91
92 <verbatim>
93 $ cd ~/fossil
94 $ mkdir demo2
95 $ cd demo2
96 $ fossil open ../demo.fossil
97 ADD clob.c
98 ADD clob.h
99 ADD clobz.c
100 ADD mkdep.c
101 ADD test-clob.c
@@ -112,12 +111,12 @@
111 Making your repository available over the web is trivial to do. We
112 assume you have some web space where you can store your fossil file
113 and run a CGI script. If not, then this option is not for you. If
114 you do, then here's how...
115
116 Copy the fossil repository file to your web server (it doesn't matter
117 where, really, but it "should" be unreachable by web browser traffic).
118
119 In your <tt>cgi-bin</tt> (or equivalent) directory, create a file
120 which looks like this:
121
122 <verbatim>
@@ -126,28 +125,27 @@
125 </verbatim>
126
127 Make that script executable, and you're all ready to go:
128
129 <verbatim>
130 $ chmod +x ~/www/cgi-bin/myrepo.cgi
131 </verbatim>
132
133 Now simply point your browser to
134 <tt>https://my.domain/cgi-bin/myrepo.cgi</tt> and you should
135 be able to manage the repository from there.
136
137 To check out a copy of your remote repository, use the
138 <em>clone</em> command:
139
140 <verbatim>
141 $ fossil clone \
142 https://MyAccountName:[email protected]/cgi-bin/myrepo.cgi
143 </verbatim>
144
145 If you do not provide your password in the URL, fossil will
146 interactively prompt you for it.
 
147
148 A clone is a local copy of a remote repository, and can be opened just
149 like a local one (as shown above). It is treated identically to your
150 local repository, with one very important difference. When you commit
151 changes to a cloned remote repository, they will be pushed back to the
152

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button