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

Support for multiple environments #158

Open
Levivb opened this issue Sep 30, 2019 · 3 comments
Open

Support for multiple environments #158

Levivb opened this issue Sep 30, 2019 · 3 comments

Comments

@Levivb
Copy link

Levivb commented Sep 30, 2019

Hey,

This seems like a nice package to support our dev team in ensuring everyone has a stable dev environment. I looked through the checks and right now it kinda supports only one configuration.

Would it be possible to support multiple configurations for different environments?
For example: local a check to test whether the routes and configs are cached makes no sense, but on production, that would be a valid check.

And within checks it would also be nice to provide several configurations, for example the MySqlConnectable uses a hardcoded localhost connection. But for production code and database don't live on the same machine

Let me know what you think :)

@antonioribeiro
Copy link
Owner

I like the idea. But it would also require it to have those resource files duplicated by environment, maybe have a common folder for those common resources and one for each environment, and also separate things (enabled resources for each environment) in the config file

@thesun2003
Copy link

Why it cannot just use environmental settings like 'DB_HOST' from .env file?

@nakehealth
Copy link

This seems like a nice package to support our dev team in ensuring everyone has a stable dev environment.

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

No branches or pull requests

4 participants