Window must be larger then treshhold and we have to use the module name in the template path
Changed the order of the files. First Backend, then director. Better for human readable. And we have to use the module name in template path
Changed the name of the config to debian default
Activate varnish automaticly. Include the new setup-class and added the VHOS declaration with Header/Footer
Added the weight parameter with an default value
Added the possibility to define vhosts. Normally Varnish will sent all traffic to the default-director. If another director should be used, then it is necessary to define it explicit
Removing TODO file from another dev
Added VHOST documentation
Added Service class, which ensure that varnish is running and added the possibility to restart varnish, if configuration is changed
Changing Position for default director
Bugfix: With round-robin as DIR-Policy it is not allowed to use weight
Added an used manually created config as an example, which is be used on another project. This Puppet Module can currently not create this config
Only neccessary for debugging
Not really good example for wordpress
Code cleaning
Normalize user agent

to avoid to many copies
Set X-Forwarded-For Header
Use anonymous, cached pages if all backends are down

You have to configure a health-check
Varnish can only cache results for GET-Requests
pipeline post requests

At the moment varnish can't deal properly with POST-Requests,
especially on wordpress-Sites