|
|
|
@ -171,11 +171,24 @@ In general, these have all been thought about and seem to be solveable
|
|
|
|
but still need more specific technical solutions.
|
|
|
|
but still need more specific technical solutions.
|
|
|
|
|
|
|
|
|
|
|
|
- backups
|
|
|
|
- backups
|
|
|
|
- logging
|
|
|
|
|
|
|
|
|
|
|
|
The storage volume used on digital ocean already provides redudancy.
|
|
|
|
|
|
|
|
To provide complete, offsite backups, the /nassella folder just needs
|
|
|
|
|
|
|
|
to be backed up. (Could be something like just rsync or tarsnap, etc),
|
|
|
|
|
|
|
|
along with providing a backup of the config and terraform files internally
|
|
|
|
|
|
|
|
or via an "export" option.
|
|
|
|
|
|
|
|
- +logging+
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Resolved for now with the [[https://dozzle.dev/][dozzle]] service
|
|
|
|
- monitoring / alerting
|
|
|
|
- monitoring / alerting
|
|
|
|
- exporting
|
|
|
|
- exporting
|
|
|
|
- migrating between platform providers (VPS providers, etc)
|
|
|
|
- migrating between platform providers (VPS providers, etc)
|
|
|
|
- updating
|
|
|
|
- updating
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Not fully implemented yet, but should be no more than updating docker
|
|
|
|
|
|
|
|
versions in the compose file and re-running ~make apply~ for each user.
|
|
|
|
|
|
|
|
Of course, long-term there should be an automated CI system to test all
|
|
|
|
|
|
|
|
apps after upgrading.
|
|
|
|
- CI system
|
|
|
|
- CI system
|
|
|
|
- docs/auto-setup for app features
|
|
|
|
- docs/auto-setup for app features
|
|
|
|
|
|
|
|
|
|
|
|
|
