// the take
Dashing-rails repackages Shopify's old Sinatra-based Dashing framework as a Rails engine, so you can drop a widget-based ops dashboard into an existing Rails app instead of running a separate service. It's for teams who already have a Rails app and want a quick internal metrics board without adopting another stack.
The data flow is simple and sound: background jobs push JSON to Redis, Redis fans it out over Server-Sent Events, and widgets just render whatever arrives — no polling, no client-side state management to fight. Decoupling via Redis also means you can feed dashboards from a completely different app or language, not just the Rails process it's installed in. The generators (dashing:install, dashing:widget, dashing:job) get you from zero to a running dashboard in a few commands.
Last pushed in January 2020 and pinned to Ruby >= 1.9.3 and Rails 4-era conventions — getting this onto a current Ruby/Rails version means patching dependencies yourself, not a quick bump. The entire frontend is built on dead tech: batman.js, CoffeeScript, Gridster, jQuery — none of it will see further updates and some of it won't install cleanly on modern Node toolchains. It has a hard requirement on a multi-threaded server with allow_concurrency enabled because it holds SSE connections open, doesn't work in IE at all, and has no documented approach to running behind multiple app instances beyond "point them at the same Redis." The widget-push API is also guarded by a single shared auth_token with no per-widget or per-user scoping.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →