aboutsummaryrefslogtreecommitdiff
path: root/scripts/box/create-backup.env.sh (unfollow)
Commit message (Collapse)AuthorFilesLines
2019-06-10Send logs via email after finishing provision.shEuAndreh1-0/+2
The email will be send for both sucessfull and failed runs.
2019-06-10Remove --progress from borg createEuAndreh1-1/+0
It shows filenames in CI output log.
2019-06-08CI debug: remove --verbose flag from borg create commandEuAndreh1-1/+0
THe objective is to remove the logged files from the CI log.
2019-06-06Fail fast on copied Bash filesEuAndreh1-0/+1
2019-06-05Remove debug echoEuAndreh1-1/+0
2019-06-05Fix ShellCheck offensesEuAndreh1-1/+1
2019-06-05Restore from backup in fresh volumeEuAndreh1-1/+2
2019-06-05Use specific known keys for connecting with the backup serverEuAndreh1-1/+1
2019-06-05Use Ansible instead of Bash for provisioningEuAndreh1-0/+2
The deployment is not quite working, and I'm unable to test right now: DigitalOcean is returning 503 for my requests. As of this commit, I can run =ansible-playbook provider.yml= more than once and it will actually be idempotent. Notes: - SSH fingerprint are now taken from the public key file instead of manually supplying it in the terraform template using the =digitalocean_ssh_key= resource; - use Ansible instead of ad-hoc Bash scripts for provisioning the Droplets created by Terraform; - use the =filename.env.extension= to create the concrete files in CI; - use the =user_data= to add the know SSH key pair to the newly created Droplet; - add =rotate-ssh-keys.sh= utils;
2019-05-28Split scripts into CI and VPS boxEuAndreh1-0/+0
2019-05-28Add backup routing before possibly tearing down machineEuAndreh1-0/+11
Create a new backup entry before running =terraform apply=, which may (or may not) destroy the current machine. This shouldn't be an issue for the backup itself, since all of the data should be stored in a separate Block Storage Volume, but we can take advantage of the sevices already needing to be taken down in order to perform a full backup of the data.