aboutsummaryrefslogtreecommitdiff
path: root/TODOs.org (unfollow)
Commit message (Collapse)AuthorFilesLines
2019-11-16TODOs.orgEuAndreh1-1/+2
2019-11-16TODOs.orgEuAndreh1-0/+1
2019-11-02TODOs.orgEuAndreh1-0/+1
2019-06-18TODOs.orgEuAndreh1-0/+1
2019-06-17TODOs.orgEuAndreh1-2/+5
2019-06-16TODOs.orgEuAndreh1-2/+12
2019-06-15TODOs.orgEuAndreh1-0/+5
2019-06-14TODOs.orgEuAndreh1-0/+2
2019-06-14TODOs.orgEuAndreh1-0/+1
2019-06-13TODOs.orgEuAndreh1-0/+2
2019-06-13TODOs.orgEuAndreh1-0/+1
2019-06-13TODOs.orgEuAndreh1-0/+2
2019-06-11TODOs.orgEuAndreh1-1/+2
2019-06-11TODOs.orgEuAndreh1-1/+4
2019-06-11TODOs.orgEuAndreh1-6/+10
2019-06-11Run shutdown with Ansible instead of BashEuAndreh1-1/+4
2019-06-10TODOs.orgEuAndreh1-15/+27
2019-06-10Store updated Terraform files in case of failureEuAndreh1-1/+2
2019-06-10Trust commited keyEuAndreh1-0/+2
2019-06-10Encrypt attached logEuAndreh1-2/+3
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-10Fail CI run if backup failsEuAndreh1-1/+2
2019-06-10Provision DNS entries using DigitalOcean instead of DNS registrarEuAndreh1-19/+82
This way we can implement dynamic (provision-time) Floating IP, instead of a hardcoded pre-created Floating IP address. Related changes: - remove =terraform-godaddy= provider, use =digitalocean_record= instead; - create =generated-known-hosts= after provisioning instead of during =setup.sh=: use the =$(terraform output public_floating_ip)= value to make this file dynamic; - remote the =$PINNED_IP= and =$TF_VAR_floating_ip= variables; - add type and descriptions to variable declarations in Terraform recipe.
2019-06-08TODOs.orgEuAndreh1-0/+1
2019-06-08TODOs.orgEuAndreh1-0/+4
2019-06-08Use terraform-godaddy and Terraform 0.11EuAndreh1-0/+1
The =terraform-godaddy= package supports only Terraform 0.11 as of now. It is not packaged by default by nixpkgs, and the =postInstall= hook is required because Terraform looks for providers usinthe the =terraform-provider-$name= template, which the package doesn't follow. I had to remove the loop on vps.tf since it requires Terraform 0.12. I'll either wait for =terraform-godaddy= to upgrade to 0.12 or try to do it myself if it bothers me enough.
2019-06-08TODOs.orgEuAndreh1-21/+21
2019-06-08Use nextcloud.${TLD} instead of cloud.${TLD} as CNAME for Nextcloud installationEuAndreh1-1/+1
2019-06-08TODOs.orgEuAndreh1-1/+9
2019-06-07TODOs.orgEuAndreh1-0/+6
2019-06-07TODOs.orgEuAndreh1-0/+2
2019-06-06Allow backups to fail for nowEuAndreh1-0/+1
2019-06-05TODOs.orgEuAndreh1-1/+2
2019-06-05TODOs.orgEuAndreh1-0/+1
2019-06-05Always destroy infrastructure before applyingEuAndreh1-1/+2
2019-06-05TODOs.orgEuAndreh1-1/+2
2019-06-05TODOs.orgEuAndreh1-1/+5
2019-06-05TODOs.orgEuAndreh1-0/+19
2019-06-05Use Ansible instead of Bash for provisioningEuAndreh1-3/+29
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-06-04TODOs.orgEuAndreh1-0/+1
2019-06-04TODOs.orgEuAndreh1-0/+4
2019-06-02TODOs.orgEuAndreh1-0/+2
2019-06-01TODOs.orgEuAndreh1-0/+1
2019-05-30TODOs.orgEuAndreh1-5/+52
2019-05-28Use Floating IP on DropletEuAndreh1-1/+7
2019-05-28TODOs.orgEuAndreh1-1/+5
Extend on how to use =vps-state= to store Terraform state.
2019-05-28TODOs.orgEuAndreh1-0/+11
Expand on the decision of using =vps-state= to store Terraform files.
2019-05-28Add backup routing before possibly tearing down machineEuAndreh1-1/+4
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.
2019-05-27TODOs.orgEuAndreh1-0/+2
2019-05-27TODOs.orgEuAndreh1-0/+1
Add =Nice to have= task on docker-compose version