aboutsummaryrefslogtreecommitdiff
path: root/backup-and-shutdown.sh
diff options
context:
space:
mode:
authorEuAndreh <eu@euandre.org>2019-05-28 00:46:24 -0300
committerEuAndreh <eu@euandre.org>2019-05-28 00:49:16 -0300
commit83b0be5ae5abecd2076cab8b7ab2a84e9756034a (patch)
treeb0492f618208f5bc9c207721362ce16eba1b9034 /backup-and-shutdown.sh
parentAdd secrets/borg_remote{.pub} SSH keypair (diff)
downloadserver-83b0be5ae5abecd2076cab8b7ab2a84e9756034a.tar.gz
server-83b0be5ae5abecd2076cab8b7ab2a84e9756034a.tar.xz
Add backup routing before possibly tearing down machine
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.
Diffstat (limited to '')
-rwxr-xr-xbackup-and-shutdown.sh8
1 files changed, 0 insertions, 8 deletions
diff --git a/backup-and-shutdown.sh b/backup-and-shutdown.sh
deleted file mode 100755
index c880a16..0000000
--- a/backup-and-shutdown.sh
+++ /dev/null
@@ -1,8 +0,0 @@
-#!/usr/bin/env bash
-set -Eeuo pipefail
-cd "$(dirname "${BASH_SOURCE[0]}")"
-
-echo "FIXME: get current backup"
-echo docker-compose down
-echo "FIXME: create a new backup"
-echo "FIXME: rsync back new backup"