21–30 of 178 posts
Earlier quoted context omitted.
I assume that he means "rather than pushing up each individual container for a project, it could take something like a compose file over a list of underlying containers, and push them all up to the endpoint."
Yes, pushing all containers one by one would not be very convenient.
this is nice, hopefully DHH and the folks working on Kamal adopt this. the whole reason I didn't end up using kamal was the 'need' a docker registry thing. when I can easily push a dockerfile / compose to my vps build an image there and restart to deploy via a make command
I'm most familiar with on-prem deployments and quickly realised that it's much faster to build once, push to registry (eg github) and docker compose pull during deployments.
You can do these image acrobatics with the dagger shell too, but I don't have enough experience with it to give you the incantation: https://docs.dagger.io/features/shell/
Docker registries have their place but are overall over-engineered and an antithesis to the hacker mentality.
Nice. And the `pussh` command definitely deserves the distinction of one of the most elegant puns: easy to remember, self-explanatory, and just one letter away from its sister standard command.
> What's that extra 's' for?
> That's a typo
A quick and dirty version: docker -H host1 image save IMAGE | docker -H host2 image load note: this isn't efficient at all (no compression or layer caching)!
I use a variant with ssh and some compression: docker save $image | bzip2 | ssh "$host" 'bunzip2 | docker load'
Ooh this made me discover uncloud. Sounds like exactly what I was looking for. I wanted something like dokku but beefier for a sideproject server setup.