Forgejo

​

Towbar manifest

id: forgejo
name: Forgejo
buildServer: null
deployment:
  type: image
  image: codeberg.org/forgejo/forgejo:16
container:
  port: 3000
  volumes:
    - name: data
      mountPath: /data
      initialData: image
environments:
  production:
    server: 192.0.2.10
rollout:
  type: recreate
  maintenanceMode: true
  reason: Persistent application data uses a single writer
secrets:
  runtime:
    - FORGEJO__server__ROOT_URL
domains:
  primary: forgejo.example.com
tls:
  mode: direct

​

Configure

1. Prepare the example server, connect the repository, and map production to the branch containing these manifests. Replace the example server IP and domain. Commit the manifests, then sync the repository and inspect the resolved configuration.
2. Set the Service’s declared runtime values under Service → Settings → Secrets using the table below. Replace descriptions and placeholders with actual values; do not commit passwords or keys.
3. Keep the Service’s named volumes attached across deployments. Towbar’s Datastore backup policy does not back up Service volumes, so include them in your own recovery plan.
4. Deploy the Service, then perform the checks below before enabling auto-deploy.

​

Runtime values

​

Verify