Trackable / re-usable configuration

AI 生成的摘要

The discussion revolves around trackable and re-usable configuration for Discourse. enricostn is looking for a way to set configuration settings, such as contact email and tags configuration, in a reusable file like app.yml, for use with Ansible provisioning and version control. sam confirms that keeping app.yml files in source control works well for managing multiple containers. enricostn requests a complete list of available settings for app.yml, which sam provides, pointing to the Discourse defaults configuration file on GitHub. The available settings can be modified by using environment variables, which are created by uppercasing and prefixing the setting name with DISCOURSE_.

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 :clap::clap::clap:

Somehow related Programmatic configuration of a new Discourse site

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! :smiley:

These can be changed by ENV vars

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