🥔 🚀 Service management tooling
Marc Cataford
98fda3b404
All checks were successful
Pull-Request / tests (pull_request) Successful in 1m9s
Pull-Request / static-analysis (pull_request) Successful in 1m38s
Pull-Request / post-run (pull_request) Successful in 30s
Push / pre-run (push) Successful in 26s
Push / tests (push) Successful in 1m4s
Push / static-analysis (push) Successful in 1m28s
Push / post-run (push) Successful in 40s
|
||
|---|---|---|
| .forgejo/workflows | ||
| cli | ||
| daemon | ||
| git | ||
| podman | ||
| service | ||
| service_definition | ||
| webclient | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| bootstrap.sh | ||
| go.mod | ||
| go.sum | ||
| install.sh | ||
| main.go | ||
| README.md | ||
spud
Service management tooling
Setup
Regardless of how you obtain your binary of choice, include it in your $PATH and you are good to go!
Building from source
spud can be built from source by checking out the commit of your choosing and go build ..
Pre-built binaries
The releases page contains pre-built binaries that can be downloaded. These are built on tag-push.
The latest version can be installed via:
curl https://forge.karnov.club/spadinastan/spud/raw/branch/main/install.sh | bash
To pull a specific version, supply a $SPUD_VERSION that corresponds to an existing release tag, and to control where
the binary is unpacked and installed, supply $SPUD_ROOT.
Development
The bootstrap.sh script should be run to prepare any pre-commit hooks and other required tooling for local development. Checks can be run manually via pipx run pre-commit run -a.