On Wed, 6 Mar 2019 at 14:47, Walter Lee Davis <wa...@wdstudio.com> wrote: > > > > On Mar 6, 2019, at 9:27 AM, Walter Lee Davis <wa...@wdstudio.com> wrote: >> > > The asset pipeline needs a JavaScript interpreter to work correctly on the > > server. I usually install whatever version of Node.js is available in a > > package manager. Alternatively, you can use the gem `therubyracer` to do > > the same thing. If you have that dependency filled, then I'm fresh out of > > ideas.
Thanks for the suggestions Walter I have checked nodejs is installed (node -v shows 10.x) > > Make sure that this works, on the server: > > RAILS_ENV=production rake assets:precompile Yes it does work, it outputs nothing, as expected. The code has been checked out of the git repo, which doesn't include the public/assets folder and the compiled assets are there ok. I just realised that I was wrong about the css, that isn't found either. One thing that confuses me, in the nginx log I see entries like GET /assets/red_pin.png HTTP/1.1" 404 457 ... Should the url not be the full name including the digest? Even more confusingly I am informed that if I access the server from another location then the images do appear, but I wonder whether that one is seeing cached images. I haven't managed to capture the log when that site issues a full refresh yet. Colin -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLv1ysWa9qmLgbtWH3R4ExfUfP%3Dpkcnb%3D%3DiFumX1Yk-S%3Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
