FAQ
This page explains what the LS hosting demo is showing: isolated WordPress sites, public domains, TLS, backup and restore planning, and what a client can safely customize.
What does this demo show?
The demo shows a WordPress tenant running behind Coolify and Traefik with a public HTTPS domain. The goal is to prove the hosting pattern, not to finish every piece of sample content.
How does isolated WordPress hosting work?
Each site has its own frontend and WordPress runtime, with database separation behind the scenes. Public traffic lands on the web server and is routed by hostname, so multiple client sites can share the same platform without sharing the same site content.
What is the backup and restore concept?
The intended operating model is to back up the site database and files before changes, keep rollback paths documented, and use a restore site to prove recovery without disrupting the public demo site.
Does it support public domains and TLS?
Yes. The public demo and restore domains are routed through the web node and served over HTTPS. Internal maintenance hostnames remain available inside the cluster for operations and fallback checks.
What can a client customize?
Clients can customize pages, menus, branding, forms, page layouts, images, and copy. This FAQ is intentionally WordPress content, so it can be edited in the normal page editor rather than maintained as a separate static file.
Why are some links still placeholders?
Links such as Authors, Themes, Patterns, Blog, Events, and Shop are part of the starter theme’s sample footer. They are left as placeholders for the prospect to decide whether those sections should exist.
Retro Uptime Maze
Move the blue packet to the green gateway. Collect all three amber checkpoints to light the status board.
Status: waiting for route.
Controls: arrow keys or WASD.
This is a tiny self-contained widget stored in WordPress content. It uses no external scripts, trackers, or remote assets.