Skip to content

CLI ​

text
claude-vps <command> [options]
CommandWhereWhat it does
setupserver, as rootRuns the install steps
updateserver, as rootPulls the latest release and runs setup again with the options from the first install
syncservergit pull, then apply
autosync on|offserversystemd user timer that runs sync every 30 minutes
doctorserverChecks Claude, tmux, Docker, xrdp, Plasma, ufw, ntfy and autosync
captureyour machineCopies the files in dotfiles/manifest.txt into dotfiles/home
publishyour machinecapture, commit and push
release X.Y.Zyour machineWrites VERSION, tags vX.Y.Z and pushes. GitHub publishes the release from CHANGELOG.md
applyanywhereWrites dotfiles/home into $HOME, backing up what it replaces
versionanywherePrints the version

setup ​

bash
sudo claude-vps setup [options]
OptionDefault
-u, --user NAME$SUDO_USER, or asksWorkstation user, created if missing
--rdp-port PORT53389xrdp port
--rdp-privateoffDon't open the RDP port in ufw
--ntfy-topic NAMEasksntfy.sh topic for notifications
--timezone TZunchangede.g. Europe/Istanbul
--no-desktopoffSame as --skip desktop,rdp
--skip a,bSteps to skip
--only a,bRun only these steps
-y, --yesoffNo questions. User defaults to dev, password is generated
-n, --dry-runoffPrint commands instead of running them

Steps, in order: base user ssh firewall desktop rdp apps claude dotfiles.

Updating ​

When a new version is out, run this on each server:

bash
sudo claude-vps update

It pulls the new code, shows what changed, and runs every setup step again. Steps that are already done are skipped, and xrdp and SSH are only restarted if their config changed, so an open RDP session stays connected. The options you chose on the first install (user, RDP port, skipped steps) are kept in /etc/claude-vps.conf and reused.

claude-vps sync also tells you when a new version has arrived.

Releasing a version ​

On your own machine, add a ## X.Y.Z section to CHANGELOG.md, commit it, then:

bash
claude-vps release X.Y.Z

The release workflow checks that the tag matches VERSION and publishes a GitHub release with that changelog section as notes.

Config source machines ​

claude-vps capture marks the machine it runs on as a config source (~/.config/claude-vps/source). On such a machine apply and sync leave your files alone, because the repo copy can be older than what you are using. Use claude-vps apply --force to override.

install.sh ​

The bootstrap script reads three environment variables:

VariableDefault
CLAUDE_VPS_REPOhttps://github.com/halitsever/claude-code-vps.git
CLAUDE_VPS_DIR/opt/claude-vps
CLAUDE_VPS_BRANCHmain

Anything after bash -s -- is passed to setup.

MIT licensed. Not affiliated with Anthropic.