wp-deploylisted
Install: claude install-skill roama-studio/skills
# WordPress deploy: Local -> shared hosting (SSH + WP-CLI)
First real run: 2026-10-23, shared hosting ukraine.com.ua. Builds on `wp-local-install`
(WP-CLI from an agent's shell) and `wp-classic-theme` (the theme). Edits to a
client's EXISTING WordPress site happen on a Playground copy first: `wp-edits`.
## 0. What only the site owner can do (ask once, all together)
- **SSH key.** We make an ed25519 key (`~/.ssh/<site>_<host>`, never in git); the
owner adds the `.pub` in the panel (or appends it to `~/.ssh/authorized_keys`
from the panel's terminal). The private key never leaves this machine.
- **Database.** On shared hosting (ukraine.com.ua and most others) a MySQL DB +
user exist **only via the panel**. A DB password is a credential: the agent never
types it into a form. The owner creates the DB and stores its data on the
server with a prompt that never echoes the password:
```
read -p "DB_NAME: " N; read -p "DB_USER: " U; read -p "DB_HOST: " H; read -s -p "DB_PASS: " P; echo; printf "DB_NAME='%s'\nDB_USER='%s'\nDB_HOST='%s'\nDB_PASS='%s'\n" "$N" "$U" "$H" "$P" > ~/.<site>-db && chmod 600 ~/.<site>-db && unset P && echo DB-OK
```
(Alternative: the panel's one-click WordPress install creates the DB; we then
reuse its `wp-config.php` and overwrite the files.)
- **PHP version** of the site in the panel (match the plugins: CF7 6.2 needs 8.3).
- **Permission rule.** Auto mode blocks "production deploy" commands; never work
around it. The owner adds, via `