Colin, thanks for pointing out the fact that each asset, JS and CSS in particular, are being fetched individually, that wouldn't happen with the production asset pipeline running. Strange still about the way images are being handled. By restarting the server, with the asset already placed things work as expected. I just don't ever recall having to start and stop the server to add images before.
Colin, are you running beta3? I have a simple test project against beta1 that I will circle back to and see if this same behaviour is present. Thanks, Dave On Wednesday, March 9, 2016 at 6:13:47 AM UTC-8, Colin Law wrote: > > On 8 March 2016 at 23:22, Dave Bell <da...@sentimentradar.com > <javascript:>> wrote: > > I believe a similar thing is happen with my install of Rails 5. It > appears > > to me that the development environment is attempting to serve assets via > the > > pipeline. For my experiment I use an image_tag to pull down an image. > In > > the first load case the PNG requested is not present in > app/assets/images. > > For the second request I have copied the PNG into place. Below is the > > console trace: > > ... > > > > When rails starts is correctly calls out that it is running in > development > > mode. However, the way it is pulling down assets on the first request > looks > > very much like the asset pipeline is being used. And clearly, with the > > second request, when the PNG is correctly placed, suggests that the > asset > > pipeline is in use. > > > > I haven't done anything with respect to the asset configuration. > Everything > > is just as 'rails new' generated. I have noticed there is now an > > app/assets/config/manifest.js file that appears to be similar in nature > to > > app/assets/javascripts/application.js but I don't know how to use this > file. > > I think the first log you provided is exactly what one would expect in > development mode. It is requesting each of the assets separately. If > it were in production mode all the js would have been precompiled into > one file, for example. > > The second log does seem odd however. Have you tried restarting the > server? I suspect the error might go away. Perhaps it is confused by > not finding it the first time, or something along those lines. Still > a bug though, but I have been unable to replicate it. > > 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/46ee6d38-974c-4033-9061-917860c50324%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
