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.
Frontend is not available (behind a reverse proxy, e.g. via heroku)
See original GitHub issueOverview of the issue
The newly introduced caching configuration makes the frontend not delivered when deployed on heroku (but I guess it a more general problem).
Motivation for or Use Case
It should just work.
Reproduce the error
Generate an application (from latest master) and deploy it to heroku. You will see the failure pacman. If you disable or remove the new StaticResourcesWebConfiguration it just works fine.
The error I see in the heroku logs is a 404 when requesting the static resources.
Suggest a Fix
Not sure, disabling the StaticResourcesWebConfiguration is not good as caching will be affected.
JHipster Version(s)
Latest master
- Checking this box is mandatory (this is just to show you read everything)
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 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
Just checked it with heroku and it works fine, thanks @pascalgrimaud & @monxxi
need to investigate, as it works with default packaging in local but it’s broken behind a reverse proxy ?
cc @monxxi