Enhance resiliency of target switching
When I’m developing and want to deploy to Production, I switch to Production and Deploy, but often forget to return back to Development target.
The issue is, I go to the browser to load localhost, and it attempts to connect to the Production database, because the selected target is Production.
It’s my belief the target switching functionality is far from ideal, as there might be a timeframe where the Development server tries to connect to a Production database. Now, imagine (e.g.) about scheduled actions of Development running on a Production database…
I suggest to enhance things in a way that production DB credentials don’t end being used by the development target, don’t ever mix target configuration
My stack: NodeJS Docker