Hello,
is there any way to set configuration stuff like contact email, notification email, tags configuration, etc in the containers/app.yml or somewhere else in the code?
I say so because I’m using Ansible to provision some server with Discourse standalone docker image and I have a lot of settings that are shared. Would be nice to have some .yml that I can re-use between projects. Version control is another reason why I would really love that.
Many thanks, really liking the experience for now
2 Likes
sam
June 17, 2016, 10:41am
3
We keep our app.yml files in source control, works great for us, we manage config for many 100s of containers this way
Hi @sam , could you please point me to a complete list of all the available settings we can use in app.yml?
Thanks!
sam
June 20, 2016, 1:01am
5
These can be changed by ENV vars
#
# 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
show original
(change to upper case and add DISCOURSE_ in front so for example rtl_css becomes DISCOURSE_RTL_CSS)
3 Likes
