cartodb/Windshaft-cartodb
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

removing raster image on timeout error

Browse Source
This commit is contained in:
Simon Martín 2018-02-02 16:38:47 +01:00
parent bbe8d4e820
commit 47c8e828df
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
config/environments/development.js.example
View File

@ -338,7 +338,7 @@ var config = {
// Use this as a feature flags enabling/disabling mechanism // Use this as a feature flags enabling/disabling mechanism
,enabledFeatures: { ,enabledFeatures: {
// whether it should intercept tile render errors an act based on them, enabled by default. // whether it should intercept tile render errors an act based on them, enabled by default.
onTileErrorStrategy: true, onTileErrorStrategy: false,
// whether the affected tables for a given SQL must query directly postgresql or use the SQL API // whether the affected tables for a given SQL must query directly postgresql or use the SQL API
cdbQueryTablesFromPostgres: true, cdbQueryTablesFromPostgres: true,
// whether in mapconfig is available stats & metadata for each layer // whether in mapconfig is available stats & metadata for each layer

2
config/environments/production.js.example
View File

@ -338,7 +338,7 @@ var config = {
// Use this as a feature flags enabling/disabling mechanism // Use this as a feature flags enabling/disabling mechanism
,enabledFeatures: { ,enabledFeatures: {
// whether it should intercept tile render errors an act based on them, enabled by default. // whether it should intercept tile render errors an act based on them, enabled by default.
onTileErrorStrategy: true, onTileErrorStrategy: false,
// whether the affected tables for a given SQL must query directly postgresql or use the SQL API // whether the affected tables for a given SQL must query directly postgresql or use the SQL API
cdbQueryTablesFromPostgres: true, cdbQueryTablesFromPostgres: true,
// whether in mapconfig is available stats & metadata for each layer // whether in mapconfig is available stats & metadata for each layer

2
config/environments/staging.js.example
View File

@ -338,7 +338,7 @@ var config = {
// Use this as a feature flags enabling/disabling mechanism // Use this as a feature flags enabling/disabling mechanism
,enabledFeatures: { ,enabledFeatures: {
// whether it should intercept tile render errors an act based on them, enabled by default. // whether it should intercept tile render errors an act based on them, enabled by default.
onTileErrorStrategy: true, onTileErrorStrategy: false,
// whether the affected tables for a given SQL must query directly postgresql or use the SQL API // whether the affected tables for a given SQL must query directly postgresql or use the SQL API
cdbQueryTablesFromPostgres: true, cdbQueryTablesFromPostgres: true,
// whether in mapconfig is available stats & metadata for each layer // whether in mapconfig is available stats & metadata for each layer

2
config/environments/test.js.example
View File

@ -333,7 +333,7 @@ var config = {
// Use this as a feature flags enabling/disabling mechanism // Use this as a feature flags enabling/disabling mechanism
,enabledFeatures: { ,enabledFeatures: {
// whether it should intercept tile render errors an act based on them, enabled by default. // whether it should intercept tile render errors an act based on them, enabled by default.
onTileErrorStrategy: true, onTileErrorStrategy: false,
// whether the affected tables for a given SQL must query directly postgresql or use the SQL API // whether the affected tables for a given SQL must query directly postgresql or use the SQL API
cdbQueryTablesFromPostgres: true, cdbQueryTablesFromPostgres: true,
// whether in mapconfig is available stats & metadata for each layer // whether in mapconfig is available stats & metadata for each layer