You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.
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.
@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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
so that we can have develop, alpha, beta like environments with its own service configuration.
cookiecutter/cookiecutter#848 (comment)
The text was updated successfully, but these errors were encountered: