Nick Ballenger d02a917f38 Commented out 'invalidation_service' section ... I commented out the entire 'invalidation_service' section from app_config.yml. It _should_ be sufficient to set 'enabled' to false in that block, in order to prevent the Redis/Resque based invalidation service from being used inside the postgres trigger for invalidating cache items, but it's actually easier to just comment out the whole block. See this portion of the Carto code for reference: 05a05fd695/app/models/user/db_service.rb (L1062-L1070) The branch we want to go down in that code is the middle one--we want to end up with `create_function_invalidate_varnish_http` running. That will create a postgres trigger based on hitting the Varnish server's HTTP listener, which is running on 6081. (You could have it hit the telnet port by taking the third branch of that code, but given that telnet isn't included in later Varnish versions, best not to.) You want to avoid the first branch of that code, `create_function_invalidate_varnish_invalidation_service`, because it includes this line: 05a05fd695/app/models/user/db_service.rb (L1601) That's calling a custom Redis command, `TCH`, which is defined in a repo that Carto has not open sourced--meaning the 'invalidation service' (as a Redis job queue for the Resque job runner) can't be used in open source Carto (unless you reverse engineer the Redis commands it uses.)		2019-07-18 16:17:28 -07:00
..
app_config.yml	Commented out 'invalidation_service' section	2019-07-18 16:17:28 -07:00
CartoDB-dev.js	Sync config files	2018-04-04 22:23:54 +02:00
cartodb.nginx.proxy.conf	Changing the Nginx config to a single file	2019-07-18 16:08:53 -07:00
database.yml	Rename active record adaptor	2018-07-27 09:11:15 +02:00
varnish.vcl	* Embed nginx inside Docker image so all services are reversed proxied behind port 80	2017-04-03 22:55:12 +02:00
WS-dev.js	Dataviews did not show due to Windshaft opening dataviews on own port instead of reverse proxy	2017-04-13 14:32:49 +02:00