Following the completion of #396 we need to create local warehouses for the fase data along with a configuration for a separate Superset instance.
The file is getting very large and hard to follow plus the profiles we currently have can trip people up if they forget to include the --profile argument. This leads to thinking that we remove the Superset services from the main docker-compose.yaml file and have a separate airflow compose file that uses docker compose include to include the base services. We would then have 2 compose files that define the facility_ops and fase Superset definitions but having a base that allows sharing some of the common services so there isn't two copies of everything for Superset.
It would mean starting Superset would require running different files, something like docker compose -f docker-compose-superset-fase.yml (off the top of my head).
This setup would more closely mirror dev/prod that has distinct instances and configuration files for different Superset instances.
Following the completion of #396 we need to create local warehouses for the
fasedata along with a configuration for a separate Superset instance.The file is getting very large and hard to follow plus the profiles we currently have can trip people up if they forget to include the
--profileargument. This leads to thinking that we remove the Superset services from the maindocker-compose.yamlfile and have a separate airflow compose file that uses docker compose include to include the base services. We would then have 2 compose files that define thefacility_opsandfaseSuperset definitions but having a base that allows sharing some of the common services so there isn't two copies of everything for Superset.It would mean starting Superset would require running different files, something like
docker compose -f docker-compose-superset-fase.yml(off the top of my head).This setup would more closely mirror dev/prod that has distinct instances and configuration files for different Superset instances.