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.57 · stable channel
Downloads the right build for your machine, checks it against the checksum published with it, and installs it.
curl -fsSL https://staging.someones.computer/install.sh | 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.57_darwin_amd64.tar.gz | 5 MiB |
8e28bd4d26ab605f0f103a43362e5c0c8e240fa55e79945de89a1771aad4b5f0
|
| macOS · ARM 64-bit | sc_0.1.57_darwin_arm64.tar.gz | 4 MiB |
465c65d1fddb004cc287b1fb4c818e7179fda736a88a98d4e92d78acca516ec5
|
| Linux · Intel / AMD 64-bit | sc_0.1.57_linux_amd64.tar.gz | 4 MiB |
5151cf856d8ea63863f6e342e2b1cbc0f3a04688c26de87c5382fc8421da9cfc
|
| Linux · ARM 64-bit | sc_0.1.57_linux_arm64.tar.gz | 4 MiB |
a87800d6b774a16ad5d564f9481811b5560b7ef688739758ad01830fddc08ba8
|
| Windows · Intel / AMD 64-bit | sc_0.1.57_windows_amd64.zip | 5 MiB |
7035c996000c70157bd035fb61d6071ec741e02acd2c54a5bea460adee44f1bc
|
| Windows · ARM 64-bit | sc_0.1.57_windows_arm64.zip | 4 MiB |
8a40f594d43672d7df464e8a4af5e2dcff84efe51d09feda9b87743658de436a
|
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 --staging
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.