server - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add credentials for manipulating DNS entries.	EuAndreh	2019-06-08	1	-0/+0
\|
*	Use nextcloud.${TLD} instead of cloud.${TLD} as CNAME for Nextcloud installation	EuAndreh	2019-06-08	1	-0/+0
\|
*	Add ${DESTROY_VOLUME} operational toggle	EuAndreh	2019-06-06	1	-0/+0
\| \| \| \| \| \| \| \| \| \| \| \| \|	This way I can dynamically control whether to destroy and recreate all the existing infrastructure entirely from scratch. The advantages of doing so are: - test the non-existence of local state on every deployment; - make sure I can always recreate everything from scratch. The disadvantages are: - slower deployment times; - longer downtime during deployments.
*	Use non-standard port for SSH	EuAndreh	2019-06-05	1	-0/+0
\|
*	Use Ansible instead of Bash for provisioning	EuAndreh	2019-06-05	1	-0/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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;
*	Use Floating IP on Droplet	EuAndreh	2019-05-28	1	-0/+0
\|
*	Remove git rev-parse from .envrc	EuAndreh	2019-05-28	1	-0/+0
\|
*	Rotate secrets	EuAndreh	2019-05-28	1	-0/+0
\|
*	Split Bash variable declaration from assignment (shellcheck offense)	EuAndreh	2019-05-28	1	-0/+0
\|
*	Add backup routing before possibly tearing down machine	EuAndreh	2019-05-28	1	-0/+0
\| \| \| \| \| \| \| \| \| \|	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.
*	Add variables to properly tag a backup	EuAndreh	2019-05-27	1	-0/+0
\|
*	Add Nextcloud recipe to docker-compose.yaml	EuAndreh	2019-05-27	1	-0/+0
\|
*	Use Bash variables for domain names and container ports	EuAndreh	2019-05-27	1	-0/+0
\|
*	Use more robust Bash cd approach	EuAndreh	2019-05-26	1	-0/+0
\|
*	Restart docker-compose after deployment	EuAndreh	2019-05-25	1	-0/+0
\|
*	Remove docker-compose.yml from git-crypt	EuAndreh	2019-05-25	1	-0/+0
\|
*	Add simple DigitalOcean droplet skeleton for Terraform	EuAndreh	2019-05-25	1	-0/+0
\|
*	Start docker-compose.yml skeleton with Wallabag	EuAndreh	2019-05-25	1	-0/+0
\|
*	Add simple stub VM definition	EuAndreh	2019-05-25	1	-0/+0