Local Development vs Development droplet

I am used to developing on a live server and making changes directly to the production server. <–(I know not a good idea, but that’s what i have been doing for years) I want to change this using digital ocean.

I’m looking for advice on how to implement a good environment. Keep in mind, i’m not working with a lot of other developers and most are small apps and some client websites.

Many posts say to implement a local machine development environment > push to github > then deploy to live/production server.

I understand the local dev environment(mac), but i have about 4 different computers i work off of on any given day(laptop at home, Imac at work 1, different imac at work 2, and another imac at home incase I don’t want to use my laptop. My point is, I hate being tied to one machine, so local dev environment has never been good for me.

My thought was to create two droplets, one for dev and another for production, with github in the middle for version control.

My question is…does this make sense? Is there anyone else doing it this way or should I be using local dev on all of my machines?

Any help would be appreciated. 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

Thanks guys. I am using php and mysql mostly on ubuntu servers…Some CMS’s for client websites and Laravel framework for applications.

I’m leaning toward two identical droplets (dev & production). I have also been looking into vagrant for a local development environment as well, but given that i bounce around from machine to machine a lot, it’s probably not the best solution.

I don’t know your environment scenario. I’m using PHP and MySQL for all my projects, some have frameworks, some don’t. They key is: PHP provides ‘Dependency Manager’ from Composer. So… wherever i move my application, Composer will take care of all libraries i need to run my app, install and keep everything up to date. Not just PHP, but Ruby also provide cool stuffs like that and sure other languages/platforms do so.

I really <strong>never</strong> (yeah, <strong>never</strong>, <strong>never</strong>, <strong>never</strong>…) had to worry about development and productions servers.

Also, i work with identical production/development environment (same specs, different servers). So, when developing I can get all possible problems, fix then in production server (install modules, change configs) and after that i get everything ready to production.

Let us know more about you languages, servers and other cool stuffs :)