-
Notifications
You must be signed in to change notification settings - Fork 44
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
Is this gem still maintained / current? #90
Comments
Looks like this might be promising: Update: For anyone else finding this in the future, this tutorial seems to work: The Progressive Rails App |
@athix thanks! Did the tutorial work in production as well? I can get everything working locally using serviceworker-rails but it fails in heroku production. |
@sunwooz long story short, progressive web apps as a framework are not mature enough for production usage. Core features, like scheduled notifications are still being worked on. I ended up moving towards separating the front-end and back-end, and using Quasar as a write-once-compile-everywhere solution for the front-end. To answer my original question, yes, others and now myself have moved onto newer frameworks, and Rails is relegated to serving as a REST API back-end. |
locally its working like a charm |
I've been scouring the internet for implementations of service workers for rails, and this seems to be the only library that comes up. The latest change seems to be 16 months ago however, which makes me nervous implementing this in a new project.
Is anyone aware of the current best practices for service workers in a Ruby on Rails environment? Or have most developers moved to other frameworks, and Rails is being used only in the more traditional scenarios?
The text was updated successfully, but these errors were encountered: