Solution to maintain a web app (PHP) deployed in different droplets


I’m developing a PHP web app that, because of business model reasons, we’re thinking to initially deploy it to each customer along with an own virtual machine (droplet).

Haven’t used docker or kubernetes before, but I understand it could help with this, but before I dig deeper into that I would like to know if it’s indeed the right path to follow.

After the app is deployed, we’ll be doing updates to the app, so we’re seeking to just “push them” to each customer’s droplet with ease.

I would like to ask the community for opinions on this and, if possible, a rough list of steps to follow.

Many thanks

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This comment has been deleted

Hi there,

A few clarifying questions about the service you are providing that may help guiding your decision.

Does your frontend scale well to many instances? If applicable, can your backend scale well to many instances? Is your application tightly coupled to any other services? Can you application easily be broken down into logical components? Are you having issues with your current design right now?

Other things to consider to get an idea of what the application may look like: Does the webapp frontend have differences per client? Do the updates you’re pushing go out to each client or sometimes only to a few? Do you need storage for some sort of backend? Do the clients each need separate backends or can they share a single one?

While kubernetes and containerization can be beneficial in a lot of ways, sometimes for very simple use cases it could certainly be unnecessary legwork to containerize applications and learn kubernetes and surrounding technologies for little actual benefit.

That being said containerization does help in easing the deployment and portability of the application in question(in most cases).

It may largely come down to what your biggest priorities for this application are, that may steer you in one direction or the other.


John Kwiatkoski Senior Developer Support Engineer