Download the PHP package dmk/mkvarnish without Composer
On this page you can find all versions of the php package dmk/mkvarnish. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dmk/mkvarnish
More information about dmk/mkvarnish
Files in dmk/mkvarnish
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package mkvarnish
MK VARNISH
Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Varnish Cache is really, really fast. It typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture. A high level overview of what Varnish does can be read on varnish-cache.org
Introduction
What does it do?
This extension tells Varnish about TYPO3 insights of a page to allow Varnish make proper caching decisions based on those information. It informs Varnish to invalidate the cache as soon as the content is changed through the TYPO3 backend.
Features
- ready to use configration for Varnish and TYPO3
- Varnish based caching for all pages using cache-tags
- TYPO3 clear cache hook to clear cache or smart ban relevant pages in Varnish
- Provide a page content error handler which does not bypass Varnish like the dafault handler does. This way 404 handling leverages Varnish too.
Background
- the extension sets
config.sendCacheHeaders = 1to enable TYPO3 core function which sends appropriate cache headers to Varnish - send "X-Cache-Tags" HTTP Header which is used to issue PURGE command against
- send appropriate PURGE Command to Varnish during a TYPO3 clearCache action
- those headers are used for Varnish processing only and get removed afterwards
Installation
We recommend the installation via composer. Maybe you can use our TYPO3-Composer-Webroot Project
From project root you need to run
Requirements
- you should make yourself familiar with Varnish and how you want to implement Varnish in your specific setup.
- Varnish has to be up and running. You can find a sample configuration in
EXT:mkvarnish/Configuration/Varnish/default-4.vcl. Make sure to change or remove the Debug ID at the beginning of sub vcl_recv. Furthermore you should check the last comment in sub vcl_recv and act accordingly. - requests to all static files should send appropriate expires headers
Configuration
- set
$TYPO3_CONF_VARS['SYS']['reverseProxyIP']to the IP address which is used by Varnish to connect to your Webserver or enable the caching in the extension configuration by setsendCacheHeaderstoForce Enabled. - do not use sessions, the fe_typo_user cookie will disable the caching
- dont set
no_cache=1 - the use of *_INT objects will disable the cache too, dont use it (You can find them with the Admin Panel.)
- Configure the page content error handler in the site configuration like this instead of the default "Page" handler if your 404 page is cachable through Varnish. Otherwise the content won't be cached/delivered through Varnish:
USER_INT objects
Sometimes there is a page that should be cached through Varnish but contains USER_INT plugins, for example a news detail page with a comment plugin. To migrate such a plugin to a USER plugin might be a hassle or even impossible. But there is a easy solution: The plugin needs to be lazy loaded with Ajax. To achieve this you can use the Ajax Content Renderer feature of mktools.
