Trackable / re-usable configuration

sam · June 20, 2016, 1:01am

These can be changed by ENV vars

config/discourse_defaults.conf

main

#
# DO NOT EDIT THIS FILE
# If you need to make changes create a file called discourse.conf in this directory with your changes
# On import this file will be imported using ERB
#

# Discourse supports multiple mechanisms for production config.
#
# 1. You can do nothing and get these defaults (not recommended, you should at least set hostname)
# 2. You can copy this file to config/discourse.conf and amend with your settings
# 3. You can pass in config from your environment, all the settings below are available.
#    Prepend DISCOURSE_ and upper case the setting in ENV. For example:
#    to pass in db_pool of 200 you would use DISCOURSE_DB_POOL=200

# All settings apply to production only

# connection pool size, sidekiq is set to 5, allowing an extra 3 for bg threads
db_pool = 8

# Database connection timeout in seconds

This file has been truncated. show original

(change to upper case and add DISCOURSE_ in front so for example rtl_css becomes DISCOURSE_RTL_CSS)

Topic		Replies	Views
Initial configuration directly from `app.yml` (discourse-docker / INSTALL-cloud.md) Self-hosting	3	1340	January 21, 2019
Discourse configuration file Product Support	2	1351	September 21, 2022
Default app.yml file anywhere? Self-hosting	3	6047	October 28, 2021
How to automate configuration Product Support	5	983	January 26, 2021
Install Discourse by environment variables in host Self-hosting	4	333	November 27, 2024

Trackable / re-usable configuration

Related topics