Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

support for dynamic environments #184

Open
anush0247 opened this issue Feb 11, 2017 · 1 comment
Open

support for dynamic environments #184

anush0247 opened this issue Feb 11, 2017 · 1 comment

Comments

@anush0247
Copy link

Hi,

we love to have dynamic environments settings files instead of fixed, local, production, testing with each has its own set of varying services configuration.

for example:

  • local can have SQLite DB, production can have Postgres SQL.
  • local can have local storage, and production can have s3 storage.

so that we can have develop, alpha, beta like environments with its own service configuration.

cookiecutter/cookiecutter#848 (comment)

@pydanny
Copy link
Owner

pydanny commented Feb 13, 2017

@anush0247, I would love to have something like that too. However, the implementation of what you request will require a significant amount of work. Not just in coding, but also testing what is generated and maintaining it going forward.

If you want to have something like this I suggest one of the following options:

  • Implement it yourself, add CI tests, then submit a pull request to this project.
  • Implement it yourself, don't add CI tests, then maintain it in a seperate project.
  • Hire me to do it for you. I'm asking for pay on this feature because it is not a trivial request. I don't need this feature, hence why I'm not going to use my free time to implement it.

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

No branches or pull requests

2 participants