Agree, I used to always use Heroku or Render style platforms for my own software, but nowadays I just have a Linux server with Docker Compose and a Cron job. The cron job every minute runs docker pull (downloads latest image) and docker up -d (switches to new version only if there is a new version). And put caddy in front for the HTTPS. This has been very cheap and reliable for years now.

▲

saltmate 11 hours ago | parent | next [-]

What images are you running that you'd need the latest version up after just a minute?

	▲	burner420042 10 hours ago \| parent \| next [-]
		I'm not the OP but I'd clarify the cron check for new versions is done every minute. So when new images are pushed they're picked up quickly. OP is not saying they push new versions at such a high frequency they need checks every one minute. The choice of one minute vs 15 minute is implementation detail and when architected like this costs nothing. I hope that helps. Again this is my own take.
	▲	huijzer 5 hours ago \| parent \| prev [-]
		When I push new images via CI, I want it to go in production immediately. Like Heroku/Render/Dokku

▲

RandomBK 8 hours ago | parent | prev [-]

One annoyance (I don't know if they've since fixed it) was that Docker Hub would count pulls that don't contain an update towards the rate limit. That ultimately prompted me to switch to alternate repositories.

	▲	faangguyindia 8 hours ago \| parent [-]
		one way is to host a manifest file (can host one on r2) and update it on each deploy and when manifest changes, new container image is pulled.