[stanislavb]

I'd say it's kind of possible when you use a solid framework and a homogeneous tech stack. For example, I run a few relatively big projects (millions of page-views per month), and I've achieved some solid automation through Ansible - both provisioning and deployments. The primary tech is Ruby on Rails + Postgres, and it's relatively easy to maintain current. As long as I keep all the projects up to date, things are under control. For example, bumping Ruby's version (or Rails) on one of the projects has an almost one-time cost, as long as I do that at the same time for all projects and document it.

[cpursley]

Postgres is nearly always the right choice. But I've had major breaking changes in the Ruby ecosystem really bite me in the past.

[sekl]

I’m a solo dev running a few large, profitable websites, and the one running Rails has simply not been feasible to update recently with all the breakage it brings. Especially Webpacker is a major pain and I regret going down that path. Active storage has been another (lesser) pain point.