I currently have a web server for my robotics team that runs a LAMP stack with CPanel, making it easy to manage websites and databases. However, we have started integrating a couple of other projects, including an ASP.NET Core backend that runs an API service through Apache. As we add more projects involving Node.js and Python backends, it's becoming quite complicated. I've dabbled with Docker for simple tasks at home and I think it would be beneficial to transition to a Docker-based environment for the server. I'm looking for advice on the following points: Should I use a separate container for each website? Is it better to have a single PHP container that handles all PHP sites? For my C# and Angular application, should the backend and frontend run in one container, or separate them? Finally, is transitioning from LAMP and CPanel to using containers a bad move?
2 Answers
Generally, it's best practice to have each Docker container handle one specific process, which means you'd want separate containers for the frontend and backend. You could work with a single PHP container if you're using something like Apache's virtual hosts that can handle multiple sites simultaneously. As for whether you should make the switch, that really hinges on how much control your team needs over the sites and what CPanel features you rely on. Consider testing a simple setup with dummy data initially to see if Docker is a good fit before committing to a full migration.
Using Docker like a lightweight VM allows for separating functions, but it's also fine to group processes in certain situations if that makes sense. Don't overthink it; the flexibility is one of Docker's strengths. You can try a simple test setup to see how it fits. Just remember—some features from CPanel will change, like managing files and databases, so make sure you're comfortable with that.
Thanks for the insights! I use CPanel mainly for file management, handling DNS, and database management via phpMyAdmin. I also want to add services like a password manager and file storage for team resources. It's more about providing an easy way for my team to use these tools and as a learning tool for web development. I think using Docker will be a fun project to tackle!