Open 0xEAB opened 10 months ago
I doubt this could reduce the bloat in this repo for adding new images as we’d still want to store the generated Dockerfiles somewhere and pin versions together. E.g. there’s likely no good reason to build an image with future DMD 2.150 on an OS version from now. Also we don’t want to create a always growing matrix of systems × compilers.
I particularly dislike the Bash and GNU/Busybox magic certain other Docker image repos use to generate their recipes. I’d prefer to have a novice-readable script in Python or something. (Pero no hablo Python…)
j2 is probably the most well-known: https://pypi.org/project/Jinja2/. I still would like generated dockerfiles to be committed or at least released.
I still would like generated dockerfiles to be committed or at least released.
would it make sense to create a “release” branch that includes the CI/CD generated dockerfiles?
That makes sense yeah, should work nicely.
Should we use a template engine to generate image recipes?