Redbrick-Git

If you run Forgejo inside Docker, please read the documentation before changing any settings.

Forgejo requires MySQL, PostgreSQL, SQLite3 or TiDB (MySQL protocol).

Database type

Host

Username

Password

Database name

SSL

Schema Leave blank for database default ("public").

Path File path for the SQLite3 database.
Enter an absolute path if you run Forgejo as a service.

Instance title Enter your instance name here. It will be displayed on every page.

Instance slogan Enter your instance slogan here. Leave empty to disable.

Repository root path Remote Git repositories will be saved to this directory.

Git LFS root path Files tracked by Git LFS will be stored in this directory. Leave empty to disable.

User to run as The operating system username that Forgejo runs as. Note that this user must have access to the repository root path.

Server domain Domain or host address for the server.

SSH server port Port number that will be used by the SSH server. Leave empty to disable SSH server.

HTTP listen port Port number that will be used by the Forgejo web server.

Base URL Base address for HTTP(S) clone URLs and email notifications.

Log path Log files will be written to this directory.

Disable self-registration

Only instance administrators will be able to create new user accounts. It is highly recommended to keep registration disabled unless you intend to host a public instance for everyone and ready to deal with large amounts of spam accounts.

Enable update checker

It will periodically check for new Forgejo versions by checking a TXT DNS record at release.forgejo.org.

Email settings

SMTP host

SMTP port

Send email as Email address Forgejo will use. Enter a plain email address or use the "Name" <email@example.com> format.

SMTP username

SMTP password

Require email confirmation to register

Enable email notifications

Server and third-party service settings

Enable local mode

Disable third-party content delivery networks and serve all resources locally.

Disable Gravatar

Disable usage of Gravatar or other third-party avatar sources. Default images will be used for user avatars unless they upload their own avatar to the instance.

Enable federated avatars

Look up avatars using Libravatar.

Allow users to sign in via OpenID.

Allow registration only via external services

Users will only be able to create new accounts by using configured external services.

Allow users to create accounts via OpenID if self-registration is enabled.

Enable registration CAPTCHA

Require users to pass CAPTCHA in order to create accounts.

Require to sign-in to view instance content

Limit content access to signed-in users. Guests will only be able to visit the authentication pages.

Hide email addresses by default

Enable email address hiding for new users by default so that this information is not leaked immediately after signing up.

Allow creation of organizations by default

Allow new users to create organizations by default. When this option is disabled, an admin will have to grant a permission for creating organizations to new users.

Enable time tracking by default

Allow usage of time tracking feature for new repositories by default.

Hidden email domain Domain name for users with a hidden email address. For example, the username "joe" will be logged in Git as "joe@noreply.example.org" if the hidden email domain is set to "noreply.example.org".

Password hash algorithm Set the password hashing algorithm. Algorithms have differing requirements and strength. The argon2 algorithm is rather secure but uses a lot of memory and may be inappropriate for small systems.

Administrator account settings

Creating an administrator account is optional. The first registered user will automatically become an administrator.

Administrator username

Email address

Password

Confirm password

These configuration options will be saved in: /data/gitea/conf/app.ini

Initial configuration

Database settings

General settings

Optional settings