4
fermac
8y

I've been trying to push good practices at work, which includes migrating testing environment to vagrant.
Been trying to push it forward for months, and this week, a "genius"co-worker just started complaining we shouldn't overcomplicate and just provision a vm for testing for everyone to use, and boss agrees immediately!
Guess who'll have to maintain it whenever someone remembers to destroy it...

Comments
  • 0
    I'm behind the times and would like to learn. Can you ELI5 why Vagrant is a better solution? I Googled it but I'm curious to here your thoughts. Thanks!
  • 1
    For me, it's easier to update a vagrantfile than to make changes on live machine and take a new snapshot.
    Also, I rather prefer people run tests on their personal machines, keeping dependencies up to date, and the ease to destroy the testing environment when they don't need it.
  • 1
    vagrant, docker, rkt,...

    allows everyone to destroy his own shit without any impact on others.
  • 0
    Most co-workers work on windows, vagrant makes it easier to deploy than docker.
  • 0
    Vagrant is a nice idea for development and deployment but provisioners are tough for beginners, and worse when you are forced to use PuPHPet which changes its goddamn specification every other week with breaking changes so most of your older projects dont work anymore. Ugh...
Add Comment