Is there any documentation or examples of how exec-once exec-always work

[George Katsanos]

I'd like to start using exec-once exec-always to setup my system automatically and take advantage of these features.. But I haven't been able to find any examples of cases in what's used..

I guess for stuff like npm packages, apache modules etc, the config.yaml is enough?

Also does anyone know if its possible to generate meaningful vhost filenames instead of the generated numbers?

[jcbollinger]

On Saturday, October 11, 2014 3:05:25 AM UTC-5, George Katsanos wrote:

I'd like to start using exec-once exec-always to setup my system automatically and take advantage of these features.. But I haven't been able to find any examples of cases in what's used..

What in the world are you talking about?

Puppet has various features that might map to those terms, and likely some third-party modules have such features, too, but the terms themselves have no conventional meaning in the Puppet context.

 

I guess for stuff like npm packages, apache modules etc, the config.yaml is enough?

I know of npm, I'm familiar with Apache modules, and I know about a 'config.yaml' used by a piece of software related to Puppet (but not Puppet itself).  I don't know how they are related to each other in the context of your question.

 

Also does anyone know if its possible to generate meaningful vhost filenames instead of the generated numbers?

Again, context?  What are you using now that generates vhost names for you?  Are you tied to that, or are you open to altogether different approaches?

Additionally, what would characterize a "meaningful" vhost name for you?  What data are available for use in computing vhost names?

Overall, what have you already tried?


John

[Felix Frank]

On 10/11/2014 10:05 AM, George Katsanos wrote:
> the config.yaml is enough?

Is this PUPHpet or something similar?