croxton · September 5, 2021 23:34 · Jan 22, 2016 · Sep 10, 2015 · Jan 8, 2015 · Jan 8, 2015
diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -149,7 +149,7 @@ PHP 5.5 has opcode caching built in, but it is disabled by default. Edit `/usr/l
 	zend_extension=opcache.so
 	[opcache]
 	opcache.enable=1
-	opcache.enable_cli=1
+	opcache.enable_cli=0
 	opcache.memory_consumption=128
 	opcache.interned_strings_buffer=8
 	opcache.max_accelerated_files=4000

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -24,7 +24,7 @@ If you want to handle 100+ concurrent users with the same modest hardware see th
 
 ### PHP 5.5.13
 
-Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/Apache/ModRuid) we're using DSO as the PHP handler. My load testing shows it's faster and more stable than the only other sensible option on cPanel (FCGI), but YMMV. When cPanel finally adds PHP-FPM to EasyApache, use that (do NOT be tempted to go the DIY route). Tick the `Silence Deprecated Patch` if you are running EE < 2.8, since a few things throw deprecated notices in PHP 5.5.
+Since we're using [mod_ruid2](https://documentation.cpanel.net/display/EA/Apache+Module:+ModRuid2) we're using DSO as the PHP handler. My load testing shows it's faster and more stable than the only other sensible option on cPanel (FCGI), but YMMV. When cPanel finally adds PHP-FPM to EasyApache, use that (do NOT be tempted to go the DIY route). Tick the `Silence Deprecated Patch` if you are running EE < 2.8, since a few things throw deprecated notices in PHP 5.5.
 
 * Bcmath
 * CGI

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -112,7 +112,7 @@ Edit `/etc/my.cnf`
 	query-cache-type                = 1
 	query-cache-size                = 80M
 	query-cache-limit               = 256K
-	query-cache-min-res-unit        = 2K
+	query-cache-min-res-unit        = 2048
 	max-connections                 = 500
 	thread-cache-size               = 50
 	open-files-limit                = 65535

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -112,7 +112,7 @@ Edit `/etc/my.cnf`
 	query-cache-type                = 1
 	query-cache-size                = 80M
 	query-cache-limit               = 256K
-	query-cache-min-res-unit        = 2k
+	query-cache-min-res-unit        = 2K
 	max-connections                 = 500
 	thread-cache-size               = 50
 	open-files-limit                = 65535

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -112,7 +112,7 @@ Edit `/etc/my.cnf`
 	query-cache-type                = 1
 	query-cache-size                = 80M
 	query-cache-limit               = 256K
-	query-cache-min-res-unit 	= 2k
+	query-cache-min-res-unit        = 2k
 	max-connections                 = 500
 	thread-cache-size               = 50
 	open-files-limit                = 65535

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -110,8 +110,9 @@ Edit `/etc/my.cnf`
 	tmp-table-size                  = 64M
 	max-heap-table-size             = 64M
 	query-cache-type                = 1
-	query-cache-size                = 128M
-	query-cache-limit               = 2M
+	query-cache-size                = 80M
+	query-cache-limit               = 256K
+	query-cache-min-res-unit 	= 2k
 	max-connections                 = 500
 	thread-cache-size               = 50
 	open-files-limit                = 65535

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -1,4 +1,4 @@
-"Medium traffic" = able to handle around 50 concurrent users on average and burst up to 100 without causing your server to thrash.
+"Medium traffic" = able to handle around 50 concurrent users on average.
 
 If you want to handle 100+ concurrent users with the same modest hardware see the [Varnish](https://gist.github.com/croxton/d2294e9413ed3c4ebde1#varnish) section below.
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -1,6 +1,6 @@
-"Medium traffic" = able to handle around 50 concurrent users on average and burst up to 100-150 without causing your server to thrash.
+"Medium traffic" = able to handle around 50 concurrent users on average and burst up to 100 without causing your server to thrash.
 
-If you want to handle 500+ concurrent users with the same modest hardware see the [Varnish](https://gist.github.com/croxton/d2294e9413ed3c4ebde1#varnish) section below.
+If you want to handle 100+ concurrent users with the same modest hardware see the [Varnish](https://gist.github.com/croxton/d2294e9413ed3c4ebde1#varnish) section below.
 
 ### VPS
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -88,7 +88,7 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 
 ### My.cnf config for MySQL 5.6
 
-The following configuration is optimised for running EE websites *with a mix of MySIAM and InnoDB tables*. Uncomment sql-mode if you want to run MySQL in strict mode (some add-ons won't like it). Note that setting `performance_schema = 0` is esential for production sites, as this can use significant amounts of memory.
+The following configuration is optimised for running EE websites **with a mix of MySIAM and InnoDB tables**. Uncomment sql-mode if you want to run MySQL in strict mode (some add-ons won't like it). Note that setting `performance_schema = 0` is esential for production sites, as this can use significant amounts of memory.
 
 Edit `/etc/my.cnf`
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -88,7 +88,7 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 
 ### My.cnf config for MySQL 5.6
 
-The following configuration is optimised for running EE websites with a mix of MySIAM and InnoDB tables. Uncomment sql-mode if you want to run MySQL in strict mode (some add-ons won't like it). Note that setting `performance_schema = 0` is esential for production sites, as this can use significant amounts of memory.
+The following configuration is optimised for running EE websites *with a mix of MySIAM and InnoDB tables*. Uncomment sql-mode if you want to run MySQL in strict mode (some add-ons won't like it). Note that setting `performance_schema = 0` is esential for production sites, as this can use significant amounts of memory.
 
 Edit `/etc/my.cnf`
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -63,7 +63,7 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 - should be same as min spare servers
 
 **Server Limit** 65 
-- Assuming MySQL uses between 0.5 - 1GB, Linux and other services are using around 0.4GB, so you have between 2.6GB-3.1GB to allocate to Apache. If your httpd processes typically use around 40MB per process (normal for EE) then being conservative: 65x40MB = 2600MB (~2.54GB)
+- Assuming MySQL uses between 0.5 - 1GB (as it will if you use the config below), Linux and other services are using around 0.4GB, so you have between 2.6GB-3.1GB to allocate to Apache. If your httpd processes typically use around 40MB per process (normal for EE) then being conservative: 65x40MB = 2600MB (~2.54GB)
 
 - Don't rely on the Template Debugger to tell you how much a typical Apache process uses - run `top` in your terminal while your site is under load.
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -63,7 +63,7 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 - should be same as min spare servers
 
 **Server Limit** 65 
-- Assuming MySQL uses between 0.5 - 1GB, Linux and other services are using around 0.4GB, so you have between 2.6GB-3.1GB to allocate to Apache. If your httpd processes typically use around 40Mb per process (normal for EE) then being conservative: 65x40Mb = 2600Mb (~2.54GB)
+- Assuming MySQL uses between 0.5 - 1GB, Linux and other services are using around 0.4GB, so you have between 2.6GB-3.1GB to allocate to Apache. If your httpd processes typically use around 40MB per process (normal for EE) then being conservative: 65x40MB = 2600MB (~2.54GB)
 
 - Don't rely on the Template Debugger to tell you how much a typical Apache process uses - run `top` in your terminal while your site is under load.
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -63,7 +63,7 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 - should be same as min spare servers
 
 **Server Limit** 65 
-- Assuming MySQL uses between 0.5 - 1Gb, Linux and other services are using around 0.4Gb, so you have between 2.6Gb-3.1Gb to allocate to Apache. If your httpd processes typically use around 40Mb per process (normal for EE) then being conservative: 65x40Mb = 2600Mb.
+- Assuming MySQL uses between 0.5 - 1GB, Linux and other services are using around 0.4GB, so you have between 2.6GB-3.1GB to allocate to Apache. If your httpd processes typically use around 40Mb per process (normal for EE) then being conservative: 65x40Mb = 2600Mb (~2.54GB)
 
 - Don't rely on the Template Debugger to tell you how much a typical Apache process uses - run `top` in your terminal while your site is under load.
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -175,7 +175,7 @@ When you're done login to WHM and find the new Varnish control panel.
 
 On the advanced configuration page:
 
-* Set Cache time to Live to 600 seconds.
+* Set Cache time to Live to 600 seconds (go higher if you have a lot of content that doesn't change frequently).
 * Set Memory Cache to 250M (can go up to 2G, depends on how big site is and how much is cached).
 * Add these URLs using the 'URL opt-out' field: `admin\.php` and `ACT=`. (Add any other URLs you want to exclude from caching, e.g. 'system' if you still have that in your webroot).
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -175,7 +175,7 @@ When you're done login to WHM and find the new Varnish control panel.
 
 On the advanced configuration page:
 
-* Set Cache time to Live to 60 seconds (go higher if you dare or have heavy traffic).
+* Set Cache time to Live to 600 seconds.
 * Set Memory Cache to 250M (can go up to 2G, depends on how big site is and how much is cached).
 * Add these URLs using the 'URL opt-out' field: `admin\.php` and `ACT=`. (Add any other URLs you want to exclude from caching, e.g. 'system' if you still have that in your webroot).
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -88,7 +88,7 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 
 ### My.cnf config for MySQL 5.6
 
-The following configuration is optimised for running EE websites with a mix of MySIAM and InnoDB tables. Uncomment sql-mode if you want to run MySQL in strict mode (some add-ons won't like it).
+The following configuration is optimised for running EE websites with a mix of MySIAM and InnoDB tables. Uncomment sql-mode if you want to run MySQL in strict mode (some add-ons won't like it). Note that setting `performance_schema = 0` is esential for production sites, as this can use significant amounts of memory.
 
 Edit `/etc/my.cnf`
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -77,6 +77,7 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 **Keep-Alive** Off  
 
 - You may want to turn on Keep Alives, but if you do use low limits:
+
 **Keep-Alive Timeout** 1    
 **Max Keep-Alive Requests** 50   
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -62,26 +62,29 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 **Start Servers** 3 
 - should be same as min spare servers
 
-**Server Limit** 75 
-- No more than 75% of available ram. If your webpages typically uses 40Mb per process then 75x40Mb = 3000Mb of ram used. Don't rely on the Template Debugger to tell you how much a typical Apache process uses - run `top` in your terminal while your site is under load.
+**Server Limit** 65 
+- Assuming MySQL uses between 0.5 - 1Gb, Linux and other services are using around 0.4Gb, so you have between 2.6Gb-3.1Gb to allocate to Apache. If your httpd processes typically use around 40Mb per process (normal for EE) then being conservative: 65x40Mb = 2600Mb.
+
+- Don't rely on the Template Debugger to tell you how much a typical Apache process uses - run `top` in your terminal while your site is under load.
 
-**Max Request Workers** 75 
+**Max Request Workers** 65 
 - Same as server limit
 
-**Max Connections Per Child** 3750
+**Max Connections Per Child** 3250
 - Should be at between 10x - 50x the max request workers.
 - Higher means more chance of memory leaks from poorly coded PHP scripts (bad) but fewer new processes (good), so experiment.
 
-**Keep-Alive** On    
+**Keep-Alive** Off  
+
+- You may want to turn on Keep Alives, but if you do use low limits:
 **Keep-Alive Timeout** 1    
-**Max Keep-Alive Requests** 50    
+**Max Keep-Alive Requests** 50   
 
-- You may want to turn off Keep Alives if Apache regularly uses up the server's limits, you use CDNs for your assets, or run a reverse-proxy like [Nginx Admin](http://www.nginxcp.com/) for static files.
 - See: http://abdussamad.com/archives/169-Apache-optimization:-KeepAlive-On-or-Off.html
+- Also: http://www.reddit.com/r/webdev/comments/1bs4t0/3_small_tweaks_to_make_apache_fly/
 
 **Time Out** 120
 
-
 ### My.cnf config for MySQL 5.6
 
 The following configuration is optimised for running EE websites with a mix of MySIAM and InnoDB tables. Uncomment sql-mode if you want to run MySQL in strict mode (some add-ons won't like it).

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -62,14 +62,14 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 **Start Servers** 3 
 - should be same as min spare servers
 
-**Server Limit** 100 
-- No more than 75% of available ram. If your webpages typically uses 30Mb per process then 100x30Mb = 3000Mb of ram used. Don't rely on the Template Debugger to tell you how much a typical Apache process uses - run `top` in your terminal while your site is under load.
+**Server Limit** 75 
+- No more than 75% of available ram. If your webpages typically uses 40Mb per process then 75x40Mb = 3000Mb of ram used. Don't rely on the Template Debugger to tell you how much a typical Apache process uses - run `top` in your terminal while your site is under load.
 
-**Max Request Workers** 100 
+**Max Request Workers** 75 
 - Same as server limit
 
-**Max Connections Per Child** 5000
-- Should be at between 10x - 50x the max clients.
+**Max Connections Per Child** 3750
+- Should be at between 10x - 50x the max request workers.
 - Higher means more chance of memory leaks from poorly coded PHP scripts (bad) but fewer new processes (good), so experiment.
 
 **Keep-Alive** On    

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -100,6 +100,7 @@ Edit `/etc/my.cnf`
 	innodb                          = FORCE
 	innodb-strict-mode              = 1
 	myisam-recover                  = FORCE,BACKUP
+	performance_schema              = 0
 	 
 	# CACHES AND LIMITS # 
 	tmp-table-size                  = 64M

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -102,10 +102,10 @@ Edit `/etc/my.cnf`
 	myisam-recover                  = FORCE,BACKUP
 	 
 	# CACHES AND LIMITS # 
-	tmp-table-size                  = 48M
-	max-heap-table-size             = 48M
+	tmp-table-size                  = 64M
+	max-heap-table-size             = 64M
 	query-cache-type                = 1
-	query-cache-size                = 64M
+	query-cache-size                = 128M
 	query-cache-limit               = 2M
 	max-connections                 = 500
 	thread-cache-size               = 50
@@ -123,7 +123,7 @@ Edit `/etc/my.cnf`
 	innodb-buffer-pool-size         = 512M
 
 	# MyISAM #
-	key-buffer-size                = 512M
+	key-buffer-size                = 256M
 
 	# LOGGING #
 	log-error                      = /var/lib/mysql/mysql-error.log

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -82,11 +82,11 @@ Since we're using [mod_ruid2](http://docs.cpanel.net/twiki/bin/view/EasyApache/A
 **Time Out** 120
 
 
-### MySQL config
+### My.cnf config for MySQL 5.6
 
-Edit `/etc/my.cnf`
+The following configuration is optimised for running EE websites with a mix of MySIAM and InnoDB tables. Uncomment sql-mode if you want to run MySQL in strict mode (some add-ons won't like it).
 
-Optimised for running EE websites with a mix of MySIAM and InnoDB tables. Uncomment sql-mode if you want to run MySQL in strict mode (some add-ons won't like it).
+Edit `/etc/my.cnf`
 
 	[mysqld]
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -120,10 +120,10 @@ Optimised for running EE websites with a mix of MySIAM and InnoDB tables. Uncomm
 	innodb_additional_mem_pool_size = 20M
 	innodb-flush-log-at-trx-commit  = 2
 	innodb-file-per-table           = 1
-	innodb-buffer-pool-size         = 2G
+	innodb-buffer-pool-size         = 512M
 
 	# MyISAM #
-	key-buffer-size                = 64M
+	key-buffer-size                = 512M
 
 	# LOGGING #
 	log-error                      = /var/lib/mysql/mysql-error.log

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -1,6 +1,6 @@
 "Medium traffic" = able to handle around 50 concurrent users on average and burst up to 100-150 without causing your server to thrash.
 
-If you want to handle far, far more traffic with the same modest hardware see the [Varnish](https://gist.github.com/croxton/d2294e9413ed3c4ebde1#varnish) section below.
+If you want to handle 500+ concurrent users with the same modest hardware see the [Varnish](https://gist.github.com/croxton/d2294e9413ed3c4ebde1#varnish) section below.
 
 ### VPS
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -174,7 +174,11 @@ On the advanced configuration page:
 * Set Memory Cache to 250M (can go up to 2G, depends on how big site is and how much is cached).
 * Add these URLs using the 'URL opt-out' field: `admin\.php` and `ACT=`. (Add any other URLs you want to exclude from caching, e.g. 'system' if you still have that in your webroot).
 
-Now you need to customize `/etc/varnish/default.vcl`. The code below is adapted from Unixy's config and [this article](http://ellislab.com/blog/entry/making-sites-fly-with-varnish) by Kevin Cupp. It enables the Mustash Varnish plugin or Kevin's own Purge extension to purge the Varnish cache when cache-breaking rules are triggered. Note also that Purging is only enabled for one domain (replace `example.com` with your domain). Refer to the article if you want to make further changes to the vcl config such as enabling Edge Side Includes.
+Now you need to customize `/etc/varnish/default.vcl`. The code below is adapted from Unixy's config and [this article](http://ellislab.com/blog/entry/making-sites-fly-with-varnish) by Kevin Cupp. It enables the Mustash Varnish plugin or Kevin's Purge extension to purge the Varnish cache when cache-breaking rules are triggered. With Mustash, Varnish cache-breaking is granular: when Stash full page caches are cleared in the CP or cache-breaking is triggered by rules, the corresponding Varnish cache object will be cleared.
+
+Refer to the article if you want to make further changes to the vcl config such as enabling Edge Side Includes.
+
+Note: If you have set a custom `cookie_prefix` in your site config, change `exp_sessionid` to `your_prefix_sessionid`.
 
 Restart Varnish (from WHM control panel) after editing `default.vcl`.
 
@@ -388,7 +392,7 @@ Restart Varnish (from WHM control panel) after editing `default.vcl`.
 	     set resp.http.X-Cache = "MISS";
 	   }
 	   
-	   # test
+	   # cache object url
 	   set resp.http.X-Url = req.url;
 
 	}

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -182,8 +182,6 @@ Restart Varnish (from WHM control panel) after editing `default.vcl`.
 	# Copyright (c) UNIXY  -  http://www.unixy.net    #
 	# The leading truly fully managed server provider #
 	###################################################
-
-	# Adapted for ExpressionEngine
 
 	include "/etc/varnish/cpanel.backend.vcl";
 
@@ -263,16 +261,22 @@ Restart Varnish (from WHM control panel) after editing `default.vcl`.
 
 	# Purge
 	if (req.request == "PURGE") {
-	        if (!client.ip ~ acl127_0_0_1) {error 405 "Not permitted";}
-	        return (lookup);
+		if (!client.ip ~ acl127_0_0_1) {error 405 "Not permitted";}
+	    return (lookup);
 	}
 
-	# EE purge (via Mustash Varnish plugin)
+	# Clear the cache for an entire domain
 	if (req.request == "EE_PURGE") {
-		ban("req.http.host ~ example.com && req.url ~ ^/.*$");
+		ban("req.url ~ ^/.*$ && req.http.host == "+req.http.host);
 		error 200 "Purged";
 	}
 
+	# Clear any cached object that matches the exact req.url
+	if (req.request == "EE_PURGE_URL") {
+	    ban("req.url == "+req.url+" && req.http.host == "+req.http.host);
+	    error 200 "Purged";
+	}
+
 	## Default request checks
 	if (req.request != "GET" &&
 	req.request != "HEAD" &&
@@ -284,10 +288,16 @@ Restart Varnish (from WHM control panel) after editing `default.vcl`.
 		return (pipe);
 	}
 
+	# Don't cache dynamic content
 	if (req.request != "GET" && req.request != "HEAD") {
 		return (pass);
 	}
 
+	# Don't cache content for logged in users
+	if (req.http.Cookie ~ "exp_sessionid") {
+		return (pass);
+	}
+
 	## Modified from default to allow caching if cookies are set, but not http auth
 	if (req.http.Authorization) {
 		return (pass);
@@ -377,6 +387,9 @@ Restart Varnish (from WHM control panel) after editing `default.vcl`.
 	else {
 	     set resp.http.X-Cache = "MISS";
 	   }
+	   
+	   # test
+	   set resp.http.X-Url = req.url;
 
 	}
 
@@ -434,3 +447,4 @@ Restart Varnish (from WHM control panel) after editing `default.vcl`.
 
 
 
+
diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -1,6 +1,6 @@
 "Medium traffic" = able to handle around 50 concurrent users on average and burst up to 100-150 without causing your server to thrash.
 
-If you want to handle far more with the same modest hardware see the [Varnish](https://gist.github.com/croxton/d2294e9413ed3c4ebde1#varnish) section below.
+If you want to handle far, far more traffic with the same modest hardware see the [Varnish](https://gist.github.com/croxton/d2294e9413ed3c4ebde1#varnish) section below.
 
 ### VPS
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -1,6 +1,6 @@
 "Medium traffic" = able to handle around 50 concurrent users on average and burst up to 100-150 without causing your server to thrash.
 
-If you want to handle far more with this modest hardware see the Varnish section below.
+If you want to handle far more with the same modest hardware see the [Varnish](https://gist.github.com/croxton/d2294e9413ed3c4ebde1#varnish) section below.
 
 ### VPS
 

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -168,7 +168,7 @@ Once you have downloaded the zip from Unixy, upload it to /usr/src. Then SSH int
 
 When you're done login to WHM and find the new Varnish control panel.
 
-On the advanaced configuration page:
+On the advanced configuration page:
 
 * Set Cache time to Live to 60 seconds (go higher if you dare or have heavy traffic).
 * Set Memory Cache to 250M (can go up to 2G, depends on how big site is and how much is cached).
@@ -178,6 +178,13 @@ Now you need to customize `/etc/varnish/default.vcl`. The code below is adapted
 
 Restart Varnish (from WHM control panel) after editing `default.vcl`.
 
+	###################################################
+	# Copyright (c) UNIXY  -  http://www.unixy.net    #
+	# The leading truly fully managed server provider #
+	###################################################
+
+	# Adapted for ExpressionEngine
+
 	include "/etc/varnish/cpanel.backend.vcl";
 
 	include "/etc/varnish/backends.vcl";

diff --git a/cpanel_vps_eecms_config.md b/cpanel_vps_eecms_config.md
@@ -174,7 +174,9 @@ On the advanaced configuration page:
 * Set Memory Cache to 250M (can go up to 2G, depends on how big site is and how much is cached).
 * Add these URLs using the 'URL opt-out' field: `admin\.php` and `ACT=`. (Add any other URLs you want to exclude from caching, e.g. 'system' if you still have that in your webroot).
 
-Now you need to customize `/etc/varnish/default.vcl`. The code below is adapted from Unixy's config and [this womderful article](http://ellislab.com/blog/entry/making-sites-fly-with-varnish) by Kevin Cupp. It enables the Mustash Varnish plugin to purge the Varnish cache when cache-breaking rules are triggered. Note also that Purging is only enabled for one domain (replace `example.com` with your domain).
+Now you need to customize `/etc/varnish/default.vcl`. The code below is adapted from Unixy's config and [this article](http://ellislab.com/blog/entry/making-sites-fly-with-varnish) by Kevin Cupp. It enables the Mustash Varnish plugin or Kevin's own Purge extension to purge the Varnish cache when cache-breaking rules are triggered. Note also that Purging is only enabled for one domain (replace `example.com` with your domain). Refer to the article if you want to make further changes to the vcl config such as enabling Edge Side Includes.
+
+Restart Varnish (from WHM control panel) after editing `default.vcl`.
 
 	include "/etc/varnish/cpanel.backend.vcl";
No results found