search

chriswhong / docker-cartodb

Dockerization for CartoDB
126 stars 53 forks source link

Update sep 2017 #22

Closed chriswhong closed 7 years ago

chriswhong commented 7 years ago

This PR includes changes to Dockerfile and the create_user script that yielded a successful build on 3 September 2017 (carto UI v.4.9.54)

thadk commented 7 years ago

I was able to get this working with my old docker volumes! Thanks and nice work.

The new version does actually seem to be consistently rendering more than a subset of my 68mil points now (referring to the feature truncating bug that the carto team suggested to us as being recently fixed at js.geo).

I may have had to manually bundle exec rake db:migrate for the old database and I definitely needed to use the database console to update the users' last_name to a string and org_admin to TRUE.

chriswhong commented 7 years ago

Hi @thadk, thanks for the feedback! I was happy to get the build working on its own but had not yet tried to make it use volumes from a previous version.

I may have had to manually bundle exec rake db:migrate for the old database and I definitely needed to use the database console to update the users' last_name to a string and org_admin to TRUE.

I was expecting to have to do a rake migrate, but why did you need to change the user's last name and org_admin? Can you say more about how to do that?

thadk commented 7 years ago

Only just now seeing this: There were errors in the startup logs that indicated values in those columns were invalid for the pre-existing users from the old database that I wanted to use until I manually inserted them. These errors prevented the login page from accessing the platform. I tried to modify them using the Rails console rather than PostgresSQL console but even with .save() it did not seem to persist. After the schema was updated with migrate, I ran a SQL UPDATE query to set those two columns for my user.