diff --git a/handbook/update.htm b/handbook/update.htm index a28c8e67d..771662229 100644 --- a/handbook/update.htm +++ b/handbook/update.htm @@ -119,19 +119,19 @@ stored just as files (not in version control). See below for details on that.
-rsync -av expo@expo.survex.com:expoimages /home/expo/fromserver
+rsync -av expo@expo.survex.com:expoimages /home/expo
To sync the local expoimage directory back to the server:
-rsync -av /home/expo/fromserver/expoimages expo@expo.survex.com:
+rsync -av /home/expo/expoimages expo@expo.survex.com:
-(do be careful not to delete piles of stuff then rsync back - as it'll all get deleted on the server too, and we may not have backups!)
+(do be careful not to delete piles of stuff then rsync back - as it'll all get deleted on the server too, and we may not have backups!). Use rsync --dry-run --delete-after -a to check what would be deleted.
To edit the website fully, you need a mercurial client. Some (static text) pages can be edited directly on-line using the 'edit this page link' which you'll see if you are logged into troggle. DYnamically-generated pages can not be edited in this way.
+To edit the website fully, you need a mercurial client. Some (static text) pages can be edited directly on-line using the 'edit this page link' which you'll see if you are logged into troggle. In general dynamically-generated pages can not be edited in this way, but forms are provided for some page-types like 'caves'.
-Mercurial can be used from the command line, but if you prefer a GUI, tourtoisehg is highly recommended on all OSes (available on Linux from Debian 6 and Ubuntu 11.04 onwards).
+Mercurial can be used from the command line, but if you prefer a GUI, tourtoisehg is highly recommended on all OSes.
Linux: Install mercurial and tortoisehg-nautilus from synaptic, then restart nautilus nautilus -q. If it works, you'll be able to see the menus of Tortoise within your Nautilus windows.
@@ -164,10 +164,12 @@ then restart nautilus nautilus -q. If it works, you'll be able to see thg push
-If someone else is editing the same bit at the same time you may also need to:
+Before pushing, you should do an hg pull to sync with upstream first. If someone else has edited the same files you may also need to do:
hg merge
+before pushing again
+Simple changes to static files will take effect immediately, but changes to dynamically-generated files (cave descriptions, QM lists etc) will not take effect, until the server runs the expoweb-update script.