Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
litespeed_wiki:cache:lscache:wordpress [2015/10/20 20:37] Michael Alegre [Discussion] |
litespeed_wiki:cache:lscache:wordpress [2017/01/03 21:31] Michael Alegre removed |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== LSCache + WordPress Configuration ====== | ====== LSCache + WordPress Configuration ====== | ||
| + | |||
| + | **Note: This page describes an easy way to set up simple caching for WordPress installations. With the release of LiteSpeed Cache for WordPress, though, this solution is now deprecated. Click [[litespeed_wiki:cache:lscwp|here]] for the LiteSpeed Cache for WordPress installation and configuration manual.** | ||
| LSCache, similar to Varnish cache, is a simpler and more efficient page caching solution built-in to LiteSpeed Web Server. When used in conjunction with WordPress, the Internets leading content management system, you can expect significant performance gains with a quick and easy setup. Cache management is also made significantly easier and more flexible with the ability to use rewrite rules to customize LSCache's behavior. | LSCache, similar to Varnish cache, is a simpler and more efficient page caching solution built-in to LiteSpeed Web Server. When used in conjunction with WordPress, the Internets leading content management system, you can expect significant performance gains with a quick and easy setup. Cache management is also made significantly easier and more flexible with the ability to use rewrite rules to customize LSCache's behavior. | ||
| Line 15: | Line 17: | ||
| It is recommended that this directory be on a dedicated disk or disk array in RAID 0 configuration. | It is recommended that this directory be on a dedicated disk or disk array in RAID 0 configuration. | ||
| - | |||
| - | |||
| - | **Note:** You will need to create the desired directory before setting it as the **Storage Path** through the WebAdmin. Do this through the command line. | ||
| For example: | For example: | ||