I've been involved with various teams and companies, and I've found that having three main environments is typically beneficial when developing a site. The first is a local machine for individual developers to see their changes. Next, there's a dev/test server where all the compiled code can be reviewed before going live. Lastly, of course, there's the production server. I'm curious to know what the best practices are for the dev/test/review stage. Should it mirror the production server closely with built files, or should it function more like a developer's environment with debugging features? From what I've seen, the review stage is usually only accessible to developers, managers, or clients.
2 Answers
If you're just two founders building something, you might not need all those servers. Extra ones can complicate things without solving real issues. Each layer should help streamline your workflow, not hinder it. Usually, larger teams benefit from integration and QC environments, but if it's just you and a partner, direct local testing can often be faster.
Remember, there isn't a one-size-fits-all approach. Best practices should adapt to your team size and project needs. If someone recommends a rigid setup without knowing your context, it might not be practical advice. Focus on what helps you achieve results efficiently and let your process evolve.
Development and testing should ideally have separate setups. Your local environment is for development, so consider having dedicated test servers instead. These should match your production configurations to ensure proper testing.
As for preview environments, they should showcase a clean view without the clutter from testing. Clients should see instances that are representative of actual use, not a mix of everything thrown together. Each preview should simulate real-world data and conditions to give clients a reliable demonstration of the product.
So, to clarify, you're saying the preview site should mirror the production site? I’ve seen different setups where the clients see a mess because of all the testing. Seems pointless if they’re supposed to be checking final features. I get now that a test site should act like a pre-release version, right?