A simple GUI to set up virtual machines for PHP development
puphpet.com
puphpet.com
1. I don't know how to pronounce it. I usually try to say "puff-pet" and look like an idiot while doing so.
2. I started learning Vagrant/Puppet a few months ago. Puppet is powerful, but has "gotchas" that felt like I was continuously bashing my head against the wall. I didn't want other people to go through the same frustration, so I decided to add buttons. Developers love buttons!
3. Some of the goals of PuPHPet are to
a) make tools like (X|W|M)AMP obsolete,
b) show developers the benefits of VM development (especially PHP developers),
and c) provide quickstart setups for popular projects (https://puphpet.com/quickstart/symfony , https://puphpet.com/quickstart/puphpet).
Possibly even d) setup an API to allow people to POST their config requirements and get back a link to a generated zip file, without needing to use the GUI itself. I could use some help on that front: https://github.com/puphpet/puphpet/issues/100
I'm wondering if you would mind elaborating on the choice of Silex over the other options out there. I've been playing a bit in this realm and would be glad to know how you came to that decision.
Thanks again
It implements a proper DIC, routing and quick ways to set up outside libraries (providers).
It comes with only what you need to get started, nothing you don't, but when you want to add more it doesn't get in your way.
https://puphpet.com/#webserver
You can also choose PostegreSQL
Slick UI + the fact that it generates this standard DevOps setup (Vagrant + Puppet) instead of trying to reinvent that particular wheel... so cool.
but the site is neat. i wouldnt call it a GUI tho, it makes it sound like another app i need to install.
And i agree with the comment that it should be cli. that would be really neat.
I have it on my list to expand out to other languages and offer in-depth configuration options just like PHP does. Unfortunately I am not familiar with any of them to be able to confidently say I am following best practices, or even know what options developers want to choose!
Opening a github issue and outlining what exactly you'd like to see would go a very long way to reaching that goal.