mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2025-10-19 02:43:18 +00:00
fix; replace Gitea -> Forgejo in app.example.ini where easily possible (#9721)
This PR changes the mentions of *Gitea* to *Forgejo* in the `app.example.ini` file if it is easily possible, like where the application itself is named, or where the binary is referenced. Corresponding issue: https://codeberg.org/forgejo/forgejo/issues/9715 Things that are explicitly not changed and are not in the scope of this PR: * URLs where there is no equivalent for Forgejo * Names of variables * Default values of variables ## Checklist ### Tests - No testable code was changed ### Documentation - No user-facing documentation was changed ### Release notes * *Is it worth mentioning? I don’t know, I leave this up to the release team.* - [ ] I do not want this change to show in the release notes. - [ ] I want the title to show in the release notes with a link to this pull request. - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/9721 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Co-authored-by: Dirk <dirk@0x7be.de> Co-committed-by: Dirk <dirk@0x7be.de>
This commit is contained in:
Dirk
Earl Warren
parent
5b13c6e024
commit
e20c674560
1 changed files with 44 additions and 44 deletions
|
|
@ -12,10 +12,10 @@
|
|||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;
|
||||
;; These values are environment-dependent but form the basis of a lot of values. They will be
|
||||
;; reported as part of the default configuration when running `gitea help` or on start-up. The order they are emitted there is slightly different but we will list them here in the order they are set-up.
|
||||
;; reported as part of the default configuration when running `forgejo help` or on start-up. The order they are emitted there is slightly different but we will list them here in the order they are set-up.
|
||||
;;
|
||||
;; - _`AppPath`_: This is the absolute path of the running gitea binary.
|
||||
;; - _`AppWorkPath`_: This refers to "working path" of the `gitea` binary. It is determined by using the first set thing in the following hierarchy:
|
||||
;; - _`AppPath`_: This is the absolute path of the running Forgejo binary.
|
||||
;; - _`AppWorkPath`_: This refers to "working path" of the `forgejo` binary. It is determined by using the first set thing in the following hierarchy:
|
||||
;; - The "WORK_PATH" option in "app.ini" file
|
||||
;; - The `--work-path` flag passed to the binary
|
||||
;; - The environment variable `$GITEA_WORK_DIR`
|
||||
|
|
@ -54,7 +54,7 @@ APP_NAME = ; Forgejo: Beyond coding. We Forge.
|
|||
RUN_USER = ; git
|
||||
;;
|
||||
;; Application run mode, affects performance and debugging: "dev" or "prod", default is "prod"
|
||||
;; Mode "dev" makes Gitea easier to develop and debug, values other than "dev" are treated as "prod" which is for production use.
|
||||
;; Mode "dev" makes Forgejo easier to develop and debug, values other than "dev" are treated as "prod" which is for production use.
|
||||
;RUN_MODE = prod
|
||||
;;
|
||||
;; The working directory, see the comment of AppWorkPath above
|
||||
|
|
@ -127,7 +127,7 @@ RUN_USER = ; git
|
|||
;; Permission for unix socket
|
||||
;UNIX_SOCKET_PERMISSION = 666
|
||||
;;
|
||||
;; Local (DMZ) URL for Gitea workers (such as SSH update) accessing web service. In
|
||||
;; Local (DMZ) URL for Forgejo workers (such as SSH update) accessing web service. In
|
||||
;; most cases you do not need to change the default value. Alter it only if
|
||||
;; your SSH server node is not the same as HTTP node. For different protocol, the default
|
||||
;; values are different. If `PROTOCOL` is `http+unix`, the default value is `http://unix/`.
|
||||
|
|
@ -169,11 +169,11 @@ RUN_USER = ; git
|
|||
;; Root path of SSH directory, default is '~/.ssh', but you have to use '/home/git/.ssh'.
|
||||
;SSH_ROOT_PATH =
|
||||
;;
|
||||
;; Gitea will create a authorized_keys file by default when it is not using the internal ssh server
|
||||
;; Forgejo will create a authorized_keys file by default when it is not using the internal ssh server
|
||||
;; If you intend to use the AuthorizedKeysCommand functionality then you should turn this off.
|
||||
;SSH_CREATE_AUTHORIZED_KEYS_FILE = true
|
||||
;;
|
||||
;; Gitea will create a authorized_principals file by default when it is not using the internal ssh server
|
||||
;; Forgejo will create a authorized_principals file by default when it is not using the internal ssh server
|
||||
;; If you intend to use the AuthorizedPrincipalsCommand functionality then you should turn this off.
|
||||
;SSH_CREATE_AUTHORIZED_PRINCIPALS_FILE = true
|
||||
;;
|
||||
|
|
@ -198,7 +198,7 @@ RUN_USER = ; git
|
|||
;; default is the system temporary directory.
|
||||
;SSH_KEY_TEST_PATH =
|
||||
;;
|
||||
;; Use `ssh-keygen` to parse public SSH keys. The value is passed to the shell. By default, Gitea does the parsing itself.
|
||||
;; Use `ssh-keygen` to parse public SSH keys. The value is passed to the shell. By default, Forgejo does the parsing itself.
|
||||
;SSH_KEYGEN_PATH =
|
||||
;;
|
||||
;; Enable SSH Authorized Key Backup when rewriting all keys, default is false
|
||||
|
|
@ -220,9 +220,9 @@ RUN_USER = ; git
|
|||
;; E.g."ssh-<algorithm> <key>". or "ssh-<algorithm> <key1>, ssh-<algorithm> <key2>".
|
||||
;; For more information see "TrustedUserCAKeys" in the sshd config manpages.
|
||||
;SSH_TRUSTED_USER_CA_KEYS =
|
||||
;; Absolute path of the `TrustedUserCaKeys` file gitea will manage.
|
||||
;; Absolute path of the `TrustedUserCaKeys` file Forgejo will manage.
|
||||
;; Default this `RUN_USER`/.ssh/gitea-trusted-user-ca-keys.pem
|
||||
;; If you're running your own ssh server and you want to use the gitea managed file you'll also need to modify your
|
||||
;; If you're running your own ssh server and you want to use the Forgejo managed file you'll also need to modify your
|
||||
;; sshd_config to point to this file. The official docker image will automatically work without further configuration.
|
||||
;SSH_TRUSTED_USER_CA_KEYS_FILENAME =
|
||||
;;
|
||||
|
|
@ -277,7 +277,7 @@ RUN_USER = ; git
|
|||
;; Manual TLS settings: (Only applicable if ENABLE_ACME=false)
|
||||
;;
|
||||
;; Generate steps:
|
||||
;; $ ./gitea cert -ca=true -duration=8760h0m0s -host=myhost.example.com
|
||||
;; $ ./forgejo cert -ca=true -duration=8760h0m0s -host=myhost.example.com
|
||||
;;
|
||||
;; Or from a .pfx file exported from the Windows certificate store (do
|
||||
;; not forget to export the private key):
|
||||
|
|
@ -288,7 +288,7 @@ RUN_USER = ; git
|
|||
;KEY_FILE = https/key.pem
|
||||
;;
|
||||
;; Root directory containing templates and static files.
|
||||
;; default is the path where Gitea is executed
|
||||
;; default is the path where Forgejo is executed
|
||||
;STATIC_ROOT_PATH = ; Will default to the built-in value _`StaticRootPath`_
|
||||
;;
|
||||
;; Default path for App data
|
||||
|
|
@ -302,7 +302,7 @@ RUN_USER = ; git
|
|||
;; For "serve" command it dumps to disk at PPROF_DATA_PATH as (cpuprofile|memprofile)_<username>_<temporary id>
|
||||
;ENABLE_PPROF = false
|
||||
;;
|
||||
;; PPROF_DATA_PATH, use an absolute path when you start gitea as service
|
||||
;; PPROF_DATA_PATH, use an absolute path when you start Forgejo as service
|
||||
;PPROF_DATA_PATH = data/tmp/pprof ; Path is relative to _`AppWorkPath`_
|
||||
;;
|
||||
;; Landing page, can be "home", "explore", "organizations", "login", or any URL such as "/org/repo" or even "https://anotherwebsite.com"
|
||||
|
|
@ -374,7 +374,7 @@ DB_TYPE = sqlite3
|
|||
;USER = root
|
||||
;PASSWD = ;Use PASSWD = `your password` for quoting if you use special characters in the password.
|
||||
;SSL_MODE = false ; either "false" (default), "true", or "skip-verify"
|
||||
;CHARSET_COLLATION = ; Empty as default, Gitea will try to find a case-sensitive collation. Don't change it unless you clearly know what you need.
|
||||
;CHARSET_COLLATION = ; Empty as default, Forgejo will try to find a case-sensitive collation. Don't change it unless you clearly know what you need.
|
||||
;;
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;
|
||||
|
|
@ -440,7 +440,7 @@ SECRET_KEY =
|
|||
;; This key is VERY IMPORTANT. If you lose it, the data encrypted by it (like 2FA secret) can't be decrypted anymore.
|
||||
;SECRET_KEY_URI = file:/etc/gitea/secret_key
|
||||
;;
|
||||
;; Secret used to validate communication within Gitea binary.
|
||||
;; Secret used to validate communication within Forgejo binary.
|
||||
INTERNAL_TOKEN =
|
||||
;;
|
||||
;; Alternative location to specify internal token, instead of this file; you cannot specify both this and INTERNAL_TOKEN, and must pick one
|
||||
|
|
@ -474,9 +474,9 @@ INTERNAL_TOKEN =
|
|||
;;
|
||||
;; Set to false to allow users with git hook privileges to create custom git hooks.
|
||||
;; Custom git hooks can be used to perform arbitrary code execution on the host operating system.
|
||||
;; This enables the users to access and modify this config file and the Gitea database and interrupt the Gitea service.
|
||||
;; By modifying the Gitea database, users can gain Gitea administrator privileges.
|
||||
;; It also enables them to access other resources available to the user on the operating system that is running the Gitea instance and perform arbitrary actions in the name of the Gitea OS user.
|
||||
;; This enables the users to access and modify this config file and the Forgejo database and interrupt the Forgejo service.
|
||||
;; By modifying the Forgejo database, users can gain Forgejo administrator privileges.
|
||||
;; It also enables them to access other resources available to the user on the operating system that is running the Forgejo instance and perform arbitrary actions in the name of the Forgejo OS user.
|
||||
;; WARNING: This maybe harmful to you website or your operating system.
|
||||
;; WARNING: Setting this to true does not change existing hooks in git repos; adjust it before if necessary.
|
||||
;DISABLE_GIT_HOOKS = true
|
||||
|
|
@ -484,7 +484,7 @@ INTERNAL_TOKEN =
|
|||
;; Set to true to disable webhooks feature.
|
||||
;DISABLE_WEBHOOKS = false
|
||||
;;
|
||||
;; Set to false to allow pushes to gitea repositories despite having an incomplete environment - NOT RECOMMENDED
|
||||
;; Set to false to allow pushes to Forgejo repositories despite having an incomplete environment - NOT RECOMMENDED
|
||||
;ONLY_ALLOW_PUSH_IF_GITEA_ENVIRONMENT_SET = true
|
||||
;;
|
||||
;;Comma separated list of character classes required to pass minimum complexity.
|
||||
|
|
@ -545,7 +545,7 @@ ENABLED = true
|
|||
;; The file must contain a RSA or ECDSA private key in the PKCS8 format. If no key exists a 4096 bit key will be created for you.
|
||||
;JWT_SIGNING_PRIVATE_KEY_FILE = jwt/private.pem
|
||||
;;
|
||||
;; OAuth2 authentication secret for access and refresh tokens, change this yourself to a unique string. CLI generate option is helpful in this case. https://docs.gitea.io/en-us/command-line/#generate
|
||||
;; OAuth2 authentication secret for access and refresh tokens, change this yourself to a unique string. CLI generate option is helpful in this case. https://forgejo.org/docs/latest/admin/command-line/#generate-secret
|
||||
;; This setting is only needed if JWT_SIGNING_ALGORITHM is set to HS256, HS384 or HS512.
|
||||
;JWT_SECRET =
|
||||
;;
|
||||
|
|
@ -670,7 +670,7 @@ LEVEL = Info
|
|||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;
|
||||
;; The path of git executable. If empty, Gitea searches through the PATH environment.
|
||||
;; The path of git executable. If empty, Forgejo searches through the PATH environment.
|
||||
;PATH =
|
||||
;;
|
||||
;; The HOME directory for Git
|
||||
|
|
@ -755,17 +755,17 @@ LEVEL = Info
|
|||
;; Whether a new user needs to be confirmed manually after registration. (Requires `REGISTER_EMAIL_CONFIRM` to be disabled.)
|
||||
;REGISTER_MANUAL_CONFIRM = false
|
||||
;;
|
||||
;; List of domain names that are allowed to be used to register on a Gitea instance, wildcard is supported
|
||||
;; eg: gitea.io,example.com,*.mydomain.com
|
||||
;; List of domain names that are allowed to be used to register on a Forgejo instance, wildcard is supported
|
||||
;; eg: forgejo.org,example.com,*.mydomain.com
|
||||
;EMAIL_DOMAIN_ALLOWLIST =
|
||||
;;
|
||||
;; Comma-separated list of domain names that are not allowed to be used to register on a Gitea instance, wildcard is supported
|
||||
;; Comma-separated list of domain names that are not allowed to be used to register on a Forgejo instance, wildcard is supported
|
||||
;EMAIL_DOMAIN_BLOCKLIST =
|
||||
;;
|
||||
;; Disallow registration, only allow admins to create accounts.
|
||||
;DISABLE_REGISTRATION = false
|
||||
;;
|
||||
;; Allow registration only using gitea itself, it works only when DISABLE_REGISTRATION is false
|
||||
;; Allow registration only using Forgejo itself, it works only when DISABLE_REGISTRATION is false
|
||||
;ALLOW_ONLY_INTERNAL_REGISTRATION = false
|
||||
;;
|
||||
;; Allow registration only using third-party services, it works only when DISABLE_REGISTRATION is false
|
||||
|
|
@ -777,7 +777,7 @@ LEVEL = Info
|
|||
;; Mail notification
|
||||
;ENABLE_NOTIFY_MAIL = false
|
||||
;;
|
||||
;; This setting enables gitea to be signed in with HTTP BASIC Authentication using the user's password
|
||||
;; This setting enables Forgejo to be signed in with HTTP BASIC Authentication using the user's password
|
||||
;; If you set this to false you will not be able to access the tokens endpoints on the API with your password
|
||||
;; Please note that setting this to false will not disable OAuth Basic or Basic authentication using a token
|
||||
;ENABLE_BASIC_AUTHENTICATION = true
|
||||
|
|
@ -1012,7 +1012,7 @@ LEVEL = Info
|
|||
;; Close issues as long as a commit on any branch marks it as fixed
|
||||
;DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH = false
|
||||
;;
|
||||
;; Allow users to push local repositories to Gitea and have them automatically created for a user or an org
|
||||
;; Allow users to push local repositories to Forgejo and have them automatically created for a user or an org
|
||||
;ENABLE_PUSH_CREATE_USER = false
|
||||
;ENABLE_PUSH_CREATE_ORG = false
|
||||
;;
|
||||
|
|
@ -1076,7 +1076,7 @@ LEVEL = Info
|
|||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;
|
||||
;; Path for local repository copy. Defaults to `tmp/local-repo` (content gets deleted on gitea restart)
|
||||
;; Path for local repository copy. Defaults to `tmp/local-repo` (content gets deleted on Forgejo restart)
|
||||
;LOCAL_COPY_PATH = tmp/local-repo
|
||||
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
|
|
@ -1088,7 +1088,7 @@ LEVEL = Info
|
|||
;; Whether repository file uploads are enabled. Defaults to `true`
|
||||
;ENABLED = true
|
||||
;;
|
||||
;; Path for uploads. Defaults to `data/tmp/uploads` (content gets deleted on gitea restart)
|
||||
;; Path for uploads. Defaults to `data/tmp/uploads` (content gets deleted on Forgejo restart)
|
||||
;TEMP_PATH = data/tmp/uploads
|
||||
;;
|
||||
;; Comma-separated list of allowed file extensions (`.zip`), mime types (`text/plain`) or wildcard type (`image/*`, `audio/*`, `video/*`). Empty value or `*/*` allows all types.
|
||||
|
|
@ -1187,7 +1187,7 @@ LEVEL = Info
|
|||
;; Sets the default trust model for repositories. Options are: collaborator, committer, collaboratorcommitter
|
||||
;DEFAULT_TRUST_MODEL = collaborator
|
||||
;;
|
||||
;; Determines when gitea should sign the initial commit when creating a repository
|
||||
;; Determines when Forgejo should sign the initial commit when creating a repository
|
||||
;; Either:
|
||||
;; - never
|
||||
;; - pubkey: only sign if the user has a pubkey
|
||||
|
|
@ -1301,7 +1301,7 @@ LEVEL = Info
|
|||
;; Whether the email of the user should be shown in the Explore Users page
|
||||
;SHOW_USER_EMAIL = true
|
||||
;;
|
||||
;; Set the default theme for the Gitea install
|
||||
;; Set the default theme for the Forgejo install
|
||||
;DEFAULT_THEME = forgejo-auto
|
||||
;;
|
||||
;; All available themes. Allow users select personalized themes regardless of the value of `DEFAULT_THEME`.
|
||||
|
|
@ -1706,10 +1706,10 @@ LEVEL = Info
|
|||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;
|
||||
;; NOTICE: this section is for Gitea 1.18 and later. If you are using Gitea 1.17 or older,
|
||||
;; NOTICE: this section is for Forgejo 1.18 and later. If you are using Forgejo 1.17 or older,
|
||||
;; please refer to
|
||||
;; https://github.com/go-gitea/gitea/blob/release/v1.17/custom/conf/app.example.ini
|
||||
;; https://github.com/go-gitea/gitea/blob/release/v1.17/docs/content/doc/advanced/config-cheat-sheet.en-us.md
|
||||
;; https://codeberg.org/forgejo/forgejo/src/commit/8769df117d6cc2f4ab00d6e1d54ef4241d063f11/custom/conf/app.example.ini
|
||||
;; https://codeberg.org/forgejo/forgejo/src/commit/8769df117d6cc2f4ab00d6e1d54ef4241d063f11/docs/content/doc/advanced/config-cheat-sheet.en-us.md
|
||||
;;
|
||||
;ENABLED = false
|
||||
;;
|
||||
|
|
@ -1762,7 +1762,7 @@ LEVEL = Info
|
|||
;; Sometimes it is helpful to use a different address on the envelope. Set this to use ENVELOPE_FROM as the from on the envelope. Set to `<>` to send an empty address.
|
||||
;ENVELOPE_FROM =
|
||||
;;
|
||||
;; If gitea sends mails on behave of users, it will just use the name also displayed in the WebUI. If you want e.g. `Mister X (by CodeIt) <gitea@codeit.net>`,
|
||||
;; If Forgejo sends mails on behave of users, it will just use the name also displayed in the WebUI. If you want e.g. `John Doe (by AppName) <johndoe@example.com>`,
|
||||
;; set it to `{{ .DisplayName }} (by {{ .AppName }})`. Available Variables: `.DisplayName`, `.AppName` and `.Domain`.
|
||||
;FROM_DISPLAY_NAME_FORMAT = {{ .DisplayName }}
|
||||
;;
|
||||
|
|
@ -1923,7 +1923,7 @@ LEVEL = Info
|
|||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;
|
||||
;; How Gitea deals with missing repository avatars
|
||||
;; How Forgejo deals with missing repository avatars
|
||||
;; none = no avatar will be displayed; random = random avatar will be displayed; image = default image will be used
|
||||
;REPOSITORY_AVATAR_FALLBACK = none
|
||||
;REPOSITORY_AVATAR_FALLBACK_IMAGE = /img/repo_default.png
|
||||
|
|
@ -2041,7 +2041,7 @@ LEVEL = Info
|
|||
;;
|
||||
;; Setting this to true will enable all cron tasks periodically with default settings.
|
||||
;ENABLED = false
|
||||
;; Setting this to true will run all enabled cron tasks when Gitea starts.
|
||||
;; Setting this to true will run all enabled cron tasks when Forgejo starts.
|
||||
;RUN_AT_START = false
|
||||
;;
|
||||
;; Note: ``SCHEDULE`` accept formats
|
||||
|
|
@ -2081,7 +2081,7 @@ LEVEL = Info
|
|||
;SCHEDULE = @every 10m
|
||||
;; Enable running Update mirrors task periodically.
|
||||
;ENABLED = true
|
||||
;; Run Update mirrors task when Gitea starts.
|
||||
;; Run Update mirrors task when Forgejo starts.
|
||||
;RUN_AT_START = false
|
||||
;; Notice if not success
|
||||
;NOTICE_ON_SUCCESS = false
|
||||
|
|
@ -2102,7 +2102,7 @@ LEVEL = Info
|
|||
;SCHEDULE = @midnight
|
||||
;; Enable running Repository health check task periodically.
|
||||
;ENABLED = true
|
||||
;; Run Repository health check task when Gitea starts.
|
||||
;; Run Repository health check task when Forgejo starts.
|
||||
;RUN_AT_START = false
|
||||
;; Notice if not success
|
||||
;NOTICE_ON_SUCCESS = false
|
||||
|
|
@ -2120,7 +2120,7 @@ LEVEL = Info
|
|||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;; Enable running check repository statistics task periodically.
|
||||
;ENABLED = true
|
||||
;; Run check repository statistics task when Gitea starts.
|
||||
;; Run check repository statistics task when Forgejo starts.
|
||||
;RUN_AT_START = true
|
||||
;; Notice if not success
|
||||
;NOTICE_ON_SUCCESS = false
|
||||
|
|
@ -2275,7 +2275,7 @@ LEVEL = Info
|
|||
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;; Update the '.ssh/authorized_keys' file with Gitea SSH keys
|
||||
;; Update the '.ssh/authorized_keys' file with Forgejo SSH keys
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;[cron.resync_all_sshkeys]
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
|
|
@ -2348,7 +2348,7 @@ LEVEL = Info
|
|||
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;; Check for new Gitea versions
|
||||
;; Check for new Forgejo versions
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;[cron.update_checker]
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
|
|
@ -2449,7 +2449,7 @@ LEVEL = Info
|
|||
;[other]
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;; Show version information about Gitea and Go in the footer
|
||||
;; Show version information about Forgejo and Go in the footer
|
||||
;SHOW_FOOTER_VERSION = true
|
||||
;; Show template execution time in the footer
|
||||
;SHOW_FOOTER_TEMPLATE_LOAD_TIME = true
|
||||
|
|
@ -2696,7 +2696,7 @@ LEVEL = Info
|
|||
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
||||
;; settings for Gitea's LFS client (eg: mirroring an upstream lfs endpoint)
|
||||
;; settings for Forgejo's LFS client (eg: mirroring an upstream lfs endpoint)
|
||||
;;
|
||||
;[lfs_client]
|
||||
;; Limit the number of pointers in each batch request to this number
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue