-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
assets:precompile fails in production due to missing manifest.yml #594
Comments
Sorry about that!
Could you share the stack trace for that? |
No need to be sorry :) Just to highlight, that only happens with the potential fix for the missing manifest I mentioned above, here's the stack trace:
|
the issue regarding the |
Is Rails.application.config.assets.precompile += ['react-server.js'] This is needed in some cases but I can't remember which :S |
It is not, let me try that. |
didn't work. what should be the path for |
shouldn't I see |
Yes, I think so, but I don't understand why it doesnt :S The last suggestion I have is to do a wholesale workaround: #443 (comment) Sadly |
Thanks for the help @rmosolgo, I'll try that next. |
I hope it worked for you after that patch! |
Help us help you! Please choose one:
react-rails
, so I've included the stack trace and the exact steps which make it crash.react-rails
with another library, but I'm having trouble. I've described my JavaScript management setup (eg, Sprockets, Webpack...), how I'm trying to use this other library, and why it's not working.rake assets:precompile:all
fails while deploying toproduction
. I suspect the problem is that I have the following configuration:Which causes the
manifest.yml
to be generated underpublic/ui
instead ofpublic/assets
, thus failing the initialization of the YamlManifestContainerOn a quick attempt to fix the issue, I tried this but then,
assets:precompile
fails cause it cannot findreact-server.js
. Any thoughts?Stacktrace:
The text was updated successfully, but these errors were encountered: