For developers

Disaster recovery

5min

This guide describes how to restore a project from a backup for developers and is not meant for disaster recovery of the hosting infrastructure.
Restore environment
If the environment was accidently removed, the only way to restore it is to redeploy it.
Restore database from a backup
Firstly, determine what database backup you wish to use using the following command:
Shell
hosty backup:database:list --full
hosty backup:database:list --full
﻿
Then, use --name flag to download the selected backup:
Shell
hosty backup:database:download --full --name=2024-07-08T00:42:13Z-full.gzip ./dump.sql.gz
hosty backup:database:download --full --name=2024-07-08T00:42:13Z-full.gzip ./dump.sql.gz
﻿
Now, upload this backup to the production environment:
Shell
hosty cp production ./dump.sql.gz hosty://path/to/persistent/storage/dump.sql.gz -v
hosty cp production ./dump.sql.gz hosty://path/to/persistent/storage/dump.sql.gz -v
﻿
Finally, log into the container and import the database:
Shell
hosty sh production
gzip -d ./path/to/persistent/storage/dump.sql.gz | mysql --user="$DB_USER" --password="$DB_PASSWORD" --host="$DB_HOST" $DB_NAME
rm ./path/to/persistent/storage/dump.sql
hosty sh production
gzip -d ./path/to/persistent/storage/dump.sql.gz | mysql --user="$DB_USER" --password="$DB_PASSWORD" --host="$DB_HOST" $DB_NAME
rm ./path/to/persistent/storage/dump.sql
﻿
Restore files from a backup
TODO: Provide instructions. It's similar to database recovery flow: first download files to the local env, then copy them to the production (or other) environment using hosty cp command.
﻿

CI/CD configuration