2020-06-13 10:03:06 +00:00
|
|
|
# Tips for moving deployments
|
|
|
|
|
|
|
|
|
|
- Take regular automatic backups and push the files to S3 compatible cloud. Setup backup and push with cronjobs
|
2021-12-10 08:53:43 +00:00
|
|
|
- Use regular cron for single machine installs
|
|
|
|
|
- Use [swarm-cronjob](https://github.com/crazy-max/swarm-cronjob) for docker swarm
|
|
|
|
|
- Use Kubernetes CronJob
|
2020-06-13 10:03:06 +00:00
|
|
|
- It makes it easy to transfer data from cloud to any new deployment.
|
2020-06-13 10:10:47 +00:00
|
|
|
- They are just [site operations](site-operations.md) that can be manually pipelined as per need.
|
2020-06-13 10:03:06 +00:00
|
|
|
- Remember to restore encryption keys and other custom configuration from `site_config.json`.
|
|
|
|
|
- Steps to move deployment:
|
2021-12-10 08:53:43 +00:00
|
|
|
- [Take backup](site-operations.md#backup-sites)
|
|
|
|
|
- [Push backup to cloud](site-operations.md#push-backup-to-s3-compatible-storage)
|
|
|
|
|
- Create new deployment type anywhere
|
|
|
|
|
- [Restore backup from cloud](site-operations.md#restore-backups)
|
|
|
|
|
- [Restore `site_config.json` from cloud](site-operations.md#edit-configs)
|
