aboutsummaryrefslogtreecommitdiff
path: root/TODOs.org
diff options
context:
space:
mode:
authorEuAndreh <eu@euandre.org>2019-05-25 23:26:36 -0300
committerEuAndreh <eu@euandre.org>2019-05-26 10:03:43 -0300
commitb1a05c7abedc5568ef7a62ce433b97a2a3d286b7 (patch)
treeebb85ed44c195e6777c6d1cc244eff4dafcc2c54 /TODOs.org
parentPull Docker images before running docker-compose up (diff)
downloadtoph-b1a05c7abedc5568ef7a62ce433b97a2a3d286b7.tar.gz
toph-b1a05c7abedc5568ef7a62ce433b97a2a3d286b7.tar.xz
TODOs.org
Diffstat (limited to 'TODOs.org')
-rw-r--r--TODOs.org23
1 files changed, 21 insertions, 2 deletions
diff --git a/TODOs.org b/TODOs.org
index 5b6934a..65571b4 100644
--- a/TODOs.org
+++ b/TODOs.org
@@ -4,8 +4,24 @@ CLOSED: [2019-05-25 Sat 13:29]
** DONE Properly provision Ubuntu droplet
CLOSED: [2019-05-25 Sat 17:50]
** TODO Use Digital Ocean's Volumes for persistent extended storage
-** WAITING Configure DNS from Terraform
** TODO Automate deployment of updates
+During build, decrypt content of files and update the deployment.
+
+How does Terraform tfstate file can be handled in this case?
+
+UPDATE:
+Terraform does support the so called "backends" to coordinate lock and usage of the =.tfstate= files. On this regard there are no restrictions on continously deploying with Terraform from the CI pipelines.
+
+However the current applications do *not* properly support blue/green deployment, like email, Nextcloud, etc.
+
+We could try to share a shared volume, but that would be a consistency nightmare.
+
+The other option is to always recreate everything, with downtime. The advantage is that we get actual immutable deployments with stateful storage, but there would be downtime for every deployment. This is due to the nature of most of the packaged applications being single node *only*.
+
+A reasonable alternative would be to redeploy everything on a different node, with a different TLD, and manually check that. But that would be just like an staging environment, with all of it's downsides too.
+
+In this situation, I if go on with automating the deployment I'd rather pick the downtime option.
+** WAITING Configure DNS from Terraform
* Must
** Fully deployable from code
Use NixOps and Terraform to fully automate all of the configuration.
@@ -14,14 +30,17 @@ Use NixOps and Terraform to fully automate all of the configuration.
** TODO =mail.euandreh.org=: Email + webmail
** TODO =cloud.euandreh.org=: Nextcloud: storage, calendar, contacts, notes
** TODO =hydra.euandreh.org=: Hydra
+Does Hydra support release management?
** TODO =annex.euandreh.org=: Public content from Git Annex repositories
Only an static file server, with folders for individual assets.
** DONE =wallabag.euandreh.org=: Wallabag
CLOSED: [2019-05-25 Sat 18:02]
** TODO =pi-hole.euandreh.org=: Pi-hole
** TODO =pwk.euandreh.org=: Piwik
-** TODO =git.euandreh.org=: CGit or GitWeb
+** TODO Software development
+*** TODO =git.euandreh.org=: CGit or GitWeb
https://github.com/iconoeugen/docker-gitweb
+*** TODO =cd.euandreh.org=: Hydra
** CANCELLED =perkeep.euandreh.org=: Perkeep
I'm already covered by using Git Annex for almost everything.
** WAITING =matrix.euandreh.org=: Matrix Synapse server