Learn how to migrate from v2 to v3
Since this is a major release, we recommend you to back up your current v2 database before migrating to v3. All the database migration scripts are automated, but it’s always better to be safe than sorry.
Connection
table is now related to Team
instead of Project
Dataset
table is now related to Team
instead of Chart
ChartDatasetConfig
to store the relationship and configuration between a Chart
and a Dataset
Team
called: teamOwner
, teamAdmin
, projectAdmin
, projectViewer
REACT_APP_API_HOST
is now VITE_APP_API_HOST
REACT_APP_CLIENT_HOST
is now VITE_APP_CLIENT_HOST
VITE_APP_CLIENT_PORT
to specify where the app runs or is served. The default value is 4018
, but you will have to change this if you run the app on a different port.admin
and editor
roles are now set as projectAdmin
. This will not allow them to create connections and datasets, so you might have to reassign the roles for your team members in the UI.Learn how to migrate from v2 to v3
Since this is a major release, we recommend you to back up your current v2 database before migrating to v3. All the database migration scripts are automated, but it’s always better to be safe than sorry.
Connection
table is now related to Team
instead of Project
Dataset
table is now related to Team
instead of Chart
ChartDatasetConfig
to store the relationship and configuration between a Chart
and a Dataset
Team
called: teamOwner
, teamAdmin
, projectAdmin
, projectViewer
REACT_APP_API_HOST
is now VITE_APP_API_HOST
REACT_APP_CLIENT_HOST
is now VITE_APP_CLIENT_HOST
VITE_APP_CLIENT_PORT
to specify where the app runs or is served. The default value is 4018
, but you will have to change this if you run the app on a different port.admin
and editor
roles are now set as projectAdmin
. This will not allow them to create connections and datasets, so you might have to reassign the roles for your team members in the UI.