SHA1 Hash:	67b5f419631974a88796ae0d4b2f6ec8a35d37f5
Date:	2009-08-24 16:00:05
User:	drh
Comment:	Added the "selfhost.wiki" page that talks about the three self-hosting fossil repositories and how they are automatically synchronized.
Timelines:	ancestors | descendants | both | trunk
Other Links:	files | ZIP archive | manifest

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

Modified www/index.wiki from [e46bb66656] to [64af6f83b5].

@@ -5,13 +5,12 @@
 [http://en.wikipedia.org/wiki/Revision_control | distributed software version control system]
 that includes an integrated
 [./wikitheory.wiki | distributed wiki] and an integrated
 [./bugtheory.wiki | distributed bug-tracking system] all in a single,
 easy-to-use, stand-alone executable.
-Fossil is [http://www.fossil-scm.org/ | self-hosting]
-since 2007-07-21 on
-[http://www.hwaci.com/cgi-bin/fossil | two separate servers].
+Fossil has been [./selfhost.wiki | self-hosting]
+since 2007-07-21.
 You can download the [/timeline?y=ci | latest sources] and
 [./build.wiki | compile it yourself].
 Or you can grab
 [http://www.fossil-scm.org/download.html | pre-compiled binaries].
 

Added www/selfhost.wiki version [1b51c5e697]

@@ -1,1 +1,66 @@
+<title>Fossil Self-Hosting Repositories</title>
+<h1 align="center">Fossil Self-Hosting Repositories</h1>
+
+Fossil has self-hosted since 2007-07-21.  As of this writing (2009-08-24)
+there are three publicly accessible repositories for he Fossil source code:
+
+  1.  [http://www.fossil-scm.org/]
+  2.  [http://www.hwaci.com/cgi-bin/fossil]
+  3.  [http://www2.fossil-scm.org/]
+
+
+The canonical repository is (1).  Repositories (2) and (3) automatically
+stay in synchronization with (1) via a
+<a href="http://en.wikipedia.org/wiki/Cron">cron</a> job that invokes
+"fossil sync" on a daily basis.
+
+Note that the two secondary repositories are more than just read-only mirrors.
+All three servers support full read/write capabilities.
+Changes (such as new tickets or wiki or check-ins) can be implemented
+on any of the three servers and those changes automatically propagate to the
+other two servers.
+
+Server (1) runs as a CGI script on a
+<a href="http://www.linode.com/">Linode 720</a> located in Dallas, TX
+- on the same virtual
+machine hosts <a href="http://www.sqlite.org/">SQLite</a> and over a
+dozen other smaller projects.  This demonstrates that Fossil does not
+require much server power.
+Multiple fossil-based projects an easily be hosted on the same machine,
+even if that machine is itself one of several dozen virtual machines on
+single physical box.  The CGI script that runs the canonical Fossil
+self-hosting repository is as follows:
+
+<blockquote><pre>
+#!/usr/bin/fossil
+repository: /fossil/fossil.fossil
+</pre></blockquote>
+
+Server (2) run as a CGI script on a shared hosting account at
+<a href="http://www.he.net/">Hurricane Electric</a> in San Jose and
+Fremont, CA.  This server demonstrates the ability of
+Fossil to run on an economical shared-host web account with no
+privileges beyond port 80 HTTP access and CGI.  It is not necessary
+to have a dedicated server to run Fossil.  As far as we are aware,
+Fossil is the only full-featured configuration management system
+that can run in
+such a restricted environment.  The CGI script that runs on the
+Hurricane Electric server is the same as the CGI script shown above,
+except that the pathnames are modified to suite the environment:
+
+<blockquote><pre>
+#!/home/hwaci/bin/fossil
+repository: /home/hwaci/fossil/fossil.fossil
+</pre></blockquote>
+
+Server (2) is synchronized with the canonical server (1) by running
+the following command via cron:
+
+<blockquote><pre>
+/home/hwaci/bin/fossil sync -R /home/hwaci/fossil/fossil.fossil
+</pre></blockquote>
 
+Server (3) is a
+<a href="http://www.linode.com/">Linode 360</a> located in Atlanta, GA
+and set up just like the canonical server (1) with the addition of a
+cron job for synchronization as in server (2).