What's deferred and why. wpfy is beta software — some features are intentionally out of v1 and tracked here so the community knows what's coming and can weigh in. Post feature requests in this category. Search first to avoid duplicates; upvote existing requests instead of reposting. Currently deferred (tracked in the project's open questions) These are documented in the repo's memory and decision log. They are not bugs — they are explicit deferrals pending validation or an architecture decision. Disposable-VPS validation The validation harness exists (scripts/vps-release-validation*.sh) but the final disposable-VPS release run is pending. Until it completes, treat wpfy as beta for production. Traefik Docker socket risk reduction Traefik reads the Docker socket for container discovery. A socket-proxy adoption decision is open. See Security. Supply-chain verification depth How deeply upstream WordPress / WP-CLI artifacts are verified before provisioning is an open question. Currently pull-only. Non-root / read-only filesystem compatibility PHP-FPM images currently run as root (USER www-data deferred — needs a volume-ownership strategy). Explicit non-root and read-only-filesystem compatibility is pending. External scanner runs testssl.sh and nuclei have not been run against a live wpfy host. Hardening probes (Nginx, security headers, ACME, reboot persistence) passed on the last validation VPS. How to request a feature Search this category first. If no match, start a new topic with: The problem you're trying to solve (not just the solution) The wpfy command or workflow you wish existed Whether you'd be willing to test a PR Upvote requests you want with a reply or reaction. What belongs here vs. elsewhere Bug (something broken) → Operations & Troubleshooting, with wpfy debug output. How do I… → the relevant category (Site Management, Stack, etc.). I wish wpfy could… → here. The maintainer triages requests against the roadmap and the decision log. Not every request becomes v1.