## [Feedback/Docs] Plain Docker/on-premises installation is much more difficult than expected

I wanted to provide some broader feedback after completing a fresh on-premises Webstudio installation.

The goal was relatively conventional:

• Webstudio builder on a local Docker host
• builder accessible only on the LAN
• internal DNS
• internal HTTPS reverse proxy
• no requirement to expose the builder to the public Internet
• project sites eventually deployed separately

Getting from docker compose up to a usable first project required considerably more troubleshooting than expected.

During the installation I encountered, among other things:

• MinIO image registry problems
• unclear behaviour when accessing the builder through a LAN IP
• cryptic 500 Invariant failed cross-origin errors
• the undocumented practical requirement for wildcard DNS for project canvases
• wildcard TLS configuration for those canvas domains
• misleading User not found errors hiding PostgREST/database errors
• private CA trust working in the browser but not inside the builder container
• project previews failing only as 400: fetch failed until NODE_EXTRA_CA_CERTS was configured
• a Chromium-only browser requirement that becomes apparent only once the builder is finally running

None of these items individually is insurmountable, but together they make a plain Docker/on-premises installation considerably more involved than the README's basic workflow suggests.

Suggestion

It would be useful to provide a complete reference architecture for an on-premises installation, for example:

Browser
  -> internal DNS
  -> HTTPS reverse proxy
  -> Webstudio builder

*.webstudio.internal.example
  -> same reverse proxy
  -> Webstudio builder canvas previews

including:

• required DNS records
• wildcard preview domains
• TLS requirements
• private CA handling
• NODE_EXTRA_CA_CERTS
• required PostgreSQL/PostgREST initialization
• supported browsers
• which services actually need externally exposed ports
• a troubleshooting table mapping common errors to likely causes

A self-hosted visual builder is especially attractive for local/private environments. Making that path reproducible would significantly improve the first-run experience.