If you doubt it that’s your right of course. These days you should doubt everything.
18 karma · joined April 23, 2020
If you doubt it that’s your right of course. These days you should doubt everything.
The interesting part is where it runs. Rails 8's Solid stack makes the whole app a single process with one database file, which means it fits on a Synology NAS. Docker container, Tailscale for access, HyperBackup and Btrfs snapshots for backups.
The post covers the non-obvious parts: Synology's SSH PATH problem with non-interactive sessions, Docker UID/permission gotchas, how Thruster's port mapping works in a non-root container, and running a local Docker registry so images stay on your network.
It’s just... people think those technologies are congruent but the overlaps are actually minimal.
For any rather sophisticated UI you can (and will want) to use both.
For example: repaint a data visualization. With Hotwire you can only replace it and start fresh, with SR you can just surgically morph data attributes without disconnecting your stimulus controllers
also, StimulusReflex predates Hotwire for 1 year and is already pretty hardened :-)
It's a SR clone, the maintainers are actually very active in our community :-)
Frankly, patterns around SR are just materializing but there’s for example https://github.com/joshleblanc/view_component_reflex that’s maybe comparable.
CableReady is the Swiss Army knife, there’s a whole ecosystem forming around it, e.g. https://github.com/julianrubisch/futurism, a lazy loading gem by me or https://optimism.leastbad.com/, a remote form validation gem (presumably superseded by Rails 6.1/TL6, but who knows)
You might want to follow me on twitter, I‘ll be posting my explorations there!