Skip to content

v1.1.1 - Host-loopback container deployment fix

Latest
Latest

Choose a tag to compare

View all tags
@NovichekLIS NovichekLIS released this 10 Jul 10:44
v1.1.1
1dedf59

Summary

Patch release for container deployments where Gitea listens only on the Docker host loopback interface.

Fixed

  • Added compose.host-network.example.yml for host-loopback Gitea deployments.
  • Made the Gunicorn bind address configurable with GUNICORN_BIND.
  • Corrected Docker installation guidance: host.docker.internal works only when Gitea listens on an address reachable from Docker bridge networking, not when Gitea is bound only to host 127.0.0.1.

Validation

Full integration smoke was run on a Debian test server with existing Gitea, ONLYOFFICE Document Server, Nginx, and systemd:

  • container build and host-network run with GUNICORN_BIND=127.0.0.1:5005
  • /healthz direct and through Nginx
  • ONLYOFFICE api.js reachability
  • Gitea file page hook delivery
  • folder ZIP through the bridge
  • Gitea OAuth edit flow
  • file proxy download
  • read-only view mode
  • simulated ONLYOFFICE force-save callback and Gitea save-back commit
  • cleanup of temporary test user/repo/container/volume/image and restoration of the original systemd bridge

Security Notes

No deployment secrets are included. Keep .env.docker private and keep /data private. Use one bridge replica unless you add shared state and sticky routing.

Assets 2
Loading