summaryrefslogtreecommitdiff
path: root/manifests/vhost/php/typo3.pp
AgeCommit message (Collapse)Author
2012-05-31fix various puppet language thingsmh
2011-10-18fix variable namingmh
2011-10-08merge functions to new stdlibs, fix has_key hash problemmh
2011-10-08introduce a new template style, less duplicated things, more handy optionsmh
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-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-11introduce logmode featuremh
We are now able to select how apache should log accesses. These modes are: * default: as you would use it * semianonym: no ips are logged for CustomLog, ErrorLog still logs ips * anonym: no ips are logged for CustomLog, ErrorLog is sent to /dev/null * nologs: all logs are sent to /dev/null
2010-01-30migrate missing partsmh
- migrate missing (newly introduced) vhosts - pass relevant_only stuff to subdefines
2010-01-04add $mod_security_relevantonly flag, enabled by default, logs only on ↵Jerome Charaoui
suspicious requests, set to 'false' to log all requests (as before)
2009-11-21introduce php_default_charset to set charset header in phpmh
2009-11-18group php options togethermh
2009-11-18renames and proc move from webhosting for php_safe_mode_exec_binsAndreas
2009-11-18add php_bin_dir for typo3Andreas
2009-11-18update typo3 managed (i.e. httpd writable) directoriesAndreas
2009-11-09temp must be writableAndreas
2009-11-01no apache::typo3 needed at the momentAndreas Maag
2009-11-01typo3 addedAndreas Maag