From 9cffc8781a82465d50f3f5d8339b42815873303a Mon Sep 17 00:00:00 2001
From: Rafa de la Torre <rtorre@carto.com>
Date: Tue, 9 Oct 2018 18:48:44 +0200
Subject: [PATCH] Sample configs: use PostGIS to generate MVT's

---
 NEWS.md                                    | 1 +
 config/environments/development.js.example | 2 +-
 config/environments/production.js.example  | 2 +-
 config/environments/staging.js.example     | 2 +-
 config/environments/test.js.example        | 2 +-
 5 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/NEWS.md b/NEWS.md
index 794e849b..7b592964 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -5,6 +5,7 @@ Released 2018-mm-dd
 
 New features
 - Aggregation time dimensions
+- Update sample configurations to use PostGIS to generate MVT's by default (as in production)
 - Upgrades Windshaft to [4.11.2](https://github.com/CartoDB/Windshaft/blob/4.11.2/NEWS.md#version-4112)
   - `pg-mvt`: Use `query-rewriter` to compose the query to render a MVT tile. If not defined, it will use a Default Query Rewriter.
   - `pg-mvt`: Fix bug while building query and there is no columns defined for the layer.
diff --git a/config/environments/development.js.example b/config/environments/development.js.example
index 87c98032..be15ca6c 100644
--- a/config/environments/development.js.example
+++ b/config/environments/development.js.example
@@ -130,7 +130,7 @@ var config = {
         //If enabled, MVTs will be generated with PostGIS directly, instead of using Mapnik,
         //PostGIS 2.4 is required for this to work
         //If disabled it will use Mapnik MVT generation
-        usePostGIS: false
+        usePostGIS: true
       },
       mapnik: {
           // The size of the pool of internal mapnik backend
diff --git a/config/environments/production.js.example b/config/environments/production.js.example
index 8e071acf..c058e27f 100644
--- a/config/environments/production.js.example
+++ b/config/environments/production.js.example
@@ -130,7 +130,7 @@ var config = {
         //If enabled, MVTs will be generated with PostGIS directly, instead of using Mapnik,
         //PostGIS 2.4 is required for this to work
         //If disabled it will use Mapnik MVT generation
-        usePostGIS: false
+        usePostGIS: true
       },
       mapnik: {
           // The size of the pool of internal mapnik backend
diff --git a/config/environments/staging.js.example b/config/environments/staging.js.example
index 60301a94..8d89e43f 100644
--- a/config/environments/staging.js.example
+++ b/config/environments/staging.js.example
@@ -130,7 +130,7 @@ var config = {
         //If enabled, MVTs will be generated with PostGIS directly, instead of using Mapnik,
         //PostGIS 2.4 is required for this to work
         //If disabled it will use Mapnik MVT generation
-        usePostGIS: false
+        usePostGIS: true
       },
       mapnik: {
           // The size of the pool of internal mapnik backend
diff --git a/config/environments/test.js.example b/config/environments/test.js.example
index d106995e..184675a7 100644
--- a/config/environments/test.js.example
+++ b/config/environments/test.js.example
@@ -130,7 +130,7 @@ var config = {
         //If enabled, MVTs will be generated with PostGIS directly, instead of using Mapnik,
         //PostGIS 2.4 is required for this to work
         //If disabled it will use Mapnik MVT generation
-        usePostGIS: false
+        usePostGIS: true
       },
       mapnik: {
           // The size of the pool of internal mapnik backend