shpellcast

Live command output, shared by link

Cast your command's output somewhere else.

Pipe any long-running job to a private, live web page. Send one link to your team instead of screenshots or SSH access. Nothing to install on the machine that runs the job.

./deploy.sh 2>&1 | nc shpellcast.godtech.in 9000

https://shpellcast.godtech.in/s/Qx7_a9Lp2mTz4vWn8KeR1g

Three steps

  1. PipeSend any command's output to shpellcast over the network.
  2. ShareThe link appears at once. Anyone with it can watch, no sign-in needed.
  3. WatchOutput arrives live, with colours and quiet-gap markers. A seal closes the run.

Small incantations

Any command, with nc

make build 2>&1 | nc shpellcast.godtech.in 9000

Use nc -N (OpenBSD) or nc -q 0 (traditional) so the cast closes when the command finishes.

Streamed upload, with curl

./backup.sh 2>&1 | curl -fsSN -T - https://shpellcast.godtech.in/ingest

Works anywhere curl does. The link is printed first, then output follows.

Follow a log file

tail -f app.log | nc shpellcast.godtech.in 9000

Any program that writes to a pipe works, including progress bars.

Honest notes

What it does well

  • Output reaches viewers as it is printed.
  • Links are long, random and expire 24 hours after output stops.
  • One small binary, no database, no accounts.
  • Progress bars redraw in place; colours are kept.

What to know first

  • Anyone with a link can read it. Treat links like passwords.
  • Memory holds recent output only, unless disk saving is turned on.
  • No search, no filters, and no rewind beyond the kept history.
  • Not a logging system; use it to watch and share, not to archive.

Host your own

One command on an Ubuntu server. The installer asks a few questions and explains each one.

curl -fsSL https://raw.githubusercontent.com/shpellcast/shpellcast/v1/install.sh | sudo bash

Unattended installs take flags such as --public-url and --proxy caddy. See the README for every option.