# HG changeset patch
# User Chris Cannam
# Date 1598351923 -3600
# Node ID 7e2de1c811b318e1471da677462767296953ca2b
# Parent  44cbe9fa0b4ee39fdfcbd5196a3ec6cd774bcde4
More notes

diff -r 44cbe9fa0b4e -r 7e2de1c811b3 deploy/README
--- a/deploy/README	Thu Feb 07 13:49:16 2019 +0000
+++ b/deploy/README	Tue Aug 25 11:38:43 2020 +0100
@@ -7,6 +7,13 @@
 that you are providing a database dump to load -- there is no
 provisioning step to initialise a new database.
 
+The provisioning process consists mostly of running the scripts found
+in provisioning.d/ in numerical order (see those scripts themselves
+for details) and installing appropriately modified versions of the
+various config files found in config/. Please refer to these files for
+documentary purposes, but don't try to run or install them by hand -
+there are scripts to coordinate it. Read on for instructions.
+
 
 You will need
 -------------
@@ -14,7 +21,10 @@
 Required:
 
  * A database dump to load. This should be left in a file called
-   postgres-dumpall in the soundsoftware-site root
+   postgres-dumpall in the soundsoftware-site root. The actual live
+   site creates regular database dumps which it saves in
+   /var/files/backups/postgres-dumpall-<date>.bz2, so one of these or
+   a backup, if available, could be copied over to seed the new site
 
  * The database password and /sys API key for the target site. (This
    can be queried from the db: settings table, name "sys_api_key". You