Adds a Node.js section to Switching your site's backend, which previously only covered PHP/PHP-FPM and the LiteSpeed/OLS add-on tier.
What changed
Intro and Steps now mention Node18/Node20/Node22 alongside PHP and LiteSpeed in the Container Type dropdown.
New ## Node.js section: the npm start model, a caution that switching an existing PHP/WordPress site to Node does not run PHP, the shared PHP-FPM/LiteSpeed placement toggle not applying to Node, the auto-raised 512 MB memory floor, and the optional WebSocket / real-time support checkbox.
New screenshot (whp-sites-edit-node.png) of the Edit Site modal with Container Type = Node22, showing Memory per Container auto-bumped to 512 MB. Captured read-only via a new tools/screenshots/capture-sites-backend.ts (modeled on capture-dns.ts), redacted per house rules.
Two new Troubleshooting entries (insufficient resources for Node, 502 after switching) and a cross-link to Create a site for file layout/start-command details.
Verification
Walked the live WHP demo panel (Sites → Edit Site, and the "What are you building?" Node.js app intent picker on Create New Site) to confirm the dropdown options, the memory auto-adjust, and the WebSocket checkbox.
Cross-checked against the WHP codebase (container_types seed data, site_intent.php, sites-forms.js) for the Node18/20/22 version list and the standalone-placement/memory-floor behavior.
npm run build passes clean (42 pages, no broken links/anchors).
Adds a Node.js section to *Switching your site's backend*, which previously only covered PHP/PHP-FPM and the LiteSpeed/OLS add-on tier.
## What changed
- Intro and Steps now mention Node18/Node20/Node22 alongside PHP and LiteSpeed in the Container Type dropdown.
- New `## Node.js` section: the `npm start` model, a caution that switching an existing PHP/WordPress site to Node does not run PHP, the shared PHP-FPM/LiteSpeed placement toggle not applying to Node, the auto-raised 512 MB memory floor, and the optional WebSocket / real-time support checkbox.
- New screenshot (`whp-sites-edit-node.png`) of the Edit Site modal with Container Type = Node22, showing Memory per Container auto-bumped to 512 MB. Captured read-only via a new `tools/screenshots/capture-sites-backend.ts` (modeled on `capture-dns.ts`), redacted per house rules.
- Two new Troubleshooting entries (insufficient resources for Node, 502 after switching) and a cross-link to Create a site for file layout/start-command details.
## Verification
- Walked the live WHP demo panel (Sites → Edit Site, and the "What are you building?" Node.js app intent picker on Create New Site) to confirm the dropdown options, the memory auto-adjust, and the WebSocket checkbox.
- Cross-checked against the WHP codebase (container_types seed data, site_intent.php, sites-forms.js) for the Node18/20/22 version list and the standalone-placement/memory-floor behavior.
- `npm run build` passes clean (42 pages, no broken links/anchors).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The "Switching your site's backend" page only covered PHP/PHP-FPM and the
LiteSpeed/OLS add-on tier. Node18/Node20/Node22 are also selectable in the
same Container Type dropdown, but weren't mentioned. Adds a Node.js section
covering the npm-start model, the auto-raised 512 MB memory floor, the
WebSocket/real-time checkbox, and that Node containers skip the shared
PHP-FPM/LiteSpeed placement choice — plus a capture script and screenshot
of the Edit Site modal with Node22 selected.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
jknapp
merged commit 6700ce27b8 into main2026-09-04 16:52:46 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds a Node.js section to Switching your site's backend, which previously only covered PHP/PHP-FPM and the LiteSpeed/OLS add-on tier.
What changed
## Node.jssection: thenpm startmodel, a caution that switching an existing PHP/WordPress site to Node does not run PHP, the shared PHP-FPM/LiteSpeed placement toggle not applying to Node, the auto-raised 512 MB memory floor, and the optional WebSocket / real-time support checkbox.whp-sites-edit-node.png) of the Edit Site modal with Container Type = Node22, showing Memory per Container auto-bumped to 512 MB. Captured read-only via a newtools/screenshots/capture-sites-backend.ts(modeled oncapture-dns.ts), redacted per house rules.Verification
npm run buildpasses clean (42 pages, no broken links/anchors).🤖 Generated with Claude Code