Gitea hosting: a Git server for your team, in one click
Pick Gitea from the app catalog, name it, deploy. The first visit shows Gitea's setup page, already pointed at your address; after that it is your GitHub, on a Starter plan with 1 GB.
What you get
- The official rootless Gitea image with ROOT_URL set to your address, so links and webhooks are right from the start.
- Repositories, pull requests, issues, wikis, a package registry and Gitea Actions.
- Everything under /data, backed up daily and restored in one click.
- Redeploy pulls the latest Gitea release.
Cloning and pushing
Over https at your address, with a token or your password. The SSH port is not exposed, since the address is https only; https remotes work with every Git client and with Actions.
Sizing
Gitea itself is light; what needs room is the work: a few active repositories fit in Starter's 1 GB, a team with Actions runners and large monorepos wants Standard or Pro. Disk under /data is 5 GB on Starter and 10 and 20 GB on the tiers above; a Git server fills it slower than you think.
Frequently asked questions
Is it GitHub-compatible?
Gitea speaks the same Git, has the same pull-request model and a compatible API for most tools; the FadeHost Deploy button and auto-deploy work with GitHub and GitLab repositories, not with your Gitea yet.
Can I use SSH remotes?
Not through the web address, which carries https only. Use https remotes with a token; they work everywhere, including from CI.
Where is the database?
SQLite under /data by default, which suits a small team. For a bigger one, create a managed PostgreSQL from the Databases page and pick it on Gitea's setup page.
What happens on a deploy?
The repository is cloned at your branch, dependencies install, the build runs when there is one, the app starts. With auto-deploy on, every push does the same. The live console shows each step; a failed one is explained in plain words.