4 ms·
I'm 90% on Ruby on Rails dockerized. Meaning I would almost certainly choose that absent a very good reason to use some other backend stack. Rails because it's
by ufmace 4y ago
I'm 90% on Ruby on Rails dockerized. Meaning I would almost certainly choose that absent a very good reason to use some other backend stack. Rails because it's highly battle tested and flexible and good enough for almost anything. Dockerized because IME setting up and maintaining a Ruby environment with up to date version on bare metal is highly painful. Docker lets me be much more consistent with both Ruby versions and the rest of the server config.
I'm less solid on the deployment. Could go with one of the commercial docker-y hosting systems, or a commercial K8s setup, or a hand-rolled Docker host via Ansible. I've done all 3, and I'm not sold on any of them being the best for everything.
Front-end side is more flexible depending on the type of site/business. Normal ERB-style SSR is probably fine for a lot of things with a few sprinkles of basic JS. Would re-explore if I thought it needed a proper front-end app. React is neat, but darned if every single time I try to do a version bump on a small React app, I end up needing to rewrite half of it.