aboutsummaryrefslogtreecommitdiff
path: root/vps-configuration.env.nix (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Use NGINX to handle the creation of certificates for prosodyEuAndreh2020-08-161-9/+26
| | | | | | | | | | | | | | | | | | 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/
* Use letsencrypt to generate the TLS certificateEuAndreh2020-08-151-11/+4
|
* Remove duplicate letsencryptEmail entryEuAndreh2020-08-151-1/+0
| | | | | This option is to override the global one. Since they are the same, it has no effect.
* Deploy "boneco" project at boneco.$TLDEuAndreh2020-08-151-0/+17
|
* Set "prosody" as the group for generated certificatesEuAndreh2020-08-141-1/+2
|
* nixfmt ./vps-configuration.env.nixEuAndreh2020-08-141-5/+5
|
* Stop hardcoding the user in favor of $USER_NAMEEuAndreh2020-08-141-2/+3
|
* Don't make lighttpd the user owner of $GIT_ROOTEuAndreh2020-08-141-1/+1
|
* Setup cgit and ProsodyEuAndreh2020-08-141-4/+91
| | | | The TLS setup for Prosody is broken, though.
* vps-configuration.env.nix: Finish working Nextcloud installationEuAndreh2020-08-111-24/+20
|
* Filter encrypted files from lintingEuAndreh2020-08-101-10/+5
|
* Semi working setup: Terraform and LetsEncrypt workingEuAndreh2020-08-101-30/+32
|
* Use password via stdin, and store the snapshot image configuration.nixEuAndreh2020-08-101-0/+118