Gitea SSL with Apache as reverse proxy
We want to host a nice and secure container registry - to push docker images there and our kubernetes cluster would pull them from this registry. So came the idea to use the gitea over ssl. Part of Developer Tools: The Complete Guide to Modern Development Workflows 1) Gitea already has container registry 2) Apache as TLS terminating proxy will add HTTPS to our Gitea. 3) That how it's started...…
The objective is to host a secure container registry using Gitea with SSL, reverse-proxying through Apache. Gitea already includes a container registry feature. Apache will be used as a TLS terminating proxy to provide HTTPS access to Gitea's registry.
The process begins by installing Apache and setting up a test site. Firewall settings are adjusted to allow access via HTTPS on port 443. Apache configuration files are edited to create a virtual host and enable necessary modules. A simple web page is created at the virtual host's document root.
Next, Gitea's SSL setup is configured to enable HTTPS access. Apache is then configured as an insecure reverse proxy, pointing to the Gitea instance running on port 3000. The necessary Apache modules are enabled and Apache is restarted. Accessing the server via HTTP or HTTPS confirms that the reverse proxy is functioning correctly.
In conclusion, this guide outlines the steps needed to successfully set up a secure container registry using Gitea, reverse-proxied through Apache. Key aspects include installing Apache, configuring SSL, setting up a virtual host, and properly configuring Apache as a proxy to the Gitea registry.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
