Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Templating engine for config files #1215

Open
jakepic1 opened this issue Sep 29, 2015 · 1 comment
Open

Templating engine for config files #1215

jakepic1 opened this issue Sep 29, 2015 · 1 comment

Comments

@jakepic1
Copy link
Contributor

Copy-pasting from one configuration file to another for each environment (especially local dev files) is painful and error-prone. Many good templating engines exist that we could use as part of our build/commit process to reduce duplication of things like database names, URLs, etc.

@jakepic1
Copy link
Contributor Author

A simple proposed solution:

  1. Use an easy templating engine like mustache. It's flexible without having way too many features or being tied to a particular programming language or environment.
  2. Rather than attempting to automatically generate the rendered YAML files at build-time, we can have a semi-manual process (i.e. running a script like ./generate_configs or similar). This would then generate the necessary "compiled" config files in their appropriate directories.
  3. Commit the compiled config files to Git, but prefer never to modify these compiled files, only the templates. This is similar to our current process for generating Java source code from Protobuf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant