Polyer

Gitea

Deploy Gitea on Polyer to run a self-hosted Git service with repositories, issues and pull requests. This template runs a single gitea/gitea:latest service with no separate database; repositories, configuration and any SQLite database live on its /data volume. Review the initial configuration page and plan to use HTTPS remotes.

Git hostingCoolify open catalog

What you can use it for

  • Host private Git repositories with issues, pull requests and code review for a small team.
  • Mirror repositories from other Git hosts to keep your own copy.

What this template creates

giteagitea/gitea:latest
Public endpoint Persistent volume

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

  1. Select Configure deployment and sign in or create an account.
  2. Choose a new or existing project and select an available region.
  3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
  4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Operating this application

  • Complete Gitea's initial configuration page on first visit: choose SQLite unless you connect an external database, confirm the base URL is the generated HTTPS domain and create the administrator account. Disable self-registration there if the instance is not meant to be open.
  • This template publishes Gitea only through its HTTPS endpoint, so clone and push with HTTPS remotes and an access token, and do not rely on the SSH clone URLs Gitea displays.
  • Back up the whole /data volume, which holds repositories, configuration and any SQLite database, and test a restore. The latest tag can move to a new Gitea release that migrates the database, so take a fresh backup before each update.

Hosting costs

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Review prices and estimate resource costs

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-10

Upstream documentation Template source and license

Choose your next step

Related templates