community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rgard...@apache.org
Subject svn commit: r1694765 - /comdev/tools/readme.md
Date Sat, 08 Aug 2015 05:41:21 GMT
Author: rgardler
Date: Sat Aug  8 05:41:21 2015
New Revision: 1694765

URL: http://svn.apache.org/r1694765
Log:
notes on the svn commit feature of the backup script

Modified:
    comdev/tools/readme.md

Modified: comdev/tools/readme.md
URL: http://svn.apache.org/viewvc/comdev/tools/readme.md?rev=1694765&r1=1694764&r2=1694765&view=diff
==============================================================================
--- comdev/tools/readme.md (original)
+++ comdev/tools/readme.md Sat Aug  8 05:41:21 2015
@@ -197,12 +197,29 @@ migration again.
 
 In order to backup your data run the script"
 
-    ./scripts/backup.sh [dev|stage|local]
+    ./scripts/backup.sh [dev|stage|local] [commit]
 
 Your backup files will be stored in /fixtures in JSON format.
 
 When running in production it is recommended that you run this script
-via a cron job or similar.
+via a cron job or similar. However, note that depending on your setup
+this may result in the backup data being saved to an ephemeral disk -
+not ideal for a data backup. It is your responsbibility to ensure the
+data is securely backed up from within the container.
+
+### Interim backup solution
+
+One way to backup the data, since it is just a text file, is to put it
+in SVN along with the project code. This will be handled automatically
+for you if you add a second argument "commit". 
+
+However, for this to work the script needs to be run by a user with
+commit access to the repository. Also note that there is a danger that
+users will overwrite the data with there own data from a local
+instance of the application.
+
+Despite these drawbacks this is a good temporary workaround since you
+will always have SVN history to revert to.
 
 TODO: implement a restore script
 



Mime
View raw message