Future polish. Today, enabling push delivery on a customer's Rails server is a multi-step manual job (add action_push_native, write config/push.yml, generate a device model + migration, add a push permission prompt to a view) that the dashboard can only describe, not do. It links out to the full guide.
A generator collapses that to one command, mirroring the existing rails generate ruby_native:install:
- add
action_push_native to the Gemfile
- create
config/push.yml from a template with labeled placeholders
- generate the device model + migration
- insert the push permission prompt into a view
- print next steps tailored to the app
The one thing it can't do is fetch an APNs key from Apple, so the end state is "run one command, then paste your APNs key into the placeholders." Still a big drop from reading the whole guide.
Once it exists, the Push tab's server-setup section becomes a single copy-box command instead of a step list, which is what would make that tab genuinely actionable rather than a docs pointer.
Implementation lives in gem/lib/generators/ruby_native/.
Context: came up 2026-05-18 while building the Push notifications dashboard tab. Deferred as future polish, separate from the pingrb-android push workstream. Migrated from Solo todo #72.
Future polish. Today, enabling push delivery on a customer's Rails server is a multi-step manual job (add
action_push_native, writeconfig/push.yml, generate a device model + migration, add a push permission prompt to a view) that the dashboard can only describe, not do. It links out to the full guide.A generator collapses that to one command, mirroring the existing
rails generate ruby_native:install:action_push_nativeto the Gemfileconfig/push.ymlfrom a template with labeled placeholdersThe one thing it can't do is fetch an APNs key from Apple, so the end state is "run one command, then paste your APNs key into the placeholders." Still a big drop from reading the whole guide.
Once it exists, the Push tab's server-setup section becomes a single copy-box command instead of a step list, which is what would make that tab genuinely actionable rather than a docs pointer.
Implementation lives in
gem/lib/generators/ruby_native/.Context: came up 2026-05-18 while building the Push notifications dashboard tab. Deferred as future polish, separate from the pingrb-android push workstream. Migrated from Solo todo #72.