Here's the Docker docs where they say /data/gitea is the folder for customization when using Docker: https://docs.gitea.io/en-us/install-with-docker/#customization
I don’t know what that means. The files live in an actual /custom folder with my local Gitea that I’m developing them in. The docs call that folder /custom. If you put them in the normal data folder, then almost certainly they will overwrite actual Gitea files, instead of adding custom ones in the custom folder.
I think it's not a big change from this PR to achieve that (create ConfigMaps for the entire folder instead of just options/label, copy the mounted files to /data/gitea/, this is what the Gitea docs call /custom). The secrets (app.ini and the dummy TLS cert) will have to be moved respectively to custom/conf and custom/https
Done in eba722992f. I created the labels as ConfigMaps and copied them to the persistent data volume as part of the init container.
This is still the old commit because we're commenting on it, new content is:
My plan was to upload them to the persistent volume, or create a small Docker container that contains these files, whichever makes more sense. kubectl cp can be used to copy files/directories to a container
Local building of images is really easy. Clone https://github.com/go-gitea/gitea and run make docker and you get a image tagged gitea/gitea:latest that you can then push. I'm updating the docs
I didn't realize the load balancers were so expensive. I have only read an introduction to Ingress so far (https://kubernetes.io/docs/concepts/services-networking/ingress/). It seems complex, but worth learning about.
It depends, I think sometimes we'll want to use releases, so official images, and sometimes we'll want an unreleased feature. production tag sounds good
Yes, but a copy of gitea/gitea:latest at the revision we want, instead of always keeping up with their latest. Creating our own images should be a separate issue