Best practice - Git + Build automation - Keeping configs separate

Viewed 2015

Searching for the best approach to keep my config files separate, yet not introduce extra steps for new developers setting up their environments.

I am guessing a submodule would suffice to do the job, but then how would I switch configs seamlessly depending on the task at hand, aka pull in DEV config regularly, pull PROD branch of config repo during build?

Needs to be:

  • Easy and painless for new devs.
  • PROD config files should only be accessible to select users + build user.

Thank you in advance.

1 Answers
Related