This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
How a TYPO3 extension for Varnish integration was born from a flash of inspiration. | |
In 2013, my former employer snowflake and Redpill Linpro, the company behind Varnish at the time, agreed to work together. Part of this contract was that I was allowed to attend a Varnish course in Oslo with two colleagues, in order to give courses in Germany, Austria and Switzerland as a certified Varnish trainer afterwards. | |
Not only the social program remained in my good memory, but also in the course we could learn a lot of new things, although we had already actively used Varnish before. Besides the successful certification of all participants, the idea for the TYPO3 Varnish Extension can be called a great achievement of these 3 days. | |
TYPO3 and Varnish | |
Up to this point a TYPO3 extension for Varnish already existed. The process of this extension was that when changing a page in the TYPO3 backend, all URLs belonging to this page were collected and then sent individually to Varnish for deletion. This was not very practical |