You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2020/03/23 13:55:06 UTC
[GitHub] [incubator-superset] durchgedreht commented on issue #9347: The front end is built locally and cannot be run after uploading to the server?
durchgedreht commented on issue #9347: The front end is built locally and cannot be run after uploading to the server?
URL: https://github.com/apache/incubator-superset/issues/9347#issuecomment-602605199
Hi,
I guess this is related to some modifications of UI files (Images, JS, etc.).
I also find it very inconvenient to modify look and feel to ones individual needs - especially addressing the OpenSource community.
As I'm using docker I ended up creating a complete dedicated dockerfile for my own customizations as the old one was kind of ... suboptimal. In the latest release I recognized a lot of work around the docker images, which is great and cleaned up a lot.
But still: Can someone elaborate which is the GOTO solution to change a UI asset in a docker production scenario?
- fork, add files, build from scratch
- use e.g. docker, add npm (to prod!?), add the files to image (hack dockerfile?), npm compile
- use e.g. docker, add npm (to prod!?), add the files using volumes
It would be great to have something like a modification folder that's picked up and merged (overwrites only the added files). This would allow in most cases to stick with release images - which you can't in the other cases (or I simply found not the right way of doing it out of the box).
Thanks!
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org