You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "SrijaniDasgupta (via GitHub)" <gi...@apache.org> on 2025/08/18 07:26:02 UTC
[D] apache superset production deployment [superset]
GitHub user SrijaniDasgupta created a discussion: apache superset production deployment
i have made changes to the source code of apache superset in windows development (changed the pivot table plugin in superset-frontend), how to reflect those changes in linux production where i downloaded superset in a virtual environment using pip
GitHub link: https://github.com/apache/superset/discussions/34729
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] apache superset production deployment [superset]
Posted by "SrijaniDasgupta (via GitHub)" <gi...@apache.org>.
GitHub user SrijaniDasgupta added a comment to the discussion: apache superset production deployment
there is no individual build folder , there are build folders for each plugins? what should i do?
GitHub link: https://github.com/apache/superset/discussions/34729#discussioncomment-14137592
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] apache superset production deployment [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: apache superset production deployment
<!-- Answer -->
You don't need to deploy the individual plugin build folders. Superset's frontend build process bundles all plugin and core assets into a single output directory: `superset/static/assets` (relative to the root of the repo). After running `npm install` and `npm run build` in `superset-frontend`, copy the contents of `superset/static/assets` from your development environment to the same location in your production environment, overwriting the existing files. This will include your plugin changes in production. The plugin-level build folders are only for development or testing—they are not used for production deployment. If your changes don't show up, try clearing your browser cache or double-checking for build errors or version mismatches.
[Reference: webpack.config.js](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/webpack.config.js)
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=7dadfd5f-1517-4fa8-9d3b-5234a9c83a78) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34729#discussioncomment-14137614
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] apache superset production deployment [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: apache superset production deployment
<!-- Answer -->
You don't need to deploy the individual plugin build folders. Superset's frontend build process bundles all plugin and core assets into a single output directory: `superset/static/assets` (relative to the root of the repo). After running `npm install` and `npm run build` in `superset-frontend`, copy the contents of `superset/static/assets` from your development environment to the same location in your production environment, overwriting the existing files. This will include your plugin changes in production. The plugin-level build folders are only for development or testing—they are not used for production deployment. If your changes don't show up, try clearing your browser cache or double-checking for build errors or version mismatches.
[Reference: webpack.config.js](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/webpack.config.js)
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/7dadfd5f-1517-4fa8-9d3b-5234a9c83a78?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7dadfd5f-1517-4fa8-9d3b-5234a9c83a78?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7dadfd5f-1517-4fa8-9d3b-5234a9c83a78?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7dadfd5f-1517-4fa8-9d3b-5234a9c83a78?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7dadfd5f-1517-4fa8-9d3b-5234a9c83a78?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7dadfd5f-1517-4fa8-9d3b-5234a9c83a78?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7dadfd5f-1517-4fa8-9d3b-5234a9c83a78?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34729)
GitHub link: https://github.com/apache/superset/discussions/34729#discussioncomment-14137614
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] apache superset production deployment [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: apache superset production deployment
<!-- Greeting -->
Hi @SrijaniDasgupta! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
To deploy your custom frontend changes (like the pivot table plugin) to your Linux production environment where Superset was installed via pip, you need to manually build the frontend assets and replace the static files used by Superset.
Here’s how you can do it:
1. On your development machine, in the `superset-frontend` directory, run `npm install` and then `npm run build` to generate the production-ready frontend assets.
2. Copy the contents of the build output (typically the `superset-frontend/build` directory) to the `superset/static/assets` directory in your Linux virtual environment, overwriting the existing files. This ensures your changes are reflected in production, since pip installs prebuilt static assets that won’t include your modifications unless you replace them yourself.
This process is necessary because pip-based installations do not automatically rebuild frontend assets from source; they use the prebuilt files included in the package. Manual replacement is the recommended approach for custom frontend deployments outside Docker environments, as confirmed by the Superset build process and Makefile [reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/Makefile).
**Caveats:**
- Your changes may be overwritten if you upgrade Superset via pip, so you’ll need to repeat this process after upgrades.
- Make sure your build matches the Superset version running in production to avoid compatibility issues.
Let me know if you need more details on any of the steps!
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=e6e10f6c-48ce-4518-b96a-22b063c85266) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34729#discussioncomment-14137543
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] apache superset production deployment [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: apache superset production deployment
<!-- Greeting -->
Hi @SrijaniDasgupta! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
To deploy your custom frontend changes (like the pivot table plugin) to your Linux production environment where Superset was installed via pip, you need to manually build the frontend assets and replace the static files used by Superset.
Here’s how you can do it:
1. On your development machine, in the `superset-frontend` directory, run `npm install` and then `npm run build` to generate the production-ready frontend assets.
2. Copy the contents of the build output (typically the `superset-frontend/build` directory) to the `superset/static/assets` directory in your Linux virtual environment, overwriting the existing files. This ensures your changes are reflected in production, since pip installs prebuilt static assets that won’t include your modifications unless you replace them yourself.
This process is necessary because pip-based installations do not automatically rebuild frontend assets from source; they use the prebuilt files included in the package. Manual replacement is the recommended approach for custom frontend deployments outside Docker environments, as confirmed by the Superset build process and Makefile [reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/Makefile).
**Caveats:**
- Your changes may be overwritten if you upgrade Superset via pip, so you’ll need to repeat this process after upgrades.
- Make sure your build matches the Superset version running in production to avoid compatibility issues.
Let me know if you need more details on any of the steps!
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/e6e10f6c-48ce-4518-b96a-22b063c85266?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e6e10f6c-48ce-4518-b96a-22b063c85266?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e6e10f6c-48ce-4518-b96a-22b063c85266?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e6e10f6c-48ce-4518-b96a-22b063c85266?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e6e10f6c-48ce-4518-b96a-22b063c85266?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e6e10f6c-48ce-4518-b96a-22b063c85266?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e6e10f6c-48ce-4518-b96a-22b063c85266?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34729)
GitHub link: https://github.com/apache/superset/discussions/34729#discussioncomment-14137543
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] apache superset production deployment [superset]
Posted by "SrijaniDasgupta (via GitHub)" <gi...@apache.org>.
GitHub user SrijaniDasgupta edited a comment on the discussion: apache superset production deployment
there is no individual build folder , there are build folders for each plugins? what should i do? @dosu
GitHub link: https://github.com/apache/superset/discussions/34729#discussioncomment-14137592
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org