seo_cache 0.9.0 → 0.10.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e101c3d2b9260ac681e1d6ffc399c88e98c5f1edc69f3148790e6b63abda2ad0
-  data.tar.gz: de86f2455bb55ecbbf70365c068f6ba3b4f865cb59dfb352975a6f14d4599681
+  metadata.gz: 4ff4b04ea72963e8609ce8ebc7ddd53e4c2f05087f80f13363f4810bc2a0f46f
+  data.tar.gz: 8072db1df79a2a2a530815fe6054fd40f3abbd162b782de2304f6af7ada944d1
 SHA512:
-  metadata.gz: 2539f235f5e806422cbd969723a3a83cb671b270869ec02f73efffa2d15f96bf401155bcc48ea462ad1ee7fac2b994692b94103decd33ec61f5ee88672c5ad16
-  data.tar.gz: d871e975c11792c10bde694427e184e19d1b7effa0ff5eb90bd88daa05ed1b42a66deccbe111e2435fb0972df24556a88c462956eb47f59d4c1875fe94e66be2
+  metadata.gz: 64088bbe57c6e6859ba0c0b578112b52bfeffd6b2f64f9cef2f88a63c946bfb27183f94245fe4ed8bba37731fde0cebc19a783972cb92ac0692927b8d6bc7a23
+  data.tar.gz: 1ac9cbe9ee21dbeee0a675f88799c48bdc23b85b6296d9e971b954204ad03aac5116b653095ec0a70481e1f579be138e8bb659f37d12fdc3c710978f3887ae62

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 ## 0.9.0
 
+- Update Readme for nginx configuration
+
+## 0.9.0
+
 - Update gems
 - Don't cache response if status is not 200
 - Add 'seo_mode' variable to env to detect si seo mode is currently active

data/README.md

@@ -186,6 +186,33 @@ You can add the `force_cache: true` option to `SeoCache::PopulateCache` for over
 If you use disk caching, add to your Nginx configuration:
 
 ```nginx
+# Before any block:
+map $http_user_agent $limit_bots {
+    default 0;
+    ~*(google|bing|yandex|msnbot) 1;
+}
+
+map $request_method $is_get {
+    default 0;
+    GET 1;
+}
+
+# Before location block:
+set $bot_request '';
+if ($is_get) {
+      set $bot_request 'GET_';
+}
+
+if ($limit_bots) { 
+  set $bot_request "${bot_request}BOT"; 
+}
+
+set $cache_extension '';
+if ($bot_request = GET_BOT) {
+  set $cache_extension '.html';
+}
+
+# Inside location block:
 location / {
     # Ignore url with blacklisted params (e.g. page)
     if ($arg_page) {
@@ -195,29 +222,16 @@ location / {
       break;
     }
     
-    # cached pages
-    set $cache_extension '';
-    if ($request_method = GET) {
-      set $cache_extension '.html';
-    }
-    
-    # Index HTML Files
-    if (-f $document_root/seo_cache/$uri/index$cache_extension) {
-      rewrite (.*) /seo_cache/$1/index.html break;
-    }
-    
-    # Other HTML Files
-    if (-f $document_root/seo_cache/$uri$cache_extension) {
-      rewrite (.*) /seo_cache/$1.html break;
-    }
-    
-    # All
-    if (-f $document_root/seo_cache/$uri) {
-      rewrite (.*) /seo_cache/$1 break;
-    }
+    try_files /seo_cache/$uri/index$cache_extension /seo_cache/$uri$cache_extension /seo_cache/$uri $uri @rubyproxy;
+}
+
+location @rubyproxy {
+    ...
 }
 ```
 
+This configuration allow you to use SEO cache only for bots (you can add other bots) and GET requests. For users, you don't want to use the cached page (user connection, basket, ...). The performance are less important for users then bots.
+
 ## Heroku case
 
 If you use Heroku server, you can't store file on dynos. But you have two alternatives :

data/lib/seo_cache/version.rb

@@ -1,3 +1,3 @@
 module SeoCache
-  VERSION = '0.9.0'.freeze
+  VERSION = '0.10.0'.freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: seo_cache
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.10.0
 platform: ruby
 authors:
 - FloXcoder
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-09-23 00:00:00.000000000 Z
+date: 2019-10-04 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport