The Weesify CLI is one small file that runs with Node.js 18 or newer. There is nothing else to install. It does everything through your workspace's API, so it can only do what your token and your role allow.
Install it
On macOS or Linux, open Terminal and run:
curl -fsSLo weesify.mjs https://weesify.com/developers/cli/weesify.mjs && node weesify.mjs login
On Windows, in PowerShell:
Invoke-WebRequest https://weesify.com/developers/cli/weesify.mjs -OutFile weesify.mjs; node weesify.mjs login
The CLI page shows the file's SHA-256 fingerprint so you can check the download is genuine.
Sign in
- In Weesify, open Settings › Developers and create a token with Read pages and websites, Manage websites and Deploy websites.
- Run
node weesify.mjs loginand paste the token. It is saved on your computer only, readable only by you, and never in your website folder.
Deploy a folder
- Go to your website's folder and run
node weesify.mjs init. Pick an existing website or create a new one. - Run
node weesify.mjs deploy -m "New menu". Your files are packed, uploaded and published, and the address is shown.
Your website becomes exactly what is in the folder: files you deleted locally are removed from the website too. Folders such as node_modules and .git, settings files such as .env, and log files are left out. To leave out more, list them in a file called .weesifyignore in the same folder.
Want to check first? deploy --draft only updates the draft. Open the editor to look it over, then publish from there.
Other things it can do
| Command | What it does |
|---|---|
status |
What is live, what changed in the draft, and how your folder differs from the live website |
pull |
Download the draft (or the live website with --live) into a folder |
deployments |
Every deployment, newest first |
rollback |
Put the previous deployment back live (or one you name) |
domains |
List, add and verify custom domains |
open |
Open the website in your browser |
In a build pipeline
Save the token as a secret called WEESIFY_TOKEN and run node weesify.mjs deploy dist --site your-website. A deploy that needs client approval stops with exit code 2, and a failed deploy with exit code 3; the website you had stays live.