Wisp CLI 0.4.1 (alpha)
Deploy static sites to the AT Protocol
The Wisp CLI is a command-line tool for deploying static websites directly to your AT Protocol account. Host your sites on wisp.place with full ownership and control, backed by the decentralized AT Protocol.
Features
Section titled “Features”- Deploy: Push static sites directly from your terminal
- Pull: Download sites from the PDS for development or backup
- Serve: Run a local server with real-time firehose updates
- Authenticate with app password or OAuth
- Incremental updates: Only upload changed files
Downloads
Section titled “Downloads”Download v0.4.1
macOS (Apple Silicon): wisp-cli-aarch64-darwin
Linux (ARM64): wisp-cli-aarch64-linux
Linux (x86_64): wisp-cli-x86_64-linux
Windows (x86_64): wisp-cli-x86_64-windows.exe
SHA-1 Checksums
69de880e160a2f26e3c26b7c28030457913754dc wisp-cli-aarch64-darwin
026189f2c10077a2be4705102e169e66cb207f84 wisp-cli-aarch64-linux
4777cff07558906717402484a3313359880eae96 wisp-cli-x86_64-linux
d6bc789d7fd7c787e5520eb476cee70c97ccb3ce wisp-cli-x86_64-windows.exe
CI/CD Integration
Section titled “CI/CD Integration”Deploy automatically on every push using Tangled Spindle:
when: - event: ['push'] branch: ['main'] - event: ['manual']
engine: 'nixery'
clone: skip: false depth: 1 submodules: false
dependencies: nixpkgs: - nodejs - coreutils - curl github:NixOS/nixpkgs/nixpkgs-unstable: - bun
environment: SITE_PATH: 'dist' SITE_NAME: 'my-site' WISP_HANDLE: 'your-handle.bsky.social'
steps: - name: build site command: | export PATH="$HOME/.nix-profile/bin:$PATH"
# you may need to regenerate the lockfile due to nixery being weird # rm package-lock.json bun.lock bun install
bun run build
- name: deploy to wisp command: | # Download Wisp CLI curl https://sites.wisp.place/nekomimi.pet/wisp-cli-binaries/wisp-cli-x86_64-linux -o wisp-cli chmod +x wisp-cli
# Deploy to Wisp ./wisp-cli \ "$WISP_HANDLE" \ --path "$SITE_PATH" \ --site "$SITE_NAME" \ --password "$WISP_APP_PASSWORD"Note: Set WISP_APP_PASSWORD as a secret in your Tangled Spindle repository settings. Generate an app password from your AT Protocol account settings.
Basic Usage
Section titled “Basic Usage”Deploy a Site
Section titled “Deploy a Site”# Download and make executablecurl -O https://sites.wisp.place/nekomimi.pet/wisp-cli-binaries/wisp-cli-macos-arm64chmod +x wisp-cli-macos-arm64
# Deploy your site./wisp-cli-macos-arm64 deploy your-handle.bsky.social \ --path ./dist \ --site my-siteYour site will be available at: https://sites.wisp.place/your-handle/my-site
Pull a Site from PDS
Section titled “Pull a Site from PDS”Download a site from the PDS to your local machine:
# Pull a site to a specific directorywisp-cli pull your-handle.bsky.social \ --site my-site \ --output ./my-site
# Pull to current directorywisp-cli pull your-handle.bsky.social \ --site my-siteServe a Site Locally with Real-Time Updates
Section titled “Serve a Site Locally with Real-Time Updates”Run a local server that monitors the firehose for real-time updates:
# Serve on http://localhost:8080 (default)wisp-cli serve your-handle.bsky.social \ --site my-site
# Serve on a custom portwisp-cli serve your-handle.bsky.social \ --site my-site \ --port 3000
# Enable SPA mode (serve index.html for all routes)wisp-cli serve your-handle.bsky.social \ --site my-site \ --spa
# Enable directory listing for paths without index fileswisp-cli serve your-handle.bsky.social \ --site my-site \ --directoryDownloads site, serves it, and watches firehose for live updates!
Authentication
Section titled “Authentication”OAuth (Recommended)
Section titled “OAuth (Recommended)”The CLI uses OAuth by default, opening your browser for secure authentication:
wisp-cli deploy your-handle.bsky.social --path ./dist --site my-siteThis creates a session stored locally (default: /tmp/wisp-oauth-session.json).
App Password
Section titled “App Password”For headless environments or CI/CD, use an app password:
wisp-cli deploy your-handle.bsky.social \ --path ./dist \ --site my-site \ --password YOUR_APP_PASSWORDGenerate app passwords from your AT Protocol account settings.
File Processing
Section titled “File Processing”The CLI handles all file processing automatically to ensure reliable storage and delivery. Files are compressed with gzip at level 9 for optimal size reduction, then base64 encoded to bypass PDS content sniffing restrictions. Everything is uploaded as application/octet-stream blobs while preserving the original MIME type as metadata. When serving your site, the hosting service automatically decompresses non-HTML/CSS/JS files, ensuring your content is delivered correctly to visitors.
File Filtering: The CLI automatically excludes common files like .git, node_modules, .env, and other development artifacts. Customize this with a .wispignore file.
Incremental Updates
Section titled “Incremental Updates”The CLI tracks file changes using CID-based content addressing to minimize upload times and bandwidth usage. On your first deploy, all files are uploaded to establish the initial site. For subsequent deploys, the CLI compares content-addressed CIDs to detect which files have actually changed, uploading only those that differ from the previous version. This makes fast iterations possible even for large sites, with deploys completing in seconds when only a few files have changed.
Limits
Section titled “Limits”- Max file size: 100MB per file (after compression)
- Max total size: 300MB per site
- Max files: 1000 files per site
- Site name: Must follow AT Protocol rkey format (alphanumeric, hyphens, underscores)
Command Reference
Section titled “Command Reference”Deploy Command
Section titled “Deploy Command”wisp-cli deploy [OPTIONS] <INPUT>
Arguments: <INPUT> Handle (e.g., alice.bsky.social), DID, or PDS URL
Options: -p, --path <PATH> Path to site directory [default: .] -s, --site <SITE> Site name (defaults to directory name) --store <STORE> OAuth session file path [default: /tmp/wisp-oauth-session.json] --password <PASSWORD> App password for authentication -h, --help Print helpPull Command
Section titled “Pull Command”wisp-cli pull [OPTIONS] <INPUT>
Arguments: <INPUT> Handle or DID
Options: -s, --site <SITE> Site name to download -o, --output <OUTPUT> Output directory [default: .] -h, --help Print helpServe Command
Section titled “Serve Command”wisp-cli serve [OPTIONS] <INPUT>
Arguments: <INPUT> Handle or DID
Options: -s, --site <SITE> Site name to serve -o, --output <OUTPUT> Site files directory [default: .] -p, --port <PORT> Port to serve on [default: 8080] --spa Enable SPA mode (serve index.html for all routes) --directory Enable directory listing mode for paths without index files -h, --help Print helpDevelopment
Section titled “Development”The CLI is written in Rust using the Jacquard AT Protocol library. To build from source:
git clone https://tangled.org/@nekomimi.pet/wisp.place-monorepocd clicargo build --releaseBuilt binaries are available in target/release/.
Related
Section titled “Related”- place.wisp.fs - Site manifest lexicon
- place.wisp.subfs - Subtree records for large sites
- AT Protocol - The decentralized protocol powering Wisp