puma-dev VS sassc-ruby

Puma-dev: A fast, zero-config development server for macOS and Linux - https://github.com/puma/puma-dev

Developing a rails application with subdomains is much more difficult on Linux than on MacOS. On Mac it requires nothing more than installing puma-dev and following the installation guide, which also covers linux but we don't understand why that works, or how, and so we close our minds to whats beyond that rabbit hole.

Check out puma-dev. It's intended to be a successor of sorts.

you can also use them with puma-dev

You develop using this approach by running the bundler in watch mode in a terminal with yarn build:css --watch (and your Rails server in another, if you're not using something like puma-dev). Whenever the bundler detects changes to any of the stylesheet files in your project, it'll bundle app/assets/stylesheets/application.[bundler].css into app/assets/builds/application.css. This build output takes over from the regular asset pipeline default file. So you continue to refer…

I will describe the installation for macOS, for Linux you can use https://github.com/puma/puma-dev#linux-support.

And I don't know if this is the same issue (it seems to be) but the solution suggested there that got a lot of thumbs-ups didn't work for me.

Generated make files now properly set the platform architecture when running on Linux/aarch64 and Apple's M1 family of CPUs. This allows sassc and other non-extension C-based gems to build and install properly. (sass/sassc-ruby#231, #7132, #7133)

This sprockets setup has always worked great, but lately some serious bit-rot has set in. Over the last few years, the Sass Team has deprecated both its original ruby-based version of sass, and more recently, the libsass/sassc library in favor of dart-sass. As of this writing, I could not find any sprockets compatible versions of dart-sass. Further, as time marches on, the sassc gem is beginning to accumulate some pretty nasty bugs and inefficiencies. With no fixes on the horizon, it's time to move on.