When I refer the helm charts in superset code base or the docker compose we see below service
redis - caching / celery process
db - persistent state management for superset
superset-init - Runs migrations, sets up example tables, charts, dashboards etc
worker
worker-beat
I don't see any separate service for node.
I made changes in superset front end code to change font, primary, secondary colors. Rebuilt the docker image from source for Superset and deployed the template with updated docker image for superset. superset-node is using a separate docker public.ecr.aws/p9r6s5p7/superset-node:v1.4.1 which I have not replaced. I see the updated css, font family when I open superset frontend, but no logs or activity on superset-node
When I refer the helm charts in superset code base or the docker compose we see below service
I don't see any separate service for node.
I made changes in superset front end code to change font, primary, secondary colors. Rebuilt the docker image from source for Superset and deployed the template with updated docker image for superset. superset-node is using a separate docker public.ecr.aws/p9r6s5p7/superset-node:v1.4.1 which I have not replaced. I see the updated css, font family when I open superset frontend, but no logs or activity on superset-node