Overview
Forgejo is useful for community Git forge 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 Forgejo from codeberg.org/forgejo/forgejo:10 on container port 3000.
- Image: codeberg.org/forgejo/forgejo:10
- Port: 3000
- Volumes: /data
Production notes for this catalog app
Treat repositories, issues, and uploaded assets as critical data and include them in backups.
Why host Forgejo with Better-PaaS
Better-PaaS is designed for apps like Forgejo: 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 Forgejo needs. For Forgejo, pay special attention to self-hosted source control with collaboration features.
- 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 Forgejo run with automatic HTTPS?
Yes. Add a domain in Better-PaaS after DNS points to the server and Caddy can issue a certificate.
Does Forgejo need persistent storage?
Most developer tools apps need some persistent storage or database plan. Treat app data and config as something to back up.