On Wednesday, February 25, 2015 at 4:35:11 PM UTC-6, Karen Ellrick wrote: > > > It's understandable if the PuPHPet project does not support hand editing >> its output... >> > > If that was the case, Juan wouldn't have told me in > https://github.com/puphpet/puphpet/issues/1352#issuecomment-72649784 that > I need to work with Puppet to do what I want. He seems to be saying that > the generated files can indeed be edited. > > Hi Karen, I've responded to you on puphpet's issue tracker.
> As PuPHPet developer, Juan is in a better position to give such advice, or >> at least to tell you about how the generated code and data are organized, >> which would help the rest of us advise you about what changes to make. >> > > When I asked Juan for help understanding the structure of the generated > code so that I'd know where to customize ( > https://github.com/puphpet/puphpet/issues/1352#issuecomment-72766107), > there was no response. He apparently doesn't have time to get into > specifics. > > I hope I addressed your questions. Note that everything I said is available within the gui itself, but it's probably my fault that you missed it - I am not a designer and UX isn't my forte. Most information is kind of haphazardly thrown in, and might be easy to miss. > With regard to LaTeX specifically, there are packages in CentOS's standard >> repositories, so you shouldn't need to configure a custom repository for it. >> > > The flavor I need is upTeX (https://www.ctan.org/pkg/uptex), which is a > bit non-standard, but I see that there are more repos for texlive stuff > than there were the last time I installed it, so I'll continue to > investigate that. I thought I was clever when I found a Puppet module for > texlive (https://github.com/andschwa/puppet-latex), but I apparently > don't understand how to use it. In Puppetfile I put > mod 'andschwa/puppet-latex', :git => ' > https://github.com/andschwa/puppet-latex.git' > but all I get is the module downloaded and unpacked, not installed. I also > tried putting the contents of that github repo in puphpet/puppet/modules, > but that didn't help. > > >> If you in fact do need to manage software that's not available >> pre-packaged from any public repository... >> > > The one I have been asking about all along is not really "software" per > se, but nginx configuration file content. So far no one has suggested > anything (even a link for more info) about how one gets that kind of thing > into Puppet. I'm using a PHP framework called Phalcon that needs some > special web server settings ( > http://docs.phalconphp.com/en/latest/reference/nginx.html#configuration-by-host) > > - I have it working on a VM, but I don't know how to get Puppet to create > it the next time. > If Phalcon needs special settings, you can either throw them into a bash file within the `puphpet/files/exec*` folders that will run on pre-defined `Vagrant` events (note that the Nginx puppet module I've chosen to use with PuPHPet *will* overwrite any non-standard configuration it did not add itself on every `vagrant provision`), or you can create Puppet code yourself to do what you want. Juan -- 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/d99ba98d-82e7-42ed-a8fe-de07ddd695c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
