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
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 :)
The text was updated successfully, but these errors were encountered:
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
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 hardcodedlocalhost
connection. But for production code and database don't live on the same machineLet me know what you think :)
The text was updated successfully, but these errors were encountered: