You pick the tools and extensions via a GUI (databases, vim, htop, apcu, redis, composer, etc.) and the necessary config is created for you. However the main reason I recommend puphpet over manual configuration, is due to relative simplicity of how the setup is achieved. The unpronounceable service (yeah, the “p” is silent) … wraps a nice web-based GUI around the Vagrantfile config.īehind the scenes it will use puppet for provisioning various tools that your might require in your project. We have tried chef, puppet, ansible and good ol’ bash scripts, we’ve made changes to config and private keys, but still something, somewhere is amiss. There are lots of stacks and pre-configured examples available on github… and with a few minor tweaks it seems like it’s just about to work… but alas, this or that constantly fails. In an epic quest to find answers as to just how to properly setup our vagrant we start researching and find countless examples of setting up a local dev environment with vagrant. I think the most obvious question one would ask at this point is. This is where the config goes and once you run that magic command vagrant up, all your provisioning dreams will be fulfilled. This file seems to be the main hurdle to make your installation work. I’m sure this is probably the first thing you’ve encountered while reading up on vagrant. There are a million ways to use it, there are countless tutorials on how to get it going to work for your app, but still when the time comes to actually try vagrant out … well nothing makes any sense. You can forget everything you know about vagrant… I saw a commercial on late night TV, it said,”Forget everything you know about slipcovers.” So I did.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |