Initial configuration

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

Database settings

STACKIT Git requires MySQL, PostgreSQL, MSSQL, SQLite3 or TiDB (MySQL protocol).

postgres
MySQL
PostgreSQL
SQLite3
disable
Disable
Require
Verify Full
Leave blank for database default ("public").
File path for the SQLite3 database.
Enter an absolute path if you run STACKIT Git as a service.

General settings

Enter your instance name here. It will be displayed on every page.
Enter your instance slogan here. Leave empty to disable.
Remote Git repositories will be saved to this directory.
Files tracked by Git LFS will be stored in this directory. Leave empty to disable.
The operating system username that STACKIT Git runs as. Note that this user must have access to the repository root path.
Domain or host address for the server.
Port number that will be used by the SSH server. Leave empty to disable SSH server.
Port number that will be used by the STACKIT Git web server.
Base address for HTTP(S) clone URLs and email notifications.
Log files will be written to this directory.
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.
It will periodically check for new STACKIT Git versions by checking a TXT DNS record at release.forgejo.org.

Optional settings

Email settings
Email address STACKIT Git will use. Enter a plain email address or use the "Name" <email@example.com> format.
Server and third-party service settings
Disable third-party content delivery networks and serve all resources locally.
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.
Look up avatars using Libravatar.
Allow users to sign in via OpenID.
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.
Require users to pass CAPTCHA in order to create accounts.
Limit content access to signed-in users. Guests will only be able to visit the authentication pages.
Enable email address hiding for new users by default so that this information is not leaked immediately after signing up.
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.
Allow usage of time tracking feature for new repositories by default.
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".
pbkdf2_hi
pbkdf2
argon2
bcrypt
scrypt
pbkdf2_hi
Set the password hashing algorithm. Algorithms have differing requirements and strengths. 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.

These configuration options will be saved in: /var/lib/gitea/custom/conf/app.ini