Another Carto Synch - Githubissues

Sync code from Carto into Tileo. Copied and modified instructions from https://github.com/splashblot/dronedb/issues/101

Every month we should:

[ ] Fast-forward the master branch to pick up latest changes
[ ] Read NEWS.md in all relevant repos (here and here and here and here as well ... probably more) and adjust as necessary
[ ] Pick up any necessary changes to config files (app_config.yml and here and here as well)
[ ] Check /diagnosis and fix any regressions
[ ] Peek at sverhoeven's repo for any lessons learned
[ ] Merge the tileo-develop branch
[ ] Create new tileo-sync- tag for all involved repos
[ ] Merge and resolve conflicts
[ ] Merge to from tileo-sync - to tileo-develop branch and test
[ ] Ready to be merged to to tileo branch!

May-specific tasks (carry-over!):

[x] ~~Make sure infowindows work in *.tileo.co~~
[ ] Deploy new DO: dataservices, bigmetadata, etc. See here and here.
[x] ~~Add the crankshaft extension to the template_postgis database as per this suggestion~~
[ ] Fix/upload NPM package to use for uploading data to tileo.co instead of carto.com, see here
[ ] (optional) https://github.com/sverhoeven/docker-cartodb/commit/bbf2c543256ca4ef0f84099b9a680ded6108e756

June-specific tasks (carry-over!):

[ ] (optional) Check to see if all DO changes landed (see issues 11663 and 12682, plus https://github.com/CartoDB/cartodb/milestone/135)
[x] ~~Re-brand email templates & Org pages~~

splashblot / dronedb