Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[FE] Cellxgene FE serves static assets from `/static/cellxgene/*`
See original GitHub issueGiven the brand merge, both cellxgene and DP will now live on cellxgene.cziscience.com.
To avoid static assets from DP and cellxgene being accidentally served from the same route, we need to do the following:
- Change cellxgene’s Webpack config to serve all static files (fonts, images, js, css, etc.) from
/static/*to/static/cellxgene/*
E.g.,
Current:
-
https://cellxgene.cziscience.com/static/main-90d61520926ca4c19056.js -
https://cellxgene.cziscience.com/static/assets/RobotoCondensed-Regular-db6d916952fb988edac1e531d47ff83a.ttf
New:
-
https://cellxgene.cziscience.com/static/cellxgene/main-90d61520926ca4c19056.js -
https://cellxgene.cziscience.com/static/cellxgene/assets/RobotoCondensed-Regular-db6d916952fb988edac1e531d47ff83a.ttf
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@seve I think we can still work on this one, because the solution for bug https://github.com/chanzuckerberg/cellxgene/issues/1783 would apply regardless of the static asset path we choose 😄
Thank you!
@seve ACTUALLY, plot change. With the new solution that Bruce provides, we can close #1762 now.
But #1783 will still be a blocker for https://github.com/chanzuckerberg/single-cell-infra/pull/144!