Open the server Apps tab
Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.


Community-driven Gitea fork
Add your server credentials to Server Compass
Choose from our template library
Fill in settings and click Deploy
Use the Forgejo template in Server Compass to deploy a self-hosted Git service with PostgreSQL on your VPS, then verify the Forgejo initial configuration screen in a browser.
Select the tutorial-vps VPS, open the Apps tab, and start a new app deployment. Keep sensitive server details hidden before capturing or sharing screenshots.

Click New App and choose the template deployment path so Server Compass can load the built-in catalog.

Use the template picker search to find Forgejo in the Server Compass template catalog.

Choose the Forgejo template. Server Compass fills the Forgejo service, PostgreSQL service, persistent Git data and database volumes, and the required database password.

Confirm the app name and compose services. In this run, the app was named forgejo-demo and used host port 3001.

Review the generated environment values, keep the database password masked, confirm the web and SSH ports are available, and click Deploy Now.

Keep the deployment modal open while Server Compass uploads the compose file, pulls the Forgejo and PostgreSQL images, starts the containers, and verifies the stack.

After deployment finishes, return to the Apps tab and confirm the Forgejo app is marked Running with its application URL available.

Click Open Application or open the application URL in a browser. The Forgejo initial configuration screen confirms the deployed Git service is reachable and ready for final setup.

The Forgejo app loaded successfully in a browser and displayed the initial configuration screen.
It deploys the official Forgejo container with PostgreSQL 16, a persistent Forgejo data volume, a persistent database volume, web access on port 3000, and Git SSH access on port 2222 by default.
The tutorial used host port 3001, which maps to the Forgejo web UI on container port 3000.
A fresh Forgejo deployment is considered reachable when the initial configuration screen loads. Completing the wizard creates real administrator credentials, so the public guide stops before account creation.
No. The deployment guide should live on the Forgejo template detail page and be linked from the reusable template deployment docs page.
Deploy Forgejo the traditional way with SSH and Docker Compose.
Open a terminal session and log into your VPS. Replace the placeholder with your actual IP.
# Connect via SSH
ssh root@your-vps-ip
# Alternative with key file
ssh -i /path/to/key root@your-vps-ipFirst time? Make sure Docker is installed on your VPS. Run: curl -fsSL https://get.docker.com | sh
Create a workspace for your deployment files.
# Create and navigate to project directory
mkdir -p ~/apps/forgejo
cd ~/apps/forgejoConfigure your containers with this Docker Compose setup:
services:
forgejo:
image: codeberg.org/forgejo/forgejo:7
ports:
- "3000:3000"
- "2222:22"
environment:
- USER_UID=1000
- USER_GID=1000
- FORGEJO__database__DB_TYPE=postgres
- FORGEJO__database__HOST=db:5432
- FORGEJO__database__NAME=forgejo
- FORGEJO__database__USER=forgejo
- FORGEJO__database__PASSWD=<your-db-password>
volumes:
- forgejo_data:/data
restart: unless-stopped
depends_on:
db:
condition: service_healthy
db:
image: postgres:16-alpine
environment:
- POSTGRES_USER=forgejo
- POSTGRES_PASSWORD=<your-db-password>
- POSTGRES_DB=forgejo
volumes:
- postgres_data:/var/lib/postgresql/data
restart: unless-stopped
healthcheck:
test: ["CMD-SHELL", "pg_isready -U forgejo"]
interval: 10s
timeout: 5s
retries: 5
volumes:
forgejo_data:
postgres_data:
PORTWeb port(default: 3000)SSH_PORTSSH port(default: 2222)DB_PASSWORDDB passwordSpin up the containers and verify the deployment.
# Start all services
docker compose up -d
# List running containers
docker compose ps
# Watch the logs
docker compose logs -fAllow incoming traffic on the application port.
# Allow the application port through firewall
sudo ufw allow 3000/tcp
sudo ufw reload
# Access your app at:
# http://your-server-ip:3000Server Compass makes deploying Forgejo effortless. Visual setup, one-click deploy, done.
After deploying Forgejo with Server Compass, complete these steps to finish setup
Complete installation wizard
Create admin account
Create repos
Need help? Check out our documentation for detailed guides.
Common questions about self-hosting Forgejo
Simply download Server Compass, connect to your VPS, and select Forgejo from the templates list. Fill in the required configuration and click Deploy. The entire process takes under 3 minutes.
Forgejo requires a minimum of 256MB RAM. We recommend a VPS with at least 1024MB RAM for optimal performance. Any modern Linux server with Docker support will work.
Yes! Server Compass provides volume mapping that allows you to import existing data. You can also use standard Forgejo backup and restore procedures.
Server Compass makes updates easy. Simply click the Update button in your deployment dashboard, and the latest Forgejo image will be pulled and deployed with zero downtime.
Forgejo is open-source software. You only pay for your VPS hosting (typically $5-20/month) and optionally Server Compass ($29 one-time). No subscription fees or per-seat pricing.

Open-source backend in a single file with realtime database, auth, and file storage

Open-source backend-as-a-service - self-hosted Firebase alternative

Open-source backend framework with dashboard

Full Supabase self-hosted with Kong, GoTrue Auth, Realtime, and Studio
Download Server Compass and deploy Forgejo to your VPS in under 3 minutes. No Docker expertise required.
Download Server Compass