4 ms·
The remote one is for production, not development. (Well, thats how I'm using them anyway). In my workflow I have two boxes in my Vagrant profile, one for deve
by mattbessey 13y ago
The remote one is for production, not development. (Well, thats how I'm using them anyway).
In my workflow I have two boxes in my Vagrant profile, one for development (local VBox VM) and one for production (DO droplet). Using Chef for provisioning, I can configure and test provisioning locally, then roll it out in production with minimal effort.
Its a really nice workflow! Although all this Docker business lately looks like it might make for an even better one.
- Keyframe 13y agoWhat's the overhead of Vagrant for production purposes? Maybe I'm too old school for all of this, but I still don't understand what docker is or what it does.
- rschmitty 13y agoThere is no overhead for vagrant, it is just something that provisions/sets up your server with chef/puppet/whatever once the server is up, it is exactly the same as if you did it by hand