aklein-1s commented on issue #34773: URL: https://github.com/apache/superset/issues/34773#issuecomment-3248418055
@dosu I follow the thread to find a solution to my problem, and I understand why the url `https://mydomain.fr/analytics/static` works with my config, because I set the environment variable BUILD_SUPERSET_FRONTEND_IN_DOCKER to false and I ran `npm i && npm run dev` like the documentation said https://superset.apache.org/docs/installation/docker-compose/#option-1---for-an-interactive-development-environment I deduced that I don't need the container superset-node from docker-compose.yml in this way, is that correct ?? So I will delete it from the compose file if it is useless. Furthermore I'm asking what is the use of containers superset-worker, superset-worker-beat and superset-tests-worker and how can I configure my nginx server to work with them with SUPERSET_APP_ROOT. For now I still have the access problem of ws : <img width="1059" height="99" alt="Image" src="https://github.com/user-attachments/assets/f06a70b3-130b-4901-a97a-f8ee2d141913"; /> So I shared my actual config of nginx : ``` upstream superset_app { server localhost:8088; keepalive 100; } upstream superset_websocket { server localhost:8080; keepalive 100; } server { listen [::]:443 ssl; listen 443 ssl; server_name mydomain.fr; include conf.d/ssl.conf; location /analytics/ws { proxy_pass http://superset_websocket; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Prefix /analytics/ws/; } location /analytics { proxy_pass http://superset_app; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Prefix /analytics/; proxy_http_version 1.1; port_in_redirect off; proxy_connect_timeout 300; } access_log /var/log/nginx/superset/access.log; error_log /var/log/nginx/superset/error.log; } ``` Do you have any idea ? @bxter I have the same problem with the logo -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
