expoweb/handbook/update.htm

97 lines
3.7 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>CUCC Expedition Handbook: Updating the website</title>
<link rel="stylesheet" type="text/css" href="../css/main2.css" />
</head>
<body>
<h2 id="tophead">CUCC Expedition Handbook</h2>
<h1>Updating the website - HOWTO</h1>
Please refer to <a href="http://www.srcf.ucam.org/caving/wiki/Expo_website_manual" target="_blank">the latest web updating guide in CUCC website</a>
<hr />
Expo data is kept in a number of different locations.
<dl>
<dt>Loser</dt>
<dd>Contains the survex data. Mercurial repository ssh://expo@seagrass.goatchurch.org.uk/loser</dd>
<dt>Expoweb</dt>
<dd>Contains the current website. Mercurial repository ssh://expo@seagrass.goatchurch.org.uk/expoweb</dd>
<dt>Tunnel data</dt>
<dd>Contains the tunnel data. Mercurial repository ssh://expo@seagrass.goatchurch.org.uk/tunneldata</dd>
<dt>Troggle</dt>
<dd>Contains the unfinished Django based website. Mercurial repository https://goatchurch@troggle.googlecode.com/hg/ troggle</dd>
<dt>Scanned notes</dt>
<dd>Scans of survey notes and drawn up surveys. Can be got via rsync.</dd>
</dl>
<p>Mercurial is a distributed revision control system. On expo this means that
many people can edit and merge their changes with each other either when they can access
the internet. Mercurial is over the top for scanned survey notes, which do not get modified, so
they are kept as a plain directory of files.
<p>If you run windows, you are recommended to install
<a href="http://bitbucket.org/tortoisehg/stable/wiki/Home">Tortoise Hg</a>, which nicely interfaces with
windows explorer.
<h2>Get the repositories</h2>
<h3>Mercurial</h3>
<h4>Linux</h4>
hg clone RepositoryURL
<h4>Windows</h4>
Install<a href="http://bitbucket.org/tortoisehg/stable/wiki/Home">Tortoise Hg</a>.
In windows explorer right click, select Tortoise Hg .. and click Clone repository.
<br>Set the source path to RepositoryURL
<br>Set the destination to somewhere on your local harddisk.
<br>Press clone.
<h3>RSync</h3>
<h4>Linux</h4>
rsync -av expoimages expo@seagrass.goatchurch.org.uk:
<h4>Windows</h4>
Not sure yet
<h2>The website conventions bit</h2>
<p>This is likely to change with structural change to the site, with style
changes which we expect to implement and with the method by which the
info is actually stored and served up.</p>
<p>... and it's not written yet, either :-)</p>
<ul>
<li>Structure</li>
<li>Info for each cave &ndash; automatically generated by <tt>make-indxal4.pl</tt></li>
<li>Contents lists &amp; relative links for multi-article publications like
journals. Complicated by expo articles being in a separate hierarchy.</li>
<li>Translations</li>
<li>Other people's work - the noinfo hierarchy.</li>
<li>Style guide for writing cave descriptions: correct use of boldface
(<i>once</i> for each passage name, at the primary definition thereof; other
uses of the name should be links to this, and certainly should not be bold.)
</ul>
<hr />
<ul id="links">
<li><a href="index.htm">Expedition Handbook</a>
<ul>
<li><a href="survey/index.htm">Surveying guide</a> - Overview</li>
<li><a href="look4.htm">Prospecting guide</a> &ndash; Overview</li>
<li><a href="rescue.htm">Rescue guide</a></li>
<li><a href="rigit.htm">Rigging guide</a></li>
<li><a href="photo.htm">Photography guide</a></li>
</ul></li>
<li><a href="../infodx.htm">Index to info/topics pages</a></li>
<li><a href="../indxal.htm">Full Index to area 1623</a>
<ul>
<li><a href="../areas.htm">Area/subarea descriptions</a></li>
</ul></li>
<li><a href="../index.htm">Back to Expedition Intro page</a></li>
<li><a href="../../index.htm">Back to CUCC Home page</a></li>
</ul>
</body>
</html>