wpa 0.4.0

WordPress Automation — publish markdown files as WordPress pages via the REST API

WPA — WordPress Automation

Minimal CLI tool to publish markdown files as WordPress pages via the REST API.

Install

pip install wpa

Or install from source:

git clone https://github.com/cadentdev/wpa.git
cd wpa
pip install -e .

Create a site config

wpa site add

This prompts for your WordPress URL, username, application password (hidden), and optional admin path. Configs are stored at ~/.config/wpa/<site-name>/.env with 600 permissions.

WordPress Application Password

1. Log into wp-admin → Users → Your Profile
2. Scroll to "Application Passwords"
3. Enter name: "WPA CLI", click "Add New Application Password"
4. Copy the generated password (use it during --new-site setup)

Usage

# Publish a page (auto-selects site if only one config exists)
wpa publish pages/your-page.md

# Specify which site to use
wpa publish --site mysite pages/your-page.md

# Create or manage site configs
wpa site add
wpa site list

# Show version
wpa --version

Multi-site behavior

Configs	--site flag	Behavior
0	No	Prompts to create a new config
1	No	Uses the single config automatically
2+	No	Prompts to select from list
Any	Yes	Uses the named config (error if not found)

Markdown file format

---
title: "Your Page Title"
slug: "your-page-slug"
status: draft
---

Page content in markdown here...

• title (required): Page title
• slug (optional): URL slug
• status (optional): draft (default), publish, pending, or private

Site config format

Each site config is stored at ~/.config/wpa/<name>/.env:

WP_SITE_URL=https://example.com
WP_USER=your-username
WP_APP_PASSWORD=xxxx xxxx xxxx xxxx
WP_ADMIN_PATH=wp-admin

• WP_ADMIN_PATH is optional (defaults to wp-admin). Override it if your site uses a custom admin URL.
• The XDG_CONFIG_HOME environment variable is respected if set.

Migration from repo-root .env

If you have an existing .env in the repo root and no XDG configs, the tool will offer to migrate it on first run.

Safety and Security

• Default status is always draft — never publishes unless frontmatter explicitly says otherwise
• HTTPS enforced for public addresses — rejects http:// for public URLs; allows HTTP for private/LAN addresses (RFC 1918 + localhost) with a warning
• Credentials in XDG config — stored outside the repo at ~/.config/wpa/ with 600 permissions
• Password input hidden — uses getpass during interactive setup
• Status validation — rejects typos and invalid values in frontmatter
• Site name validation — only alphanumeric characters and hyphens allowed
• Connection error handling — timeouts and network failures produce clear messages, not tracebacks

Development

pip install -e '.[dev]'
pytest --cov=wpa --cov-report=term-missing

Links

• Release Notes
• Contributing