I've solved that problem with docker compose. it took a while to get it right, but since then everybody can clone the repository, run one command and start developing.
but, yeah these are all valid points. As always, YMMV.
I've solved that problem with docker compose. it took a while to get it right, but since then everybody can clone the repository, run one command and start developing.
but, yeah these are all valid points. As always, YMMV.
But I consider that a workaround. When the tooling gets so complex that you need more (complex) tooling to help manage that, the problem lies deeper.
Compare it to e.g. Go or Rust. Where you (or a CI) builds something and deployment literally can be a `scp target/release/foobar foobar.com:/usr/bin && ssh foobar.com systemctl restart foobar`.
I say this as someone who has been hosting Rails apps for decades: it sucks and it is hard. I have a full-blown Rails hosting (ansible, Digital Ocean, Linode and some more) but still often grab a Heroku or do the docker-dance, because some edgecase is causing havoc.
[0]https://github.blog/2021-08-11-githubs-engineering-team-move...