🥔 🚀 Service management tooling
Find a file
2024-10-04 00:03:12 -04:00
.forgejo/workflows ci: build and save artifact 2024-06-03 00:22:23 -04:00
cli feat: start cmd for remote hosts 2024-10-04 00:03:12 -04:00
daemon feat: add request-level logging 2024-10-03 00:33:08 -04:00
podman feat: add port type support 2024-09-27 00:03:20 -04:00
service refactor: inject service client / podman in daemon 2024-10-02 23:03:57 -04:00
service_definition feat: add build command + build,images config 2024-09-26 23:29:52 -04:00
webclient feat: start cmd for remote hosts 2024-10-04 00:03:12 -04:00
.gitignore feat: init + crude start command 2024-06-02 01:11:56 -04:00
go.mod build: update go -> 1.23.1 2024-09-29 15:34:11 -04:00
go.sum feat: init + crude start command 2024-06-02 01:11:56 -04:00
install.sh build: add install script and instructions 2024-06-03 23:31:32 -04:00
main.go feat: add explicit flag / arg definitions 2024-09-28 21:49:46 -04:00
README.md build: add install script and instructions 2024-06-03 23:31:32 -04:00

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.