summaryrefslogtreecommitdiff
path: root/manifests/centos.pp
AgeCommit message (Collapse)Author
2015-02-27lintingmh
2014-04-25use builtin language function instead of an own onemh
2014-02-23introduce a datadir for all dynamic hostingsmh
2013-12-28reduce dependency on lsb modules, rather use the builtin factsmh
2013-03-17fix selttype on EL6mh
2013-03-17lintingmh
2013-03-09fix fcontexts to be bettermh
2012-12-01fix typomh
2012-11-27lintingmh
2012-11-27make logdirs httpd_log_tmh
2012-06-05new style for 2.7mh
2012-05-29rename site modulesmh
2012-02-21use correct selinux typemh
2012-02-12manage selinux stuffmh
2011-11-23there is another Listen example already commented outmh
2011-11-22as file_line lacks ensure => absent, we have to do it with a sedmh
2011-10-09remove stupid cyclemh
2011-10-09migrate to new file_line typemh
2010-08-16impelement itk plus modemh
itk plus mode is an additional mode to deploy itk based hostings which should be a bit more performant. The idea is that we have two apache-instances running: A) prefork based, listening on the external interface B) itk based, listening on the loopback interface A) will serve all static webpages, as well as possibly serve all static content of dynamic websites. All requests to dynamic content will be redirected to B). The idea is that A) doesn't load any modules to server dynamic content at all. B) will serve all the dynamic scripts of a vhost. This will mean that for vhosts (static ones) as well as static content (all none dynamic scripts) we can benefit from the fast prefork model, while we can use itk's security model for all the dynamic scripts. There are two new additional run_modes: - proxy-itk: this just passes all requests to apache instance B). This one is similar to plain itk based mode and should be used for vhosts that shouldn't (yet) changed to the mixed mode. - static-itk: this passes only requests to dynamic scripts to B) while all static content is served by A). Beware that the user with which A) is running should be member of the run group of B) and all static files need to readable by the group. This reduces the security model you have with plain itk, as the prefork apache user will be able to read php (config-) files of any vhost that runs in static-itk mode. If you want to keep the level of security for a certain vhost, you need to run the specific vhost in proxy-itk mode. Note 1: you cannot run vhosts in itk mode and others in proxy or static itk mode. There is a duplicate file resource definition that blocks that possibility. Note 2: This mode works currently only on CentOS based systems, as no work have been done so far to implement an init.d script that's able to run 2 apache instances.
2010-08-07remove unnecessary fileserver variable (#2460)mh
2009-12-23simplify config subclassesJerome Charaoui
2009-12-23organize files in subdirectories per type : 'config' for main apache config; ↵Jerome Charaoui
'scripts' for extra shell scripts; 'service' for service default parameters. also, manage apache2.conf on Debian.
2009-12-23introduce config::global for global configs in conf.d and config::include ↵Jerome Charaoui
for vhost snippets in include.d
2009-11-14update apache module to 0.25.x stylemh
2009-11-02recursivly updating file path to new 0.25 stylemh
2009-06-03introduced logrotate only if we have vhostsmh
otherwise we get nasty logrotate errors introduced a first logrotate naming scheme. the openbsd logrotation should be integrated in that one as well.
2009-06-02added vhosts folders to logrotationmh
2009-05-17extracted every define and class in it's own filemh