{"id":3359,"date":"2017-09-07T12:48:12","date_gmt":"2017-09-07T12:48:12","guid":{"rendered":"https:\/\/cloudkul.com\/blog\/?p=3359"},"modified":"2018-07-17T09:22:03","modified_gmt":"2018-07-17T09:22:03","slug":"magento-2-and-varnish-cache-integration-with-docker-compose","status":"publish","type":"post","link":"https:\/\/cloudkul.com\/blog\/magento-2-and-varnish-cache-integration-with-docker-compose\/","title":{"rendered":"Magento 2 and Varnish Cache Integration With Docker-Compose"},"content":{"rendered":"

In our last\u00a0blog,<\/a>\u00a0after being introduced to docker-compose, we had discussed the deployment of multi-container architecture in Docker. Using this tool we had setup Magento 2 running with apache2 server and mysql-server on separate containers interlinked with each other. We had also discussed the volume\u00a0mapping, ports allocation, containers linking etc techniques for docker-compose.yml file.<\/p>\n

As we are now familiar with docker and docker-compose, their working and their integration with applications (Magento 2 in our case), we will now take a further step ahead. In our previous blogs, we have installed Magento 2 with default configurations. We were focused on infrastructure performance rather than application optmisation. Moving further, in this blog we will discuss integration of Varnish cache with Magento 2 on the architecture of Docker and of course we will be using docker-compose to setup this architecture as we did earlier.<\/p>\n

 <\/p>\n

Introduction To Varnish Cache<\/strong><\/h2>\n

 <\/p>\n

If you are familiar with Magento 2 and own your store then you might have heard of Varnish cache once in a while. If not all of you, then those who are struggling with high traffic on their Magento 2 store, they must have considered using some cache server at some point. Those who are not familiar with Varnish cache, following lines are for you,<\/p>\n

 <\/p>\n

Quoting from Varnish docs,\u00a0Varnish cache is a web application accelerator also known as a caching HTTP reverse proxy. It\u00a0is a powerful open source HTTP engine\/reverse HTTP proxy that can speed up a website by up to 1000 percent by doing exactly what its name implies: caching (or storing) a copy of a webpage the first time a user visits.\u00a0Varnish cache\u00a0visits your server once to cache the page, then all future requests for the same page will be served by\u00a0Varnish cache.\u00a0<\/strong><\/em><\/p><\/blockquote>\n

 <\/p>\n

Unlike other web-accelerators, Varnish cache deals only with HTTP traffic. The key element in Varnish cache setup is its Varnish Configuration Language (VCL) file. VCL files are needed to be customised for specific frameworks or applications. Default VCL file does not work directly with all the applications. If you consider Varnish Cache as a radio, then you have it tune it according your server needs. Luckily for us, Magento 2 works out of box with Varnish Cache and provides its own VCL file for its setup. Also from Magento 2 docs,<\/p>\n

 <\/p>\n

\u201cWe strongly recommend you use Varnish in production. The built-in full-page caching (to either the file system or database) is much slower than Varnish, and Varnish is designed to accelerate HTTP traffic.\u201d<\/strong><\/em><\/p><\/blockquote>\n

 <\/p>\n

Magento 2 And Varnish Cache Setup With Docker-Compose<\/strong><\/h2>\n

 <\/p>\n

As we are still on our multi-container docker architecture, we will be using separate containers for apache2 server, mysql-server and varnish cache server for its integration with Magento 2 on Ubuntu 16.04.<\/strong> As separate containers will require inter-linking with each other, we will be using docker-compose tool to achieve this architecture.<\/p>\n

The parent directory holding all the files\/directories will be considered as the project name. Custom project name can also be in set docker-compose.yml file. Here we are creating separate directories for apache2, mysql server and varnish cache server setup that hold their Dockerfile(s) and their associated volumes.<\/strong><\/em><\/p>\n

Take a note that: following the same approach,\u00a0Magento 2 files will be placed on our host. As it is a good practice to keep application files on host so that it will not be lost if containers or images get accidentally removed. These magento files will be mapped from host to running docker container<\/strong>.<\/em><\/p>\n

We are also using supervisor to control all three of our servers\u00a0in their respective containers. Apart from controlling these servers, supervisor is also running various commands and scripts that will be mentioned later in this blog.<\/p>\n

To begin with create a directory on your Ubuntu 16.04 server for this project. Our directory architecture will be something like:<\/p>\n

 <\/p>\n