Location Intelligence & Data Visualization tool
BSD-3-CLAUSE License
Bot releases are hidden (Show)
Published by azamorano over 9 years ago
# Before get last changes from master, let's remove the
# common submodule
git submodule deinit app/assets/stylesheets/common
# Clean tmp sass folder, avoiding possible compass problems
rm -rf tmp/sass/*
git pull origin master
git submodule sync
git submodule update --init
Bugfixes:
ogr2ogr2-static-bin
packageBugfixes:
Published by luisbosque over 10 years ago
Published by xavijam over 10 years ago
Published by javierarce over 10 years ago
Published by xavijam over 10 years ago
Published by zenitraM over 10 years ago
Published by zenitraM over 10 years ago
Published by luisbosque over 10 years ago
Published by luisbosque over 10 years ago
Published by zenitraM over 10 years ago
Published by zenitraM over 10 years ago
NOTE: This version introduces another kind of privacy setting: "Link-only".
Now visualizations and tables which are public are listed by default on user pages.
Due to this, you may want to turn all your Public tables and visualizations to "Link-only" state.
To do this, just run the following SQL query on your metadata database:UPDATE visualizations SET privacy='link' WHERE privacy='public'; UPDATE user_tables SET privacy=2 WHERE privacy=1;
Published by zenitraM over 10 years ago
Published by rafacas over 10 years ago
Published by rafacas over 10 years ago
Published by zenitraM over 10 years ago
From this release, CartoDB uses UUIDs instead of IDs to reference to all objects on
the database, so that it is being able to work on distributed environments much
reliably.
Your database would need manual upgrade in order to use this CartoDB version.
We have created a script to help you migrate your database. Even this script has
been tested and used on production environments by us, we highly encourage
to make a FULL backup of your database before running it.
This backup should involve both PostgreSQL metadata and user data databases
and redis metadata database.
In order to run this migration you need to stop your application and make sure
that there is not any connection to your databases while you run the script.
After you run the migration script manually you will need to run the rails
migration task as usual.
This migration will detect that your database is already in the right state and will
continue normally (and won't work until you do so).
Notice that this migration is mandatory in order to use this CartoDB version
and any other future version. Also, versions starting with this one are
incompatible with the old database schema with integer based ids.
These are the steps you need to follow in order to run the manual script:
$ cd <application_root>
$ export RAILS_ENV=<rails_env>
$ export DBNAME=<your_postgresql_database_name>
$ export DBHOST=<your_postgresql_database_host>
$ export DBUSER=<your_postgresql_database_user>
$ export REDIS_HOST=<your_redis_host>
$ bundle exec ruby ./script/migrate_to_uuid.rb schema
$ bundle exec ruby ./script/migrate_to_uuid.rb meta
$ bundle exec ruby ./script/migrate_to_uuid.rb data
$ bundle exec ruby ./script/migrate_to_uuid.rb clean
Now, back to the features:
Published by rafacas over 10 years ago
Published by rafacas over 10 years ago
Published by rafacas over 10 years ago
Published by rafacas over 10 years ago