Start overriding the config
Before launching the cares: customize your configs.
In this page, we will detail the steps to override the configs in Cares-on-platform. As an example, we're going to override Superset configuration that was initialized in Platform:
Create a folder of the target package in Cares-on-platform
Our package that we need to override its config called in the Platform: dashboard-visualiser-superset, it is a good practice to create a folder with the same name under importer
folder.
Now we have: importer
-> dashboard-visualiser-superset
Configuration files
If you check the platform, you will find a folder called importer
inside dashboard-visualiser-superset
package, what inside that folder are the files that you need to configure Superset.
We have:
A JS script that will send the request to import the assets.
A ZIP file that contains the extracted assets
Each package will have its own files and its own logic to initialize and configure it.
You will need the JS script to use it as it is (it is possible that you will need to create your own script in other cases)
You should have exported a new ZIP file from Superset that contains the new configs (check the docs of Superset).
You can put these two files under importer
-> dashboard-visualiser-superset.
Docker compose config update
If you check importer
-> docker-compose.config.yml
you will find already some services declared with their configs declaration. You will need to add the Superset config-importer service and their new configs.
Make sure in this step that you use a light image (example: node image) and to give the configs a label: cares
.
Update Swarm.sh bash script
Last, don't forget to update the swarm.sh to remove the config importers.
Example:
Last updated