If you’re the only user, you can avoid almost all the security issues by not exposing any HTTP ports to the internet, and instead accessing any web interfaces t

If you’re the only user, you can avoid almost all the security issues by not exposing any HTTP ports to the internet, and instead accessing any web interfaces through SSH port forwarding. For example: 1. Run Gitea on your server, but make it only available on localhost. 2. Connect to your server via SSH, and use the -L flag to forward the port that Gitea is using e.g. ssh -L 8888:localhost:8888 me@myserver.com 3. Access Gitea by opening http://localhost:8888 http://localhost:8888 (or whatever port you’re using) in your browser. However, this doesn’t work if you’d like to collaborate with anyone who you don’t trust enough to give SSH access to your machine. It would also be annoying or impossible to open the web interfaces on mobile devices.