Long-term support for v1 mainline
As expressed in an early pad from 9. April 2018 and through discussing the once rejected merge request about Changing deployment patterns for more generalised use cases (!159) · Merge Requests · libre.sh / compose.libre.sh, we ask ourselves about implications for long-term support of the v1 mainline of libre.sh.
Internal developments in ecobytes (1) currently show differences around integration of
- ZFS
- Ansible
- different internal and edge routing
- different TLS termination and load balancing plus
- different backup procedure
to what is recorded here.
Also there is the use case of using GitLab CI/CD with something like
GitLab Pages + Let's Encrypt-
Dokku static pagesor - a compose.libre.sh webhook/git adapter
to update static sites (2).
We would like to see these developments happen in an open process. For this we would love to hear your thoughts on modularising the existing code base and establishing good software development practice around the tool, while keeping everything as general as possible for a wide range of use cases.