aboutsummaryrefslogtreecommitdiff
path: root/secrets/terraform (follow)
Commit message (Expand)AuthorAgeFilesLines
* Use NGINX to handle the creation of certificates for prosody•••After a terraform state rm '...' of the server and domain configuration, and recreating the instance again while leaving the dettached one running. I had to do this because I was experimenting too much with the domain and I hit the Let's Encrypt rate limit[0]. Because of that I'll recreate certificates less often so that doesn't happen in the new domain during development of the VPS. I'm not shure if this solution works, but I'll commit just as a checkpoint. I had to change the custom DNS nameservers from Digital Ocean to Vultr and that may take a while, so it's worth having this as a checkpoint in time while I'm off to other things. [0]: https://letsencrypt.org/docs/rate-limits/ EuAndreh2020-08-166-0/+0
* Use new image with ownership of /etc/nixos/configuration.nix by user•••Useful reference: - https://discourse.nixos.org/t/can-i-move-etc-nixos-to-my-dotfiles-and-symlink-it-back-to-etc-nixos/4833/10 EuAndreh2020-08-154-0/+0
* Add generated Terraform filesEuAndreh2020-08-144-0/+0
* Add updated terraform filesEuAndreh2020-08-142-0/+0
* Add .tfplan extension to Terraform plan filesEuAndreh2020-08-1233-0/+0
* vps-configuration.env.nix: Finish working Nextcloud installationEuAndreh2020-08-116-0/+0
* Update Terraform infrastructureEuAndreh2020-08-103-0/+0
* Semi working setup: Terraform and LetsEncrypt workingEuAndreh2020-08-1021-0/+0
* Interactive Terraform plan -> apply cycleEuAndreh2020-08-1011-0/+0
* Migration: Remove Ansible and Docker code, move only to NixOSEuAndreh2020-08-101-0/+0
* WIP: Move to Vultr and NixOSEuAndreh2020-08-102-0/+0