SHA1 Hash:	70dcb9fc8baea109ee504804db921f27dcc06764
Date:	2008-05-19 15:08:39
User:	drh
Comment:	Clarifications of the "quickstart.wiki" documentation.
Timelines:	ancestors | descendants | both | trunk
Other Links:	files | ZIP archive | manifest

• branch=trunk inherited from [a28c83647d]
• sym-trunk inherited from [a28c83647d]

Modified www/quickstart.wiki from [7b2cbf4808] to [d68d09590f].

@@ -14,14 +14,18 @@
     someplace on your PATH environment variable.</p>
 
     </blockquote>
     <h2>Cloning A Existing Repository</h2>
     <blockquote>
- 	<p>Cloning is the first step in checking out a repository,
-	and is fossil's equivalent to making a local copy of a remote repository.</p>
-
-    <p>Use this command:</p>
+
+    <p>Most fossil operations interact with a repository that is on the
+    local disk drive, not on a remote system.  Hence, before accessing
+    a remote repository it is necessary to make a local copy of that
+    repository.  Making a local copy of a remote repository is called
+    "cloning".</p>
+
+    <p>Clone a remote repository as follows:</p>
 
     <blockquote>
     <b>fossil clone</b> <i>URL  repository-filename</i>
     </blockquote>
 
@@ -29,17 +33,17 @@
     you want to clone.  You can call the new repository anything you
     want - there are no naming restrictions.  As an example, you can
     clone the fossil repository this way:</p>
 
     <blockquote>
-    <b>fossil clone http://www.fossil-scm.org/fossil myclone.fsl</b>
-    </blockquote>
-
-    <p>Cloning only a local copy of the source tree (as a single file), but
-        not something you can directly browse. After cloning, you can access
-        the files in the repository using the <tt>open</tt> command,
-        described below</p>
+    <b>fossil clone http://www.fossil-scm.org/fossil myclone.fossil</b>
+    </blockquote>
+
+    <p>The new local copy of the respository is stored in a single file,
+    which in the example above is named "myclone.fossil".
+    You can name your repositories anything you want.  The ".fossil" suffix
+    is not required.</p>
 
     <p>Note: If you are behind a restrictive firewall, you might need
     to <a href="#proxy">specify an HTTP proxy</a> to use.</p>
 
 </blockquote><h2>Starting A New Project</h2><blockquote>
@@ -179,11 +183,11 @@
     <b>commit</b> and possibly also <b>push</b> your changes.   Remember
     that nobody else can see your changes until you <b>commit</b> and
     if other are using a different repository you will also need to
     <b>push</b>.</p>
 
-<a name="serversetup">
+<a name="serversetup"></a>
 </blockquote><h2>Setting Up A Server</h2><blockquote>
 
     <p>The easiest way to set up a server is:</p>
 
     <blockquote>
@@ -209,11 +213,11 @@
     inetd server.  To use the CGI server, create a CGI script that
     looks something like this:</p>
 
     <blockquote><b>
     #!/usr/local/bin/fossil<br>
-    repository: /home/proj1/repos1.fsl
+    repository: /home/proj1/repos1.fossil
     </b></blockquote>
 
     <p>Adjust the paths in this CGI script to match your installation.
     Now point clients at the CGI script.  That's all there is to it!</p>
 
@@ -221,11 +225,11 @@
     installation, make an entry in /etc/inetd.conf that looks something
     like this:</p>
 
     <blockquote><b>
     80 stream tcp nowait.1000 root /usr/bin/fossil \<br>
-        /usr/bin/fossil http /home/proj1/repos1.fsl
+        /usr/bin/fossil http /home/proj1/repos1.fossil
     </b></blockquote>
 
     <p>Adjust the paths to suit your installation, of course.  Notice that
     fossil runs as root.  This is not required - you can run it as an
     unprivileged user.  But it is more secure to run fossil as root.