They're both easy-to-use platforms for container-based deployments. They might make a good default recommendation over digitalocean droplets. Can we get develop-in-prod to work on either of those? I'm skeptical but worth a shot. If not, the default recommendation could be "start with a single digitalocean droplet, and when you've outgrown that, switch to fly.io/railway".
On the other hand, maybe the ease of deploying a dockerfile on one of those platforms (vs. setting up a new droplet and running the setup script on it) will outweight the benefits of develop in prod. At a minimum we have to be able to do an nrepl connection to the prod server; I can't live without that.
They're both easy-to-use platforms for container-based deployments. They might make a good default recommendation over digitalocean droplets. Can we get develop-in-prod to work on either of those? I'm skeptical but worth a shot. If not, the default recommendation could be "start with a single digitalocean droplet, and when you've outgrown that, switch to fly.io/railway".
On the other hand, maybe the ease of deploying a dockerfile on one of those platforms (vs. setting up a new droplet and running the setup script on it) will outweight the benefits of develop in prod. At a minimum we have to be able to do an nrepl connection to the prod server; I can't live without that.