diff options
| author |   khilman <khilman@users.noreply.github.com> | 2018-07-20 11:38:40 -0500 |
|---|---|---|
| committer |   GitHub <noreply@github.com> | 2018-07-20 11:38:40 -0500 |
| commit | 45f76344b4278f1ecf9956f3a81bfe11cd525c43 (patch) | |
| tree | 08cfb059940190cac3eb62bcb8b5a6d01ca67396 /README.md | |
| parent | ed83f7aa1af39e75c10d5e8c4f1385c302beec12 (diff) | |
| parent | 0f09e5c9b89cee21a6ee39db9daf8e17525dd493 (diff) | |
Merge pull request #32 from montjoie/persistantdb_pr
Persistantdb pr
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -215,6 +215,7 @@ masters: - name: lava-master name of the master host: name name of the host running lava-master (default to "local") webadmin_https: Does the LAVA webadmin is accessed via https + persistent_db: True/False (default False) Is the postgres DB is persistent over reboot users: - name: LAVA username token: The token of this user @@ -321,6 +322,17 @@ For the moment, it is unsupported and unbuilded. ## Backporting LAVA patches All upstream LAVA patches could be backported by placing them in lava-master/lava-patch/ +## Backups / restore +For backupping a running docker, the "backup.sh" script could be used. +It will store boards.yaml + postgresql database backup + joboutputs. + +For restoring a backup, postgresql database backup + joboutputs must be copied in master backup directory before build. + +Example: +./backup.sh +This produce a backup-20180704_1206 directory +For restoring this backup, simply cp backup-20180704_1206/* output/local/master/backup/ + ## Security Note that this container provides defaults which are unsecure. If you plan on deploying this in a production enviroment please consider the following items: |