4 ms·
Here's my one-weird-trick: On my VM, keep this running: while true; do ssh pipe.pico.sh sub deploy-app; docker compose pull && docker compose up -d; done
by qudat 2y ago
Here's my one-weird-trick:
On my VM, keep this running:
while true; do ssh pipe.pico.sh sub deploy-app; docker compose pull && docker compose up -d; done
On my local machine:
docker buildx build --push -t ghcr.io/abc/app .; ssh pipe.pico.sh pub deploy-app -e
https://pipe.pico.sh/ https://pipe.pico.sh/
- yjftsjthsd-h 2y agoWhy not just (from the local machine) run docker buildx build --push -t ghcr.io/abc/app . && ssh myvm 'cd /my/app/path && docker compose pull && docker compose up -d' ?
- qudat 2y agoThat's a really good point! That might work if you have a single VM but it's a little more complicated when you have an app on multiple instances. pipe is a multicast pubsub which means you can have many subscribers.
- mdaniel 2y agoHeh, another feather in the "all you need is PostgreSQL" hat: if you already use PG, then LISTEN/NOTIFY can do what that external host does as well as acting like a health check for the instance since if it can't access PG it likely is in a bad way (situationally, of course, like all solutions coming from Internet commentary)