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),
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
Great work. What I find though is that a lot of WAMP/LAMP developers don't understand all these. You can add tremendous value to your Project by adding a few notes as to what are all the components and how do they fit together.
I've found that these sort of tools are more likely to take hold in ecosystems where command line actions and easy configuration tend to be common-place. I authored a Vagrant setup for Railo (open source version of Adobe ColdFusion) - http://github.com/bdcravens/railo-vagrant (not that great, haven't put much time into it - other contributors have really done more with it than I), but I haven't heard of much uptake of this or others using Vagrant in the ColdFusion community.
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.
I upgraded my development environment to VM just 2 months ago. I'm still configuring VM by myself bu i admire your work. i just wanted to congratulate you. thanks for your work.
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