That was it. Thanks very much for the reply.
-f
On Wednesday, January 18, 2017 at 5:15:03 PM UTC-5, Rob Nelson wrote:
>
> In the `apache` class there is a `default_mods` parameter as well (param
> https://github.com/puppetlabs/puppetlabs-apache#default_mods and code
> path
> https://github.co
In the `apache` class there is a `default_mods` parameter as well (param
https://github.com/puppetlabs/puppetlabs-apache#default_mods and code path
https://github.com/puppetlabs/puppetlabs-apache/blob/28e9d41b2028f13c81b43e47c79bd28899170ccb/manifests/init.pp#L334-L345),
it looks like you would wan
I'm running puppet 4.8 and I'm trying to configure the Puppetlabs-Apache
module, which is v1.10.0. According to the README apache::mod::expires has
three parameters, one of which is expires_default.
(https://forge.puppet.com/puppetlabs/apache#class-apachemodexpires). It
also says that is use
Hi,
apache/manifests/init.pp defines:
if $::apache::conf_dir and $::apache::params::conf_file {
case $::osfamily {
'debian': {
$error_log= 'error.log'
$scriptalias = '/usr/lib/cgi-bin'
$access_log_file = 'access.log'
}
I would l
Thanks a lot for your answer,
Cheers
2015-11-06 16:34 GMT+01:00 Matthew Hyclak :
> No, because puppet is now "managing" the file, it won't be included in the
> purge.
>
> On Fri, Nov 6, 2015 at 9:11 AM, Arnau wrote:
>
>> Hi,
>>
>> thanks for your answer.
>> But with this file + apache doing a d
No, because puppet is now "managing" the file, it won't be included in the
purge.
On Fri, Nov 6, 2015 at 9:11 AM, Arnau wrote:
> Hi,
>
> thanks for your answer.
> But with this file + apache doing a directory purge on each run, isn't it
> going to be add/remove the file in every run?
>
> (custom
Hi,
thanks for your answer.
But with this file + apache doing a directory purge on each run, isn't it
going to be add/remove the file in every run?
(custom_config is working like a charm)
TIA,
Arnau
2015-11-06 14:48 GMT+01:00 Matthew Hyclak :
> Could/should be as simple as
>
> class thruk {
>
Could/should be as simple as
class thruk {
package { 'thruck':
ensure => 'installed',
}
file { '/etc/httpd/conf.d/thruk.conf':
ensure => 'file',
require => Package['thruk'],
}
}
Salt to taste.
On Fri, Nov 6, 2015 at 5:00 AM, Arnau wrote:
> Hi Hunter,
>
> thanks for your ans
Hi Hunter,
thanks for your answer.
I don't see how to do what you suggest, could you please give me a short
example?
(I was using apache::custom_config as a workaround)
TIA,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe
The apache module contains many mod manifests [1] that use file
resources with templates [2] that you can pattern your code after. No
need to use apache::vhost at all.
[1] https://github.com/puppetlabs/puppetlabs-apache/tree/master/manifests/mod
[2] https://github.com/puppetlabs/puppetlabs-apache/
Hi all,
Puppetlab apache module [1] by default purges everything under
/etc/httpd/conf.d . If you want to add an extra file, you must use
apache::vhost.
I'm writing a module for managin thruk. The trhuk rpm packge provides a
apache conf file (/etc/httpd/conf.d/thruk.conf). At this point I'm
wonder
As far as I have read it's not possible to change the default port for
Apache
class
{ 'apache': default => 8080, }
apache::listen
{ '8080': }
will just add the port 8080 but the port 80 is still available.
Is this a bug? If not does somebody know how to do that?
--
You received this
Does the apache::vhost facility in puppetlabs-apache support mod_jk
redirects in some fashion I'm missing?
I'm about to use this module (along with a couple of others) to set up
Jenkins on a server of mine for purely research purposes...
--
You received this message because you are subscribed to
El 25/06/15 a las 12:47, UK_beginner escribió:
I'm using the puppetlabs-apache module (currently v1.5.0) and I'm
looking for a way to be able to define some default values for every
virtual host. For example, it would be good to set ServerAdmin to
'x...@yy.com' as a default, allowing overrides on
Hello
Wrap your own site::apache module.
As another benefit you give yourself a single point to adapt to changes to
puppet labs hapax he
Neil
I'm using the puppetlabs-apache module (currently v1.5.0) and I'm looking
for a way to be able to define some default values for every virtual host.
For e
I'm using the puppetlabs-apache module (currently v1.5.0) and I'm looking
for a way to be able to define some default values for every virtual host.
For example, it would be good to set ServerAdmin to 'x...@yy.com' as a
default, allowing overrides only when necessary.
Can anyone suggest a way t
Thanks for this guys; sorry I hadn't seen these responses till now...
I'd gladly do a PR, but what would be the situation when its not required?
Is it if @proxy_dest or @proxy_pass are set?
Secondly; my setup (running a jenkins box behind apache) also needs these
directives set:
AllowEncodedSl
Set it to /dev/null ?
On 17 Sep 2014 17:53, "Hunter Haugen" wrote:
> Yeah, basically `$docroot` is still a required parameter because
> historically it was required (apache::vhost didn't do proxy stuff) and was
> never updated. If you want to make a PR that makes it default to `undef`
> and then
Yeah, basically `$docroot` is still a required parameter because
historically it was required (apache::vhost didn't do proxy stuff) and was
never updated. If you want to make a PR that makes it default to `undef`
and then raises helpful errors in cases when it is needed, then that would
be great :)
Unfortunately you can't. This is a restriction of Apache, which requires a
docroot value for every vhost, and not of Puppet.
--
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
Hi there,
pretty new to puppet so I'm guessing this is something simple. I'm trying
to set up an apache virtual host that simply acts as a proxy to push all
traffic on port 80 to a servlet running on 8080. I have this working on a
non puppet managed server with this virtual host:
ServerAdmin
I think the parameter you're looking for is
https://github.com/puppetlabs/puppetlabs-apache/#mpm_module
So:
class { 'apache':
mpm_module => 'prefork',
}
class { 'apache::mod::php': }
or if you need to provide the prefork module custom parameters:
class { 'apache':
mpm_module => false,
}
c
Have a bit of frustration here: I have a class I've written to install a
vhost based Wordpress site on a server. There will be serveral there.
Since mod_php is needed I also need to install mod_prefork.
I invoke the apache class thusly:
class {'apache':
default_
Hi,
we are using puppetlabs-apache module version 1.01.
When we run puppet parser validate to check our Puppet code we see the
following error:
Warning: You cannot collect exported resources without storeconfigs being
set; the collection will be ignored on line 65 in file
/etc/puppet/modules/
Hi all,
I am trying to work out the best way to solve something that does not get
configured correctly with puppetlabs-apache.
using puppetlabs-apache and WSGI defaults, it places the wsgi socket into
the default location according to:
http://code.google.com/p/modwsgi/wiki/ConfigurationDirecti
On Tue, Dec 10, 2013 at 10:42 PM, William Van Hevelingen
wrote:
> I opened an issue for SUSE/SLES support to track it's progress.
>
> https://github.com/puppetlabs/puppetlabs-apache/issues/525
Got some email from github on this early, thanks. Where does
discussion on this module take place, this
I opened an issue for SUSE/SLES support to track it's progress.
https://github.com/puppetlabs/puppetlabs-apache/issues/525
On Tue, Dec 10, 2013 at 5:18 AM, Darin Perusich wrote:
> On Tue, Dec 10, 2013 at 3:58 AM, William Van Hevelingen
> wrote:
> > A couple of days ago we released puppetlabs/
On Tue, Dec 10, 2013 at 3:58 AM, William Van Hevelingen
wrote:
> A couple of days ago we released puppetlabs/apache 0.10.0, and as busy as
> all involved people were we were to accomplish the release they are now
> equally
> busy to do other amazing things.
>
> http://forge.puppetlabs.com/puppetl
A couple of days ago we released puppetlabs/apache 0.10.0, and as busy as
all involved people were we were to accomplish the release they are now
equally
busy to do other amazing things.
http://forge.puppetlabs.com/puppetlabs/apache/0.10.0
Among the endless (22) features that we've added in this
Hello!
Sorry for the confusion. It appears that the parameters you're referencing
are from the master branch of the github repo, but are installing the older
version from the forge (which has far less attention). The documentation on
https://github.com/puppetlabs/puppetlabs-apache is only in refer
Thank you for giving my question a look,
I'm starting up working with puppet and so far its great, however the
apache module is driving me crazy :-/
The manual on the website https://github.com/puppetlabs/puppetlabs-apache
gives tons of options, only a view work for me.
I have installed the 0.6.0
- Original Message -
| Hi All,
|
| I'm trying to use the Puppet Labs Apache module from the forge or the
| git repo and when I install it, and then add
|
| class {'apache': }
|
| inside the node definition I end up with the error
|
|
| Could not retrieve catalog from remote server: Er
Hi All,
I'm trying to use the Puppet Labs Apache module from the forge or the git repo
and when I install it, and then add
class {'apache': }
inside the node definition I end up with the error
Could not retrieve catalog from remote server: Error 400 on SERVER: Resource
type a2mod doesn't
Hi Shantanu,
On Fri, Aug 24, 2012 at 1:52 PM, Shantanu wrote:
>
> I am getting following errors with the latest puppetlabs-apache
> module. I am using Puppet 2.6.16 on CentOS 6.2 OSs and with required
> dependency modules firewall (v0.0.4-80-g63fd433) and stdlib (3.0.0-27-
> g4e25230) installed i
I am getting following errors with the latest puppetlabs-apache
module. I am using Puppet 2.6.16 on CentOS 6.2 OSs and with required
dependency modules firewall (v0.0.4-80-g63fd433) and stdlib (3.0.0-27-
g4e25230) installed in the modulepath.
I have included only following class to in a node temp
Silviu Paragina wrote:
>> according to Luke @ puppetcamp Europe this is a problem that should be
>> fixed within puppet. So it should be possible to define that package
>> cron or apache should be installed and all the cron/a2mod depend on that
>> package and puppet shouldn't fail before.
>>
>
On 28.06.2010 21:16, Peter Meier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
1. Is this a good ideea? (if not why not?) From other discussions, I
know that this is how puppet should behave in general about type providers.
2. Should I open a ticket to add this new file for the apach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> 1. Is this a good ideea? (if not why not?) From other discussions, I
> know that this is how puppet should behave in general about type providers.
> 2. Should I open a ticket to add this new file for the apache module?
> 3. This seems trivial. Why wa
I'm trying out the apache module from puppet labs. Note the a2mod type
in it. Now I have uncovered the classical provider problem with it. If
you require some apache modules enabled and you don't have apache
installed you get the classical no provider for a2mod (in this
particular case) and pup
39 matches
Mail list logo
