We are currently testing around with setting up OpenSlides on k3s. As with k3s deployment definitions are much more verbose, having them all in just one file (as currently done with the docker-compose.yml) would make it very unreadable and also not follow the best practices.
So I implemented the possibility to instead define the template as a directory containing go templates. The structure of that directory is then traversed and go templates are applied. The resulting files will then also be output following the same tree structure.
For this I utilized the FS package and it's FS abstractions. I think perhaps the most questionable changes are those made for backwards compatibility, also see my code comments for details.
@normanjaeckel Can you review this?
We are currently testing around with setting up OpenSlides on k3s. As with k3s deployment definitions are much more verbose, having them all in just one file (as currently done with the
docker-compose.yml) would make it very unreadable and also not follow the best practices. So I implemented the possibility to instead define the template as a directory containing go templates. The structure of that directory is then traversed and go templates are applied. The resulting files will then also be output following the same tree structure. For this I utilized the FS package and it's FS abstractions. I think perhaps the most questionable changes are those made for backwards compatibility, also see my code comments for details.