Hi, Juan! It's great to hear from you here. As you can see, John felt that 
my question was more of a PuPHPet question than a Puppet one. After a 
little more work on my own I then posted on PuPHPet Issues 
(https://github.com/puphpet/puphpet/issues/1352), and you told me that it 
was a Puppet question. I felt a little like a ping pong ball... :( So I'm 
glad the loop is closing a bit.

jcbollinger - you're right in that PuPHPet has changed drastically since 
> your original archive was created.
>

It's not John, but me, that had the old archive. After creating a new one 
from the old config.yaml, PHP didn't work, requiring two changes (one you 
told me about, and the other someone else named Kevin who had the same 
problem and figured it out - 
https://github.com/puphpet/puphpet/issues/1364).
 

> Hope your current VM is running smoothly, though!
>

I'm still stuck at the overall question I tried to ask here and on github, 
which is how to modify either the PuPHPet config.yaml or the Puppet files 
to handle things beyond PuPHPet's GUI. Naturally it would be good to 
include as much of it in config.yaml as possible so that it won't be lost 
if I go back to the PuPHPet GUI later, but so far I have only figured out a 
few other places to put particular things - see 
https://github.com/puphpet/puphpet/issues/1352#issuecomment-72766107 for a 
list of mods I have done so far, which are scattered in four places. I have 
not gotten any farther - I still don't know how to include nginx config 
changes and installation of things that don't have a yum repo, like LaTeX 
and specialty files I'll need. Help from Juan, John, or anyone else is 
appreciated.

-- 
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/a1a5d4f5-5b86-4c9f-819e-5c688aa44ca3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to