Developer Tools solution

Run Gitea Locally with FlyEnv

Gitea can use a local database and a reverse proxy or web server for browser access. FlyEnv helps manage those services and Go tooling when a project builds Gitea from source.

Download FlyEnv Official documentation

Local project stack

Services FlyEnv can manage around Gitea

About Gitea

Gitea is a self-hosted Git forge that provides repository hosting, pull requests, issues, actions, packages, and organization management. It is a deployable service with Git-over-SSH and HTTP behavior, not merely a Go project that developers run as an API framework.

A local Gitea instance can use embedded SQLite for a small evaluation, or MySQL, MariaDB, or PostgreSQL for a more representative server setup. Its `app.ini` controls repository storage, SSH, OAuth, mail, actions, and database settings; Go is only necessary when building the service from source.

Core capabilities

Git over SSH and HTTP
Pull requests
Issues and projects
Gitea Actions
Package registry
Organization management

Common use cases

Private team Git hosting
Self-managed CI experimentation
Source control integration testing
Internal package publishing

Gitea combines a forge service with Git transport

A compact evaluation can be one executable plus SQLite, while authentication, actions, and production-like storage add targeted dependencies.

Gitea service and app.ini: Runs the web forge and configures its repositories, SSH port, security settings, and storage.
Database choice: SQLite suits a small local instance; MySQL, MariaDB, or PostgreSQL is used when configured for a shared-style setup.
SSH and local domain: Test clone URLs, SSH keys, webhooks, and browser flows with the same endpoints clients will use.
Optional Actions runner: A runner is required only when validating Gitea Actions workflows.

Project resources

For installation commands, supported versions, and project-specific configuration, refer to the official Gitea documentation.

Typical local stack

The exact services depend on the project, its release, and its local configuration. This is a common local setup, not a fixed requirement.

Component	Typical role
Gitea service	Runs the self-hosted Git application.
MySQL MariaDB PostgreSQL	May store application data when SQLite is not used.
Nginx Caddy	May proxy a local Git service domain.
Go	May be needed when building from source.

How FlyEnv helps

Manage data services
Run the database selected by the Gitea configuration.
Use Go when building source
Keep Go tooling available for source-based workflows.
Configure secure local access
Use a local domain and HTTPS for web and Git clients.
Keep the service stack grouped
Start Gitea and its selected services together.

Set up the local environment

Project installation stays with the upstream documentation. FlyEnv manages the runtimes, databases, web servers, and supporting services around it.

1Use the official Gitea documentation for installation and server configuration.
2Start a database only when the Gitea configuration does not use SQLite.
3Select Go when the workflow builds Gitea from source.
4Configure a local reverse proxy and domain when browser access needs one.
5Enable local HTTPS when Git clients or web integrations need a secure origin.
6Save the service and its dependencies in a Startup Group when useful.