WP Transformer

Converts WordPress MySQL dumps into self-contained static HTML sites — no live WordPress installation required. Multi-tenant dashboard with human-in-the-loop pipeline.

Stack

• PHP 8.2+ — no framework, no Composer
• MySQL (ALL-INKL managed) or PostgreSQL (Strato VPS / transformer.crumbforest.io)
• Tailwind CSS v3 — pre-compiled, dark theme
• nginx + PHP-FPM (VPS) or FastCGI (ALL-INKL managed)

Architecture

SQL Dump (Upload or crawl)
    │
    ▼
WPParser          — pure-PHP tokenizer, no MySQL dependency
    │
    ▼
wpt_posts         — editable intermediate layer in DB
    │
    ▼
StaticBuilder     — index.html, per-post HTML, feed.json, .htaccess
    │
    ├── ZIP Download
    └── FTP Deploy  → Customer subdomain / server

Multi-Tenant Pipeline

Each tenant goes through four steps — with human review at each:

1. SQL Upload — WordPress UpdraftPlus / mysqldump export
2. Parse — extracts posts/pages/categories, auto-detects DB prefix
3. Build — generates static HTML with per-tenant branding
4. Deploy — ZIP download or direct FTP push

Two-Server Setup

WPTransformer uses two distinct hosting environments with different roles:

┌─────────────────────────────────────┐     ┌─────────────────────────────────┐
│  Strato Root VPS                    │     │  ALL-INKL Managed Hosting       │
│  transformer.crumbforest.io         │     │  wptransformer.org              │
│                                     │     │                                 │
│  → The app runs here                │     │  → Static output lands here     │
│    Admin dashboard                  │     │    Generated HTML sites         │
│    Pipeline engine                  │     │    Customer subdomains          │
│    PostgreSQL database              │     │    MySQL (managed)              │
│    nginx + PHP-FPM                  │     │    FastCGI (managed)            │
│    Full root access                 │     │    FTP deploy, .htaccess        │
└─────────────────────────────────────┘     └─────────────────────────────────┘

Strato VPS — App Deploy (primary)

./scripts/deploy_transformer.sh

Requires SSH access to root@87.106.12.97. Creates DB, sets up nginx vhost, syncs files.

config.local.php on server:

<?php
define('DB_TYPE',          'pgsql');
define('DB_HOST',          'localhost');
define('DB_NAME',          'wptransformer_db');
define('DB_USER',          'wptransformer');
define('DB_PASS',          'generated-by-deploy-script');
define('PASSWORD_PEPPER',  'generated-by-deploy-script');
define('MAIL_TYPE',        'file');
define('APP_ENV',          'production');

First deploy: run init_pg.sql to create schema. On updates: run migrate_103.php in browser (admin login required), then delete it.

ALL-INKL — Static Output Destination

The built static sites (ZIP or FTP deploy from StaticBuilder) land here.
wptransformer.org hosts the generated HTML — not the app itself.

FTP deploy target for finished tenant builds. No PHP pipeline runs here.

Pre-Deploy Health Check

bash wptransformer-doktor.sh [/var/www/app-dir]

Checks: system resources, PostgreSQL, nginx, PHP-FPM, SSL, app config. Run on target server before every deploy.

Security

• .htaccess blocks .sql, .sh, .md, config.local.php (ALL-INKL managed)
• nginx vhost blocks classes/, templates/, logs/, scripts/ directories
• tenants/ blocked except tenants/*/public/
• CSRF tokens on all POST forms (Csrf::verify())
• bcrypt password hashing (cost 12)
• Password reset via time-limited token (SHA-256 hashed, 1h TTL)
• Slug whitelist: [^a-z0-9\-] stripped — no path traversal
• display_errors = 0 in production

Version History

Repo

git remote: https://git.crumbforest.org/branko/wptransformeer-OZMv0.git