So that we can keep one python base image for our python things,
base jinja-init and gitea-init on python-base. Also, tie jinja-init
to python-base in the dependency graph and gitea-init to jinja-init.
This way if python-base updates, we'll rebuild our python images.
Update FROM lines to use full paths to images.
Change-Id: I554bf07fa8e458e443729cf4b8f40d7ceeaafa04
Gitea supports internal TLS termination as well as redirection of
http to https. That may be simpler than terminating in a reverse
proxy. Let's try it.
Also, make the dockerfile match the expectation of the job that
there will be a gitea-init stage.
Also, fix the repository root setting in app.ini.
Change-Id: Ia6b66b53cebdb1afa49fef89a0559615f98052f1
This creates a jinja-init image based on
https://github.com/ObjectifLibre/jinja-init
We can use this image as an "init container" in k8s to template out
config files using configmaps and secrets.
It also adds a gitea-init Dockerfile, which will require the
jinja-init image to be published first.
Change-Id: I88e14c4f0d868f99aa0a0316e6b9e24c2a8fea68
