3 ms·
Working in a consulting capacity, mainly doing LAMP development with a small team. We use a standardized Vagrant image (https://github.com/readysetrocket/vagran
by garethsprice 11y ago
Working in a consulting capacity, mainly doing LAMP development with a small team. We use a standardized Vagrant image (https://github.com/readysetrocket/vagrant-lamp https://github.com/readysetrocket/vagrant-lamp) which has cut down on a lot of local environment issues for our dev team.
Previously all devs had their own environment (some MAMP/WAMP, some homebrew, some remote, etc) which led to onboarding and support issues. Setting up a standardized recommended dev environment has helped with that a lot - both in terms of reducing project onboarding and getting junior developers up and running.
Would love a day where we can build projects as Docker containers and hand them off to our clients' IT teams, but that seems to be a way off.
SO thread where the authors of Vagrant and Docker weigh in: http://stackoverflow.com/questions/16647069/should-i-use-vagrant-or-docker-io-for-creating-an-isolated-environment http://stackoverflow.com/questions/16647069/should-i-use-vag...