Docs

Requirements

  • A Linux server with systemd (amd64 or arm64), or a Mac.
  • Docker with the Compose plugin, usable by your user (the docker group on Linux; Docker Desktop, OrbStack or Colima on macOS).
  • An authenticator app on your phone for the login codes.

Install

One line installs the latest release, shows a QR code to scan with your authenticator app, and starts yasssm as a service on 127.0.0.1:8090. Run it again to update.

Linux

curl -fsSL https://yasssm.luizlab.com.br/install.sh | sh

A systemd user service; lingering is turned on so it keeps running after you log out and starts at boot.

macOS

curl -fsSL https://yasssm.luizlab.com.br/install-macos.sh | sh

A launchd agent that starts when you log in. On a Mac used as a server, turn on automatic login so it starts after a reboot. Logs go to ~/Library/Logs/yasssm.log.

yasssm totp-qr shows the QR code again (for a second phone); yasssm totp-init -force makes a new secret.

From source

Needs Go; make downloads the Tailwind CLI the first time.

# build and install the binary
make build-linux
install -m 755 bin/yasssm-linux-amd64 ~/.local/bin/yasssm

# scan the QR code with your authenticator app
yasssm totp-init

# run it as a user service that survives logout and reboots
cp deploy/yasssm.service ~/.config/systemd/user/
systemctl --user daemon-reload
systemctl --user enable --now yasssm
loginctl enable-linger

On macOS use make build-darwin and deploy/com.yasssm.plist:

# build and install the binary
make build-darwin
install -m 755 bin/yasssm-darwin-arm64 ~/.local/bin/yasssm

# scan the QR code with your authenticator app
yasssm totp-init

# run it as a launchd agent that starts when you log in
sed "s|HOME|$HOME|g" deploy/com.yasssm.plist > ~/Library/LaunchAgents/com.yasssm.plist
launchctl load ~/Library/LaunchAgents/com.yasssm.plist

Access

yasssm listens on 127.0.0.1:8090 only. Publish it on your tailnet with Tailscale, so only your devices reach it, over HTTPS:

tailscale serve --service=svc:yasssm --https=443 --bg http://127.0.0.1:8090

The server must be a tagged node, and your user its operator (sudo tailscale set --operator=$USER). Approve svc:yasssm once in the Tailscale admin console; it is then at https://yasssm.<your-tailnet>.ts.net. Add it to your phone's home screen to open it like an app.

Using it

  • Stacks: every folder under YASSSM_STACKS_DIR with a compose file is a stack. Up, restart, stop, pull and recreate it; start, restart, stop and read the logs of each container.
  • Services: systemd services on Linux (failed first); your launchd agents on macOS.
  • Cron: your crontab, the system cron files, and systemd timers on Linux, each with the code it runs. Read only.
  • Jobs: every action shows its commands on a confirmation page first, then runs in the background; its page shows the output until it ends.

Configuration

Environment variables, set in the service file:

YASSSM_ADDR
Address to listen on. Keep it on loopback. Default: 127.0.0.1:8090.
YASSSM_STACKS_DIR
Folder whose subfolders are your Compose stacks. Default: $HOME.
YASSSM_TOTP_FILE
The login secret: ~/.config on Linux, ~/Library/Application Support on macOS. Default: config dir/yasssm/totp.
YASSSM_SECURE_COOKIE
Set to 1 behind HTTPS (Tailscale serve) to mark the session cookie Secure. Default: unset.

macOS notes

  • Services lists your own launchd agents; Apple's jobs and running apps are hidden. System daemons need root, so they are not shown.
  • There are no systemd timers; Cron shows your crontab and /etc/periodic.
  • Disk is the data volume (/System/Volumes/Data), the one that fills up.

Security

  • Docker access is as good as root: never expose yasssm to the internet, not even with Tailscale Funnel.
  • Login is a 6-digit TOTP code. Reused codes are rejected, and 5 wrong codes lock the login for 5 minutes.
  • The pages run no JavaScript; the content security policy blocks scripts. Forms are protected against cross-site requests.