Addendum: I got a chance to talk to someone at a PHP user's group gathering with my computer in front of me, and he explained a lot of fundamentals I was missing. I am better informed now about the different roles of Vagrant and Puppet, and what PuPHPet was doing for me. My main configuration file for PuPHPet was not manifest.pp at all, but config.yaml - once I saw what was in there, things starting making more sense. And I discovered that PuPHPet has grown a lot since I used it a year ago - it still can't do everything I need, but I now understand why you saw it as having a more active ongoing role. Since it can accept my current config.yaml as a starting point so that I don't have to go through all the steps again, I'm going to have it make me another server (so that I get the newest, best version of the PuPHPet-generated code) and work from there. I may still end up with a simplified Puppet setup (sans PuPHPet) long term, but since I'm such a newbie, it's nice to be able to reference example code that a Puppet expert wrote, even if it's more complex than it needs to be.
Thanks again for your help. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4eecadbd-c587-4951-ad41-e17353d20164%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
