Gitea

Install and configure PostgreSQL.

Choose between TCP or UNIX Socket, and jump to the corresponding section.

Create the new user while connecting to the server as postgres user (you will be prompted for a password for the new user):

[postgres]$ createuser -P gitea

Create the Gitea database, owned by user:

[postgres]$ createdb -O gitea gitea

PostgreSQL#Configure PostgreSQL to be accessible from remote hosts

Verify it works:

$ psql --host=ip_address --dbname=gitea --username=gitea --password

Configure Gitea either through the first-run installer or update :

Create the new user while connecting to the server as postgres user:

[postgres]$ createuser gitea

Create the Gitea database, owned by user:

[postgres]$ createdb -O gitea gitea

Setup the Unix socket by adding the following line to :

Restart postgresql.service.

Verify it works:

[gitea]$ psql --dbname=gitea --username=gitea

Configure Gitea either through the first-run installer or update :

/etc/gitea/app.ini

DB_TYPE             = postgres
HOST                = /run/postgresql/
NAME                = gitea
USER                = gitea
PASSWD              =

The following is an example of setting up MariaDB, setting your desired password:

Try connecting to the new database with the new user:

$ mysql -u gitea -p -D gitea

Configure MariaDB either through the first-run installer or update :

With you can use the official cli-client of gitea. More information can be found at https://gitea.com/gitea/tea

Make sure SSH is properly configured and running.

You might want to set SSH_DOMAIN, e.g.:

/etc/gitea/app.ini

SSH_DOMAIN                 = git.domain.tld

By default, Gitea will run as the user ; this account will also be used for ssh repository access. For ssh access to work, you have to enable PAM. Alternatively, you might have to unlock service account.

If you use in your SSH configuration, add to it, e.g.:

Restart if you use it (nothing to do if you use ).

By default, the ability to interact with repositories by HTTP protocol is enabled. You may want to disable HTTP-support if using SSH, by setting to .

If you use the built-in SSH server and want Gitea to bind it on port 22, or if you want to bind Gitea webserver directly on ports 80/443 (that is in a setup without proxy), you will need to add a drop-in systemd unit override:

/etc/systemd/system/gitea.service.d/override.conf

[Service]
AmbientCapabilities=CAP_NET_BIND_SERVICE
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
PrivateUsers=false

In the ui section, you can set the DEFAULT_THEME to for making the web interface use a dark background.

The following is an example of using nginx as reverse proxy for Gitea over unix socket (you need to provide the SSL certificate):

Update the and section of :

For additional information and examples, see the Reverse Proxies section on the Gitea documentation website .

As of now, you cannot use a custom path like as your server home, since the shipped unit file marks everything read-only.

To enable these custom paths, create a drop-in snippet with your server home directory as a new directive:

/etc/systemd/system/gitea.service.d/data-directory.conf

[Service]
ReadWriteDirectories=/srv/gitea

Then do a daemon-reload and restart for the changes to take effect.

A problem can appear after the upgrade to 1.5.0. The service will not start, and the following error is present in the logs:

To fix this problem, run the following command as the `root` user on your MySQL/MariaDB server

gitea should stop complaining about key size and startup properly.