Forgejo is a self-hosted Git forge (code hosting, issues, pull requests, wikis). This repository packages it as a Cloud in a Bottle app.
- Forgejo running on
https://forgejo.<zone>/. - Public landing page: anyone can browse public repos and the explore page.
- Owner logged in as admin automatically via Cloud in a Bottle SSO.
- Invited users log in with Forgejo-local passwords (accounts created by the admin).
- Walk-in registration disabled. New accounts require admin action.
- Git over HTTPS (SSH disabled). Authenticate with personal access tokens.
- Issues, pull requests, releases, wikis, webhooks, organizations.
Open https://forgejo.<zone>/. As the Cloud in a Bottle owner you are logged
in automatically as the admin user. Your Forgejo username matches your Cloud in
a Bottle username.
To invite collaborators:
- Go to Site Administration, User Accounts, Create User Account.
- Set a temporary password and hand it to the user out of band.
- They log in at
/user/loginand change the password in their settings.
Git operations use HTTPS. Create a personal access token under Settings, Applications, then use it as the password when cloning or pushing.
- SSH is disabled. Use HTTPS + personal access tokens for git.
- No SMTP configured. Email features (activation links, password reset, notification delivery) do not work without adding SMTP settings.
- Walk-in registration returns 403. Accounts must be admin-created.
All persistent data lives under $OPENHOST_APP_DATA_DIR/:
gitea/forgejo.db: SQLite database (users, repos, issues, settings)gitea/conf/app.ini: effective configurationgit/repositories/: bare git repos.secret_key: generated on first boot, persisted
About 512 MB RAM and 0.5 CPU cores.
Forgejo is licensed under the GNU General Public License v3.0 (GPL-3.0). The container image built from this repo is distributed under that license. The packaging files original to this repository are additionally available under the MIT License. See LICENSE and NOTICE for details.