Aller au contenu principal
Development

Self-host Forgejo on a VPS

A community-governed, lightweight Git forge.

A fork of Gitea with a community-first governance model — Git hosting, issues, pull requests and CI in a small binary.

Why self-host Forgejo?

Forgejo offers Gitea’s lightweight footprint with community governance, appealing if you want the project’s direction to be independent.

How to install Forgejo

  1. 1

    Provision a VPS

    Pick a Debian/Ubuntu template and get root SSH in about a minute.

  2. 2

    Install the runtime

    Install Single binary + PostgreSQL/SQLite.

  3. 3

    Deploy the application

    Net what you need from the project’s official source and run it.

  4. 4

    Put it behind TLS

    Reverse-proxy with Nginx and issue a Let’s Encrypt certificate.

  5. 5

    Add it to your backups

    Include the data directory and database in your backup routine before you rely on it.

Practical tips

  • Give Forgejo its own database user with rights only on its own schema.
  • Reverse-proxy Forgejo and terminate TLS at the proxy so certificates are managed in one place.
  • Take a VPS snapshot before major upgrades so you can roll back cleanly.
  • Keep Forgejo patched — most self-hosting incidents are unpatched software.

Frequently asked questions

How much RAM does Forgejo need?
Plan on 1–2 GB for typical use; add headroom if you expect many concurrent users.
What stack does Forgejo run on?
Single binary + PostgreSQL/SQLite.
Can I run other things on the same VPS?
Yes — size the plan so Forgejo plus your other workloads fit in RAM with room to spare.

Looking for something else? Popular alternatives include Gitea, GitLab CE, SourceHut — browse all app guides.