Show HN: Pooshit – Sync local code to remote Docker containers

39 points by marktolson 4 hours ago

Pronounced Push-It....

I'm a lazy developer for the most part, so this is for people like me. Sometimes I just want my local code running in live remote containers quickly, without building images and syncing to cloud docker repos or setting up git workflows or any of the other draining ways to get your code running remotely.

With pooshit (and a simple config file), you can simply push your local dev files to a remote folder on a VM then automatically remove relevant running containers, then build and run an updated container with one command line call.

It works well with reverse proxies like nginx or caddy as you can specify the docker run arguments in the pooshit_config files.

https://github.com/marktolson/pooshit

WastedCucumber 3 hours ago

Dumb question, out of real curiosity - is the double fecal pun deliberate?

  • robertlagrant 2 hours ago

    I can't wait for version number 2 to drop

  • CBLT 3 hours ago

    Line 1 of the readme has a poop emoji

mhuffman 2 hours ago

Useful project. Name that no reasonable company would allow IT department to use. 10 out of 10! It worked for CockroachDB. I hope it turns into a unicorn and I'm not joking about that.

  • another-dave 2 hours ago

    I can't remember what the package was, but when I was working for "large bank", one of the npm dependencies we wanted to use had a licence file that just said 'Do whatever the fuck you want'.

    Legal came back saying that it was "highly unorthodox, but approved for use"

  • chillfox an hour ago

    I have never worked at or heard of a company caring about the names of software, at most it's been a bit of a chuckle. Best guess is being concerned about software names is a super conservative culture thing.

    • manquer an hour ago

      Perhaps not directly in a review.

      Names can be troublesome though, badly named products get caught in spam filters, or blocked in some firewall blacklist.

  • spacebanana7 2 hours ago

    I believe people chose to pay Adobe subscriptions simply to avoid explaining the acronym for the GNU Image Manipulation Program in meetings.

sippeangelo 3 hours ago

Neat project, but what does this do differently than docker compose with the --host flag? https://docs.docker.com/reference/cli/docker/#host

It uploads your whole local docker context, source code and all, builds the image on the remote server and up's the container(s) all with a single command. I use this all the time when deploying simple services to avoid all of the complexity of registries etc.

    docker -H ssh://remote compose up -d
  • zsimjee 3 hours ago

    To me, it looks like this new project is aimed more at being able to develop remotely and share your localhost:3000 env instead of getting a real production box up. Bidi sync etc... hints at that, it's like having a 2-interface dev env.

  • marktolson an hour ago

    Probably pretty similar except you get to just write "pooshit" instead.

gregjw 34 minutes ago

what a name! fun conversations ahead for people that want to utilise it at work!

bilekas an hour ago

Can't wait to try and get this greenlit at work.

  • infogulch 7 minutes ago

    My grandma laughed at this one.

  • marktolson an hour ago

    Better off trying to get it brownlit.

ElCapitanMarkla 3 hours ago

I had a similar script a few years ago when I refused to give up my aging Macbook Air and built a server to host my dev env. I had an rsync command that would sync the differences from my local machine up to the remote box. It was surprisingly quick considering the size of the projects.

_def 2 hours ago

I don't really understand the use case and wonder if containers are the right tool here at all.

  • marktolson an hour ago

    Here is my main use case. I have lightweight services that I need to update and deploy regularly (until I movee to K8s or a proper production env). Using pooshit, I can push my entire local dev folder to a remote server then destroy the old image, rebuild the new image and spin up a new container with one call. Your config file contains your remote config. You need nothing in between you and your remote server and it only relies on SSH and docker, nothing else, no middleman, repos, and no deployment containers running on your VM.

wolttam an hour ago

`docker context`?

lagniappe 3 hours ago

no middlemane i like it