Maintainer documentation for application templates and their configuration is missing
As the developers and administrators of the ecobytes collective can also be considered end users of the infrastructure, their needs for developer experience have also to be taken into account when writing documentation. They will not need an end user manual, but rather a technical reference manual.
Additionally to the services known from #1 (moved) , we'd also do good in documenting the intangible parts of the infrastructure.
-
DNS -
E-Mail -
libre.sh -
Ansible/ZFS provisioning -
Backups -
Monitoring -
Secrets handling -
Repeating procedures -
...
Some pieces of information have previously been collected for:
-
GitLab https://lab.allmende.io/ecobytes/infrastructure/issues/47 -
Discourse https://lab.allmende.io/ecobytes/infrastructure/issues/48 -
Nextcloud https://lab.allmende.io/ecobytes/infrastructure/issues/49 -
Etherpad https://lab.allmende.io/ecobytes/infrastructure/issues/46 -
Piwik https://lab.allmende.io/ecobytes/infrastructure/issues/42 -
Known https://lab.allmende.io/ecobytes/infrastructure/issues/43 -
BOA https://lab.allmende.io/ecobytes/infrastructure/issues/44 -
...
We may want to sufficiently complete these lists and start writing initial explanations.
For the application templates it would be good to have useful documentation as close as possible to upstream.