Is it possible to deploy the static resources of superset-frontend independently in nginx?

[ascendlin]

Is it possible to deploy the static resources of superset-frontend independently in nginx?

[dosubot[bot]]

Hey @ascendlin! I'm here to help you with any issues or questions you have. I'm a bot designed to assist with bug fixes, troubleshooting, and contributions. Let me know how I can assist you!

I found a similar unsolved discussion on separating superset-frontend and superset here ^[1].

To deploy the static resources of superset-frontend independently in Nginx, you would typically configure Nginx to serve the static files from a specific directory. This involves setting up a location block in your Nginx configuration to point to the directory where your static assets are stored. You can customize the static asset paths in Superset using the STATIC_ASSETS_PREFIX configuration option, which allows you to set a prefix for all static asset paths, useful for hosting assets on an external CDN ^[2].

Unfortunately, I couldn't find specific Nginx configuration examples in the repository, but generally, you would do something like this in your Nginx configuration:

server {
    listen 80;
    server_name your_domain.com;

    location /static/ {
        alias /path/to/your/static/assets/;
    }
}

This configuration serves static files from the /path/to/your/static/assets/ directory when requests are made to your_domain.com/static/. Adjust the paths according to your setup.

To continue talking to Dosu, mention @dosu.