Install sc

sc is the deploy agent: run it in your project directory and it reads your compose file, packs every build: context into a tarball, and uploads the lot here. One static binary — no runtime, no daemon, nothing else to install.

macOS & Linux

0.1.1-snapshot-c9c5c93 · dev channel

Downloads the right build for your machine, checks it against the checksum published with it, and installs it.

curl -fsSL https://someones.computer/install.sh?channel=dev | sh

It lands in /usr/local/bin when that is yours to write to and ~/.local/bin otherwise — it will not reach for sudo on its own. Set SC_INSTALL_DIR to put it somewhere else. Read it first if you like: install.sh.

Or take the archive

stable · dev

Unpack it and put sc anywhere on your PATH. Windows is a zip and has no install script — that is all there is to do with it.

Platform Download Size SHA-256
macOS · Intel / AMD 64-bit sc_0.1.1-snapshot-c9c5c93_darwin_amd64.tar.gz 4 MiB
3444af27be5f5f81e3a8c4d233039458bab683c451f6789ec71a4df9ba2bc235
macOS · ARM 64-bit sc_0.1.1-snapshot-c9c5c93_darwin_arm64.tar.gz 4 MiB
d252e5b463bbe24918a335f2bef89e1d875ea0c6856586cbf6b3343074093f35
Linux · Intel / AMD 64-bit sc_0.1.1-snapshot-c9c5c93_linux_amd64.tar.gz 4 MiB
320d3cea13f1edd59b4587f79d50e77bd17f9f34d8a77c58ab6dca2d523a6966
Linux · ARM 64-bit sc_0.1.1-snapshot-c9c5c93_linux_arm64.tar.gz 4 MiB
880cbfcceb3666a8cef0cadb31058519cbd6b08611451633f248ec494bb82b9e
Windows · Intel / AMD 64-bit sc_0.1.1-snapshot-c9c5c93_windows_amd64.zip 4 MiB
ae2c7287bfaad915667f802942385094cf67fbd44932b0a42cc3d5978474b2a4
Windows · ARM 64-bit sc_0.1.1-snapshot-c9c5c93_windows_arm64.zip 4 MiB
c765d0f7a0b3ac3a5d73c2ec637757c6bf193467ae6190c830daae850f340ce5

Checksums are goreleaser's own, mirrored here with the archives — the install script above checks the same values before it writes anything.

Build from source

Needs a Go toolchain and nothing else. Always an option, and the only one if you want a build of main.

git clone https://git.grey.ooo/Grey.ooo/someones.computer_agent.git cd someones.computer_agent go build -o sc ./cmd/sc

Then sign in

sc login prints the page to mint an API token on, offers to open it, and reads what you paste without echoing it. Tokens are stored per endpoint, so a local stack and this one can each have their own.

sc login

After that, sc deploy beside your compose file is the whole thing. In CI, set $SC_TOKEN and pass --yes so nothing waits on a prompt.

There is a tray app too

sc-tray shares this credential store — sign in once above and it is signed in as well. It sits in the menu bar showing what is running and switching deployments on and off.

See the tray app →