Changeset 3397819
- Timestamp:
- 11/18/2025 07:47:35 AM (4 months ago)
- Location:
- tnc-toolbox
- Files:
-
- 2 edited
-
tags/2.0.7/readme.txt (modified) (4 diffs)
-
trunk/readme.txt (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
tnc-toolbox/tags/2.0.7/readme.txt
r3397813 r3397819 41 41 _Please let us know your ideas on [GitHub](https://github.com/The-Network-Crew/TNC-Toolbox-for-WordPress/) - we'd love to hear from you!_ 42 42 43 == Caching Deployments == 44 45 **Caching ideals:** 46 - Don't forget, ea-NGINX (reverse proxy caching) is meant to be 2nd-level 47 - ie. Make sure your WP site also has on-site caching, like WP Super Cache 48 - You can go further with caching, and should: like browser-caching assets! 49 50 **3-layer Cache:** 51 1. NGINX Caching Proxy (ahead of Apache) 52 2. WP Super Cache, WP Rocket, etc on-site 53 3. htaccess/etc rules for Browser Caching 54 55 **This way, you can ensure maximum efficiency!** 56 57 The key is to purge when stale, so properly configuring your WP Plugin Cache is critical to ensuring that you don't end up with cache misses due to stale data that could've/should've been purged by garbage collection, preloading, etc, rule-sets. 58 43 59 == Updating from v1 to v2.x.x == 44 60 … … 64 80 65 81 Note: To do this, you require `root` access to the Server. 66 67 == Caching Deployments ==68 69 **Caching ideals:**70 - Don't forget, ea-NGINX (reverse proxy caching) is meant to be 2nd-level71 - ie. Make sure your WP site also has on-site caching, like WP Super Cache72 - You can go further with caching, and should: like browser-caching assets!73 74 **3-layer Cache:**75 1. NGINX Caching Proxy (ahead of Apache)76 2. WP Super Cache, WP Rocket, etc on-site77 3. htaccess/etc rules for Browser Caching78 79 **This way, you can ensure maximum efficiency!**80 81 The key is to purge when stale, so properly configuring your WP Plugin Cache is critical to ensuring that you don't end up with cache misses due to stale data that could've/should've been purged by garbage collection, preloading, etc, rule-sets.82 82 83 83 == Screenshots == … … 111 111 112 112 1. To use ea-NGINX features, your Hosting needs to be on cPanel 113 2. Acquire a cPanel API Token(cPanel > Manage API Tokens)113 2. Acquire a [cPanel API Token](https://docs.cpanel.net/cpanel/security/manage-api-tokens-in-cpanel/) (cPanel > Manage API Tokens) 114 114 3. Configure the TNC Toolbox plugin inside WordPress 115 115 … … 123 123 6. Save the config & use WP as-normal! 124 124 125 [cPanel Docs re: API Tokens](https://docs.cpanel.net/cpanel/security/manage-api-tokens-in-cpanel/) 126 127 ** Updating from v1 to v2:** 125 **Updating from v1 to v2:** 128 126 129 127 On every website running the plugin, check that: 130 131 128 1. Website is reporting v2.x.x plugin version. 132 129 2. Plugin has been activated post-update. * -
tnc-toolbox/trunk/readme.txt
r3397813 r3397819 41 41 _Please let us know your ideas on [GitHub](https://github.com/The-Network-Crew/TNC-Toolbox-for-WordPress/) - we'd love to hear from you!_ 42 42 43 == Caching Deployments == 44 45 **Caching ideals:** 46 - Don't forget, ea-NGINX (reverse proxy caching) is meant to be 2nd-level 47 - ie. Make sure your WP site also has on-site caching, like WP Super Cache 48 - You can go further with caching, and should: like browser-caching assets! 49 50 **3-layer Cache:** 51 1. NGINX Caching Proxy (ahead of Apache) 52 2. WP Super Cache, WP Rocket, etc on-site 53 3. htaccess/etc rules for Browser Caching 54 55 **This way, you can ensure maximum efficiency!** 56 57 The key is to purge when stale, so properly configuring your WP Plugin Cache is critical to ensuring that you don't end up with cache misses due to stale data that could've/should've been purged by garbage collection, preloading, etc, rule-sets. 58 43 59 == Updating from v1 to v2.x.x == 44 60 … … 64 80 65 81 Note: To do this, you require `root` access to the Server. 66 67 == Caching Deployments ==68 69 **Caching ideals:**70 - Don't forget, ea-NGINX (reverse proxy caching) is meant to be 2nd-level71 - ie. Make sure your WP site also has on-site caching, like WP Super Cache72 - You can go further with caching, and should: like browser-caching assets!73 74 **3-layer Cache:**75 1. NGINX Caching Proxy (ahead of Apache)76 2. WP Super Cache, WP Rocket, etc on-site77 3. htaccess/etc rules for Browser Caching78 79 **This way, you can ensure maximum efficiency!**80 81 The key is to purge when stale, so properly configuring your WP Plugin Cache is critical to ensuring that you don't end up with cache misses due to stale data that could've/should've been purged by garbage collection, preloading, etc, rule-sets.82 82 83 83 == Screenshots == … … 111 111 112 112 1. To use ea-NGINX features, your Hosting needs to be on cPanel 113 2. Acquire a cPanel API Token(cPanel > Manage API Tokens)113 2. Acquire a [cPanel API Token](https://docs.cpanel.net/cpanel/security/manage-api-tokens-in-cpanel/) (cPanel > Manage API Tokens) 114 114 3. Configure the TNC Toolbox plugin inside WordPress 115 115 … … 123 123 6. Save the config & use WP as-normal! 124 124 125 [cPanel Docs re: API Tokens](https://docs.cpanel.net/cpanel/security/manage-api-tokens-in-cpanel/) 126 127 ** Updating from v1 to v2:** 125 **Updating from v1 to v2:** 128 126 129 127 On every website running the plugin, check that: 130 131 128 1. Website is reporting v2.x.x plugin version. 132 129 2. Plugin has been activated post-update. *
Note: See TracChangeset
for help on using the changeset viewer.