Configuration¶
Find the Gitea files, listen address, and limits for your instance.
Where things live¶
| Path | What it is |
|---|---|
gitea.service |
Gitea service. |
| Port 8443 | HTTPS UI and API. |
~/.config/sushi/gitea/access.json |
Account file for ubuntu, mode 0600. |
server.crt beside that file |
TLS certificate for this instance. |
sushi-gitea-api |
Helper. It authenticates as the generated administrator without printing credentials. |
/var/lib/gitea |
Repositories and application state. |
/etc/gitea |
Server configuration and the TLS identity. |
/home/ubuntu/.config/sushi/gitea |
Client account files. |
/opt/gitea and /usr/share/doc/gitea |
Installed package and notices. |
The generated administrator name is sushi.
Listen address¶
Forward port 8443 with Session Manager. For a workstation client, copy the certificate and the client credential file over an authenticated channel. Do not put credentials in URLs, command arguments, user data, or support logs. Do not disable certificate verification.
Git clone and push use the credential helper documented in
/opt/sushi/docs/README.md. Run that helper only through Git. Running it
directly prints a secret.
Limits¶
One instance, local repositories, SQLite. Registration, SSH Git hosting, LFS, Actions, and the mailer are disabled. No external database, high availability, public hostname, or DNS automation is configured.
The certificate expires after 365 days. Replace it before expiry. Public DNS and automatic renewal are not included.
The example that creates a repository is in
Getting started. Do not delete
/etc/gitea as a reset.
Last updated November 1, 2026 · Suggest an improvement