Document syncing to test
This commit is contained in:
parent
c32d50dacb
commit
6c173745d1
1 changed files with 9 additions and 0 deletions
|
@ -79,7 +79,16 @@ ahoy artifacts
|
||||||
ahoy deploy-site-force example_test
|
ahoy deploy-site-force example_test
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Sync live database to test
|
||||||
|
|
||||||
|
If you have new content on the live site that you want to see how your code works with, or if you have created entities on the test site that block the removal of configuration you changed your mind about, you will want to sync from live to test.
|
||||||
|
|
||||||
|
```bash
|
||||||
|
ssh d-example-live
|
||||||
|
sync_to_test.sh
|
||||||
|
```
|
||||||
|
|
||||||
|
This handles making a paranoia dump of the test site in `~/backups`, dropping the test database to ensure no tables are left to clutter and interfere, skipping the content of cache tables, and bringing over user files (skipping cache files like the twig folder).
|
||||||
|
|
||||||
## Bonus: Keep Drutopia builds with similar available modules
|
## Bonus: Keep Drutopia builds with similar available modules
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue