Stefan Verhoeven

When building a new image, I get the same error from the sql api. Seems the api key is not in redis.

Checking if api keys exist inside container with: ```bash redis-cli -n 5 keys 'api_keys*' echo 'select * from api_keys;' | psql -U postgres -t carto_db_development ``` Both return nothing. Create...

During startup the api keys get generated. Another problem might be a cookie of a previous docker run, try to close the session or clear the cookie and relogin.

No idea, please ask at https://groups.google.com/forum/#!forum/cartodb

A list of valid file extensions that is checked in browser is at 1. lib/assets/javascripts/builder/config/upload-config.js, used when uploading file and is missing carto extension 2. lib/assets/javascripts/dashboard/common/upload-config.js, contains carto extension

`127.0.1.1` is valid for Debian/Ubuntu based operating systems. Which OS are you using which made the resolving of cartodb.localhost not work?

A note would be nice, we should be careful not to break the hosts file.

Nice, could you document the port usage in the README?

The Docker container exists when the cartodb rails web application dies. Can you share the log, retrieve with `docker logs `? I suspect exit code 134 is out of memory...

The "carto_db_development" is the central db and used for user management. The carto server is running in development mode, that is why the database is called "carto_db_development". Each user/organization has...