I'm looking for some expert feedback on our current local development setup. Here's what we're doing:
- We have our production and staging environments running in the cloud (EC2), with databases and services in a private IP space, and DNS names resolving to these private IPs.
- For local development and testing, everyone has been instructed to:
- Use ifconfig to alias a real internal IP,
- Hardcode that IP in the Nginx configuration,
- Use the same DNS names locally as they do in staging and production,
- Use root access for the database.
My concern is around potential routing issues. What could happen if some team members are accidentally connected to a VPN while others are not, or if someone forgets to alias their IP and ends up executing commands against the database? Could they inadvertently connect to production or staging environments instead of their local database?
2 Answers
This whole setup sounds like a disaster waiting to happen. Relying on hardcoded IPs and giving everyone root access to the DB is just asking for trouble. You really need to follow best practices here; using standard setups can save you from massive headaches and data loss.
I can't believe you're doing this in 2026. You've got a lot of things stacked against you; using real IPs and relying on manual configurations sounds like a recipe for disaster. You need to simplify your process and improve your security practices, stat!
Right? Just use proper technology and best practices. There's no excuse for an overly complicated and unsafe setup.
Definitely agree. It feels overly complex and risky. Just a single mistake could lead to a lot of chaos.