Overview
Gitea is useful for lightweight Git hosting. Better-PaaS gives it a practical home on your own server with a one-click app workflow, domain routing, HTTPS, logs, and persistent storage habits.
Catalog image and ports
Better-PaaS deploys Gitea from gitea/gitea:1 on container port 3000.
- Image: gitea/gitea:1
- Port: 3000
- Volumes: /data
- Key env vars: USER_UID, USER_GID
Production notes for this catalog app
Git hosting benefits from persistent storage and a clear backup/restore plan before teams depend on it.
Why host Gitea with Better-PaaS
Better-PaaS is designed for apps like Gitea: small services that need reliable routing, a domain, persistent data, and quick redeploys without manually editing reverse proxy files.
Deployment checklist
Before going live, decide the domain, persistent volume, backup cadence, and any environment variables Gitea needs. For Gitea, pay special attention to repositories, issues, pull requests, and packages.
- Choose the app catalog template or Docker image
- Add required environment variables
- Attach a persistent volume if data must survive redeploys
- Deploy and inspect logs
- Add a custom domain after the app is healthy
Operations after launch
Watch logs during the first deploy, confirm storage survives a redeploy, and include the app data in server backups. If the service exposes an admin area, use a strong password and restrict access where appropriate.
FAQ
Can Gitea run with automatic HTTPS?
Yes. Add a domain in Better-PaaS after DNS points to the server and Caddy can issue a certificate.
Does Gitea need persistent storage?
Most developer tools apps need some persistent storage or database plan. Treat app data and config as something to back up.