summaryrefslogtreecommitdiff
path: root/manifests/vhost/file.pp
AgeCommit message (Collapse)Author
2012-05-31fix various puppet language thingsmh
2012-05-29rename site modulesmh
2011-05-17improve mod_security rulesmh
* handled now by a partial * possibility to add rules that should be removed * possibility to add custom mod_sec options" * use new infrastructure for existing mod_sec tweaks
2010-10-09fix typomh
2010-10-09only manage file parts if the file should actually be presentmh
2010-08-17remove includes in defines that are called a lot, it looks like compile time ↵mh
goes up with such includes
2010-08-16correctly fix problemmh
2010-08-16fix include bugmh
2010-08-16improve vhosts stuffmh
- move various inclusion to the file define, as this is the last define for all in the chain - only include if our vhost is not set to absent
2010-08-16fix various missing things for itk_plus modemh
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-11only manage source or content if file should be presentmh
2010-08-07remove unnecessary fileserver variable (#2460)mh
2010-07-20fix wrong statementmh
2010-07-05remove duplicate source entrymh
2009-12-08improve Debian supportJerome Charaoui
2009-11-14update apache module to 0.25.x stylemh
2009-11-02recursivly updating file path to new 0.25 stylemh
2009-06-16introduce usage of mod_macroMarcel Haerry
2009-05-17extracted every define and class in it's own filemh