Imagine if people just used the tools themselves instead of creating yet another layer in hopes of simplifying something that can already be done with a few lines on a bash script.
And I assume you want to be building once to test your changes anyways, so you really only need to push.
I mean, what if you needed to change the way it worked? With bash you'd have to open a text editor, change a line, and save the file! And on top of that you need to understand shell scripting!
With Go, you can set up your development environment, edit the source code, run the compiler, download the external dependencies, generate a new binary, and copy it to your server. And all this requires is learning the Go language and its development model. This is clearly more advanced, and thus better.
> "Ansible ... would be a handful of lines"
How many lines are a handful? Ansible is a few hundred thousand.
If you're enjoying `uv`, consider `mise` for small helpers like the above.
Plays well with `uv`, handles this sort of thing with tasks:
Long scripts suck in Makefile, but can call external scripts for anything big.
#!/usr/bin/env bash
export DOCKER_HOST="ssh://username@host:port"
docker compose up -d --build time="2025-03-10T08:39:06-07:00" level=debug msg="commandconn: starting ssh with [-o ConnectTimeout=30 -T -l ec2-user -- ip-10-0-2-3 docker system dial-stdio]"
If possible could you share gist of that script ?
while true; do git pull && sudo reboot; done