...
Official installation guide: https://superset.apache.org/docs/installation/docker-compose
...
Configuration
Requirements
Have the necessary datasets in a
.zip
file ready for import.Have the dashboard in a
.zip
file ready for import.User must have an admin role to import items and create new database connections.
Dataset Export
Download the Items
The Zimbabwe (ZWE) dashboard uses three different datasets to allow for various visualizations:
zwe_elearning_certificates_view_dev
zwe_elearning_enrolmentscourseunifiedview_dev
zwe_course_grades
There is also a dashboard associated with these datasets. The dashboard's export file is a .zip
with the following format:dashboard_export_[YYYYMMDD]_T[HHMMSS]
All dataset names retain their original names from the zwe_elearning_dev database.
Import the Items
It is very important to follow the correct order when importing the datasets and the dashboard.
1. Connect to the Database
Path: setting/database connection/database
Before migrating or exporting a dashboard, ensure that the database connection is properly set up.
2. Import Datasets
Path: dataset/import
Depending on the scenario, the dataset can be created via the interface or may need to be migrated to include additional elements such as metric columns. For the ZWE dashboard, the best practice is to download the dataset and upload it to the new Superset server. The order of importing the datasets is not crucial, but it is essential that the datasets required by the dashboard are available on the server.
Dashboard Import
Path: dashboard/import
Once the datasets are uploaded, you can proceed with the dashboard import. Verify that all connections are functioning correctly and ensure there are no missing connections or errors related to any metrics that the dashboard uses.
Notes
Always ensure that the imported datasets are properly linked to the dashboard.
If any metrics are missing after the import, verify the dataset configurations and the database connections.
If custom CSS is applied to the dashboard and doesn't work correctly, it could be due to changes in class names between different Superset versions affecting the visualizations.