Discussion of Progressive Web Apps (PWA) is catching fire in the JavaScript community, but amongst Rails developers... not so much.
Progressive We...
For further actions, you may consider blocking this person and/or reporting abuse
Hey Ross, awesome gem. Was trying to play around with it and currently stuck on adding an icon to
manifest.json.erb
. What's the best way of adding in thesrc
of the image? I tried using<%= asset_path %>
but it doesn't quite work, at least not in development. Currently trying to "Add to homescreen" in development via DevTools -> Application -> Manifest.Here's
manifest.json.erb
:Again, not sure what to fill in for
"src"
.Does
image_path
work? Check out how I'm using it in my sample app here.Awesome! Thanks for the quick reply. Working so far :)
Great looking gem, Ross. Good chance this makes it into the dev.to codebase π
Thanks, Ben. Let me know if you have any feedback when you get around to trying it out!
Hi Ross, very good article. I have this rails (v4.2) app with webpack working and delayed jobs running on background, and I would to know if it is possible to use this gem together with those?
tks
Hey there. If you're using Webpack instead of the typical Rails asset pipeline, you probably just want to use Webpack to transpile and bundle your Service Worker scripts. This gem is mostly useful for folks who use Sprockets to bundle assets in their Rails apps.
The use and methodology for delayed jobs in your app is completely orthogonal to your approach to front-end assets; there'd be no conflict and/or benefit for background processing in whether you use this gem or not.