ccchb/ansible-role-gitea
4
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
ansible-role-gitea/templates/gitea.ini.j2

219 lines
8.6 KiB
Text
Raw Normal View History

Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
; this file is the configuration of your local gitea instance
; {{ ansible_managed }}
;
; This file overwrites the default values from gitea.
; undefined variables will use the default value from gitea.
; Cheat Sheet: https://docs.gitea.io/en-us/config-cheat-sheet/
;
First commit
2017-01-10 15:09:34 -06:00
; App name that shows on every page title
APP_NAME = {{ gitea_app_name }}
; Change it if you run locally
RUN_USER = {{ gitea_user }}
; Either "dev", "prod" or "test", default is "dev"
RUN_MODE = prod
[repository]
Add config option to set repository path different to home_path
2020-05-18 16:37:17 -05:00
ROOT = {{ gitea_repository_root }}
First commit
2017-01-10 15:09:34 -06:00
; Force every new repository to be private
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
FORCE_PRIVATE = {{ gitea_force_private }}
update config ini comments
2019-03-10 07:46:18 -05:00
; Global limit of repositories per user, applied at creation time. -1 means no limit
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
MAX_CREATION_LIMIT = {{ gitea_user_repo_limit }}
First commit
2017-01-10 15:09:34 -06:00
; Mirror sync queue length, increase if mirror syncing starts hanging
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
MIRROR_QUEUE_LENGTH = 1000
update config ini comments
2019-03-10 07:46:18 -05:00
; Disable the ability to interact with repositories using the HTTP protocol
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
DISABLE_HTTP_GIT = {{ gitea_disable_http_git }}
First commit
2017-01-10 15:09:34 -06:00
[ui]
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Whether the email of the user should be shown in the Explore Users page
First commit
2017-01-10 15:09:34 -06:00
SHOW_USER_EMAIL = {{ gitea_show_user_email }}
fix typo in THEMES
2020-05-15 03:56:12 -05:00
THEMES = {{ gitea_themes }}
Allow to specify default theme
2020-05-09 16:01:51 -05:00
DEFAULT_THEME = {{ gitea_theme_default }}
First commit
2017-01-10 15:09:34 -06:00
[server]
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; The protocol the server listens on. One of 'http', 'https', 'unix' or 'fcgi'.
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
PROTOCOL = {{ gitea_protocol }}
DOMAIN = {{ gitea_http_domain }}
ROOT_URL = {{ gitea_root_url }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; The address to listen on. Either a IPv4/IPv6 address or the path to a unix socket.
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
HTTP_ADDR = {{ gitea_http_listen }}
HTTP_PORT = {{ gitea_http_port }}
improve https support
2020-09-18 05:41:54 -05:00
{% if gitea_http_port == 443 %}
PORT_TO_REDIRECT = 80
{% endif %}
{% if gitea_http_letsencrypt_mail is defined %}
ENABLE_LETSENCRYPT = true
LETSENCRYPT_ACCEPTTOS = true
LETSENCRYPT_EMAIL = {{ gitea_http_letsencrypt_mail }}
{% endif %}
First commit
2017-01-10 15:09:34 -06:00
; Disable SSH feature when not available
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
DISABLE_SSH = false
; Whether to use the builtin SSH server or not.
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
START_SSH_SERVER = {{ gitea_start_ssh }}
First commit
2017-01-10 15:09:34 -06:00
; Domain name to be exposed in clone URL
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
SSH_DOMAIN = {{ gitea_ssh_domain }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; The network interface the builtin SSH server should listen on
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
SSH_LISTEN_HOST = {{ gitea_ssh_listen }}
First commit
2017-01-10 15:09:34 -06:00
; Port number to be exposed in clone URL
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
SSH_PORT = {{ gitea_ssh_port }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; The port number the builtin SSH server should listen on
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
SSH_LISTEN_PORT = %(SSH_PORT)s
First commit
2017-01-10 15:09:34 -06:00
; Disable CDN even in "prod" mode
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
OFFLINE_MODE = {{ gitea_offline_mode }}
First commit
2017-01-10 15:09:34 -06:00
; Default path for App data
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
APP_DATA_PATH = {{ gitea_home }}/data
Enable git lfs options With this change it is possible to enable the git-lfs server. And to configure where data are stored.
2019-07-05 11:46:41 -05:00
{%- if gitea_lfs_server_enabled | bool %}
;Enables git-lfs support.
LFS_START_SERVER = true
; Where to store LFS files.
LFS_CONTENT_PATH = {{ gitea_lfs_content_path }}
{%- endif %}
First commit
2017-01-10 15:09:34 -06:00
[database]
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Either "mysql", "postgres", "mssql" or "sqlite3", it's your choice
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
DB_TYPE = {{ gitea_db_type }}
HOST = {{ gitea_db_host }}
NAME = {{ gitea_db_name }}
USER = {{ gitea_db_user }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Use PASSWD = `your password` for quoting if you use special characters in the password.
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
PASSWD = {{ gitea_db_password }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; For Postgres, either "disable" (default), "require", or "verify-full"
; For MySQL, either "false" (default), "true", or "skip-verify"
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
SSL_MODE = {{ gitea_db_ssl }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; For "sqlite3" and "tidb", use an absolute path when you start gitea as service
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
PATH = {{ gitea_db_path }}
improve logging
2020-09-18 10:13:46 -05:00
{% if gitea_log_only_warning %}
LOG_SQL = false
{% endif %}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
[indexer]
; Issue indexer storage path, available when ISSUE_INDEXER_TYPE is bleve
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
ISSUE_INDEXER_PATH = {{ gitea_home }}/indexers/issues.bleve
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Issue indexer queue, currently support: channel or levelqueue, default is levelqueue
ISSUE_INDEXER_QUEUE_TYPE = levelqueue
fix indexer config, keep old openid config
2019-03-10 08:37:47 -05:00
; When ISSUE_INDEXER_QUEUE_TYPE is levelqueue, this will be the queue will be saved path,
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; default is indexers/issues.queue
fix indexer config, keep old openid config
2019-03-10 08:37:47 -05:00
ISSUE_INDEXER_QUEUE_DIR = {{ gitea_home }}/indexers/issues.queue
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; repo indexer by default disabled, since it uses a lot of disk space
Add config options for repository indexer
2020-06-18 00:41:59 -05:00
REPO_INDEXER_ENABLED = {{ gitea_repo_indexer_enabled }}
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
REPO_INDEXER_PATH = {{ gitea_home }}/indexers/repos.bleve
Add config options for repository indexer
2020-06-18 00:41:59 -05:00
REPO_INDEXER_INCLUDE = {{ gitea_repo_indexer_include }}
REPO_INDEXER_EXCLUDE = {{ gitea_repo_indexer_exclude }}
REPO_INDEXER_EXCLUDE_VENDORED = {{ gitea_repo_exclude_vendored }}
MAX_FILE_SIZE = {{ gitea_repo_indexer_max_file_size }}
First commit
2017-01-10 15:09:34 -06:00
[security]
; Whether the installer is disabled
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
INSTALL_LOCK = true
First commit
2017-01-10 15:09:34 -06:00
; !!CHANGE THIS TO KEEP YOUR USER DATA SAFE!!
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
SECRET_KEY = {{ gitea_secret_key }}
INTERNAL_TOKEN = {{ gitea_internal_token }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; How long to remember that an user is logged in before requiring relogin (in days)
LOGIN_REMEMBER_DAYS = 7
First commit
2017-01-10 15:09:34 -06:00
[service]
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Disallow registration, only allow admins to create accounts.
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
DISABLE_REGISTRATION = {{ gitea_disable_registration }}
improve mailing configuration
2020-09-18 10:07:34 -05:00
REGISTER_EMAIL_CONFIRM = {{ gitea_register_email_confirm }}
First commit
2017-01-10 15:09:34 -06:00
; User must sign in to view anything.
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
REQUIRE_SIGNIN_VIEW = {{ gitea_require_signin }}
First commit
2017-01-10 15:09:34 -06:00
; Enable captcha validation for registration
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
ENABLE_CAPTCHA = {{ gitea_enable_captcha }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Type of captcha you want to use. Options: image, recaptcha
CAPTCHA_TYPE = image
; Enable recaptcha to use Google's recaptcha service
; Go to https://www.google.com/recaptcha/admin to sign up for a key
RECAPTCHA_SECRET =
RECAPTCHA_SITEKEY =
; Show Registration button
adds template variable for SHOW_REGISTRATION_BUTTON
2019-03-10 08:40:33 -05:00
SHOW_REGISTRATION_BUTTON = {{ gitea_show_registration_button }}
add variable gitea_only_allow_external_registration
2020-05-09 21:18:59 -05:00
ALLOW_ONLY_EXTERNAL_REGISTRATION = {{ gitea_only_allow_external_registration }}
Add configuration option for enabling notify email
2020-07-28 05:22:35 -05:00
ENABLE_NOTIFY_MAIL = {{ gitea_enable_notify_mail }}
First commit
2017-01-10 15:09:34 -06:00
[mailer]
adds mailer config parameters
2019-03-08 05:29:34 -06:00
ENABLED = {{ gitea_mailer_enabled }}
First commit
2017-01-10 15:09:34 -06:00
; Mail server
; Gmail: smtp.gmail.com:587
; QQ: smtp.qq.com:465
; Note, if the port ends with "465", SMTPS will be used. Using STARTTLS on port 587 is recommended per RFC 6409. If the server supports STARTTLS it will always be used.
adds mailer config parameters
2019-03-08 05:29:34 -06:00
HOST = {{ gitea_mailer_host }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Disable HELO operation when hostnames are different.
DISABLE_HELO =
; Custom hostname for HELO operation, if no value is provided, one is retrieved from system.
HELO_HOSTNAME =
First commit
2017-01-10 15:09:34 -06:00
; Do not verify the certificate of the server. Only use this for self-signed certificates
adds mailer config parameters
2019-03-08 05:29:34 -06:00
SKIP_VERIFY = {{ gitea_mailer_skip_verify }}
First commit
2017-01-10 15:09:34 -06:00
; Use client certificate
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
USE_CERTIFICATE = false
First commit
2017-01-10 15:09:34 -06:00
CERT_FILE = {{ gitea_home }}/custom/mailer/cert.pem
KEY_FILE = {{ gitea_home }}/custom/mailer/key.pem
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Should SMTP connection use TLS
adds template variable for IS_TLS_ENABLED
2019-03-10 08:14:57 -05:00
IS_TLS_ENABLED = {{ gitea_mailer_tls_enabled }}
First commit
2017-01-10 15:09:34 -06:00
; Mail from address, RFC 5322. This can be just an email address, or the `"Name" <email@example.com>` format
adds mailer config parameters
2019-03-08 05:29:34 -06:00
FROM = {{ gitea_mailer_from }}
First commit
2017-01-10 15:09:34 -06:00
; Mailer user name and password
Add username and password for smpt servers. Defaulting to blank
2019-06-10 14:10:39 -05:00
USER = {{ gitea_mailer_user }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Use PASSWD = `your password` for quoting if you use special characters in the password.
Add username and password for smpt servers. Defaulting to blank
2019-06-10 14:10:39 -05:00
PASSWD = `{{ gitea_mailer_password }}`
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Send mails as plain text
SEND_AS_PLAIN_TEXT = false
improve mailing configuration
2020-09-18 10:07:34 -05:00
SUBJECT_PREFIX = {{ gitea_subject_prefix }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Set Mailer Type (either SMTP, sendmail or dummy to just send to the log)
issue #53: define mailer type
2020-07-21 07:18:08 -05:00
MAILER_TYPE = {{ gitea_mailer_type }}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Specify an alternative sendmail binary
SENDMAIL_PATH = sendmail
; Specify any extra sendmail arguments
SENDMAIL_ARGS =
First commit
2017-01-10 15:09:34 -06:00
[session]
; Either "memory", "file", or "redis", default is "memory"
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
PROVIDER = file
First commit
2017-01-10 15:09:34 -06:00
; Provider config options
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; memory: doesn't have any config yet
First commit
2017-01-10 15:09:34 -06:00
; file: session file path, e.g. `data/sessions`
; redis: network=tcp,addr=:6379,password=macaron,db=0,pool_size=100,idle_timeout=180
; mysql: go-sql-driver/mysql dsn config string, e.g. `root:password@/session_table`
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
PROVIDER_CONFIG = {{ gitea_home }}/data/sessions
First commit
2017-01-10 15:09:34 -06:00
[picture]
AVATAR_UPLOAD_PATH = {{ gitea_home }}/data/avatars
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; This value will always be true in offline mode.
First commit
2017-01-10 15:09:34 -06:00
DISABLE_GRAVATAR = {{ gitea_disable_gravatar }}
[attachment]
; Whether attachments are enabled. Defaults to `true`
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
ENABLED = true
First commit
2017-01-10 15:09:34 -06:00
; Path for attachments. Defaults to `data/attachments`
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
PATH = {{ gitea_home }}/data/attachments
First commit
2017-01-10 15:09:34 -06:00
[log]
Simplify configuration file I kicked out some config values, that are not controlled via ansible variables. Maybe it makes more sense if we only customize the values, we are really changing. *(like database, domain and other behavior...)* I had the problem, that after upgrading gitea it won't run with the config provided by this ansible role. But the default config worked fine. I assume that the official gitea chenged and updated some options. Some options in the old config file of this role did not appear in the [official cheat sheet](https://docs.gitea.io/en-us/config-cheat-sheet/). @thomas-maurice: What did you think about it? Better track every value and update it in our config. Or clean up the config and only keep the parameter we really need and let gitea set everything else with their default values?
2019-05-22 02:10:57 -05:00
ROOT_PATH = {{ gitea_home }}/log
First commit
2017-01-10 15:09:34 -06:00
; Either "console", "file", "conn", "smtp" or "database", default is "console"
; Use comma to separate multiple modes, e.g. "console, file"
improve logging support
2020-09-18 07:02:41 -05:00
{% if gitea_log_systemd %}
MODE = console
improve logging
2020-09-18 10:13:46 -05:00
MACARON = console
improve logging support
2020-09-18 07:02:41 -05:00
{% else %}
First commit
2017-01-10 15:09:34 -06:00
MODE = file
improve logging support
2020-09-18 07:02:41 -05:00
{% endif %}
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
; Buffer length of the channel, keep it as it is if you don't know what it is.
First commit
2017-01-10 15:09:34 -06:00
BUFFER_LEN = 10000
; Either "Trace", "Debug", "Info", "Warn", "Error", "Critical", default is "Trace"
improve logging support
2020-09-18 07:02:41 -05:00
{% if gitea_log_only_warning %}
LEVEL = Warn
REDIRECT_MACARON_LOG = true
{% else %}
First commit
2017-01-10 15:09:34 -06:00
LEVEL = Info
adds all new config parameters from app.ini.sample Version: https://github.com/go-gitea/gitea/blob/e777c6bdc6f12f9152335f8bfd66b956aedc9957/custom/conf/app.ini.sample
2019-03-10 08:12:12 -05:00
REDIRECT_MACARON_LOG = false
improve logging support
2020-09-18 07:02:41 -05:00
{% endif %}
First commit
2017-01-10 15:09:34 -06:00
add back oauth2 parameters
2019-12-21 07:18:58 -06:00
[oauth2]
ENABLE = {{ gitea_oauth2_enabled }}
JWT_SECRET = {{ gitea_oauth2_jwt_secret }}
adds metrics endpoint config support
2019-12-21 06:08:19 -06:00
[metrics]
ENABLED = {{ gitea_metrics_enabled }}
TOKEN = {{ gitea_metrics_token }}
Reference in a new issue Copy permalink