The Weesify CLI

Install

Download the file and run it with Node.js. There is nothing else to install, and no npx or package registry involved.

macOS and Linux

curl -fsSLo weesify.mjs https://weesify.com/developers/cli/weesify.mjs && node weesify.mjs login

Windows (PowerShell)

Invoke-WebRequest https://weesify.com/developers/cli/weesify.mjs -OutFile weesify.mjs; node weesify.mjs login

To type just "weesify" anywhere, put it on your PATH (macOS and Linux):

chmod +x weesify.mjs && sudo mv weesify.mjs /usr/local/bin/weesify
weesify --version

Login asks for an API token. Make one in your workspace under Settings → Developers with the scopes sites:read, sites:write and sites:deploy. It is saved in ~/.config/weesify/credentials.json, readable only by you, never in your project folder.

Check the file

Version 1.0.0, 44 KB. Compare its SHA-256 with this one before you run it:

e98494277685934e20bdfb05c7f9fe5087db5db66d80b2365a4d3f74ed51c8af

shasum -a 256 weesify.mjs        # macOS
sha256sum weesify.mjs            # Linux
Get-FileHash weesify.mjs         # Windows

First deploy

cd my-site
weesify init            # link this folder to a website (or create one)
weesify deploy -m "First version"
weesify status          # live vs draft vs this folder

deploy zips the folder on your computer, uploads it, makes the website exactly that folder and publishes it. The previous version stays one weesify rollback away. Add --draft to update the draft only and publish later from the editor.

Left out automatically: node_modules/, .git/, .env, *.log and system files. Add your own patterns to .weesifyignore (the same syntax as .gitignore). Server code such as .php is never published.

Commands

Every command takes --json for machine-readable output, --site to pick a website and --host for a self-hosted Weesify.

CI and automation

In CI, set the token as a secret named WEESIFY_TOKEN; no login step is needed. Each deploy sends its own Idempotency-Key, so a retried upload never publishes twice.

# GitHub Actions
- run: curl -fsSLo weesify.mjs https://weesify.com/developers/cli/weesify.mjs
- run: echo "e98494277685934e20bdfb05c7f9fe5087db5db66d80b2365a4d3f74ed51c8af  weesify.mjs" | sha256sum -c -
- run: node weesify.mjs deploy dist --site ${{ vars.WEESIFY_SITE }} -m "Build ${{ github.sha }}"
  env:
    WEESIFY_TOKEN: ${{ secrets.WEESIFY_TOKEN }}

A website that needs client approval can’t be published by a token until the current draft is approved; the deploy then stops with exit code 2.

Exit codes