feat: site create modal add root directory location browse option

[plusemon]

Adds folder browse options to site creation modals across Linux and Windows UI apps, aligning directory location input directly below web server selection.

[plusemon]

@wpexpertinbd kindly merge this and update, it is necessary for most of the website when serve sites from diferent dir's.

[wpexpertinbd]

Thanks for this — the folder pickers are a genuinely nice UX win, and I ran a full supply-chain pass over the diff (new network calls, downloads, eval/base64, new dependencies, process launches): completely clean. Much appreciated.

Requesting changes on three blockers, all straightforward:

1. macOS won't compile. macos/Sources/BHServe/AppState.swift (~line 618) became:

if type is "php" or "laravel" or "wordpress" {

That's the C# 9 pattern match you (correctly) wrote in windows/src/BHServe.Core/Engine.cs, pasted into the Swift file. Swift's is needs a type on the right, and there's no or operator — so swift build fails outright. Please use:

if type == "php" || type == "laravel" || type == "wordpress" {

and run cd macos && swift build before re-requesting review. No CI job builds Swift, so this would ship silently and surface at the next macOS release.

2. Linux GUI: "Add app" is dead on the Node and Python pages. In linux/app/bhserve/window.py, _app_dialog loses name = Gtk.Entry(placeholder_text="app name"), but both consumers survive — rows = [(name, "Name"), ...] and nm, fd = name.get_text().... Result is a NameError; PyGObject swallows it to stderr, so the button just silently does nothing. Please restore the entry (with hexpand=True to match the new row loop) and open both dialogs once to confirm.

3. Laravel sites 404 out of the box. site_add sets vhost_root="$root/public" but only runs mkdir -p "$root", and the branded landing index.php is written to $root — one level above the document root. Windows is the same (Engine.cs). Needs mkdir -p "$vhost_root" (plus Directory.CreateDirectory(vhostRoot)) with the index written there.

Two smaller ones:

• Please keep nginx -s reload as the primary path and use restart only as a fallback — details in my comment on #6.
• linux/app/bhserve/pages.py changes "Open config" from _open_editor(...) to _open(...), which loses the code/codium/cursor/subl/gedit chain (_open_editor already falls back to _open, so it's a strict superset). The neighbouring "Open in editor" still uses _open_editor, so the two now behave differently. Could you revert that line?

Note that #6 contains these same commits, so whichever you'd prefer to fix in, let me know — happy to re-review quickly once these land. Thanks again for continuing to contribute!

[plusemon]

All 5 review points are fixed and pushed. The branch was also merged with the latest master (was CONFLICTING, now CLEAN) — this picked up the quoted-document-root and root-validation changes too, so those coexist cleanly with the new laravel type.

• macOS compile — AppState.swift now uses type == "php" || type == "laravel" || type == "wordpress"
• Linux "Add app" — restored the missing name entry in _app_dialog
• Laravel 404 — site_add creates the document root and writes the landing index there ($root/public for Laravel); same in Engine.cs
• nginx reload — -s reload is primary, full restart only as a fallback (engine, platform-linux.sh, Nginx.cs)
• "Open config" — reverted to _open_editor

All 3 CI checks (swift build, dotnet build, python+bash) pass. Ready for re-review 🙏

[wpexpertinbd]

Re-reviewed — all 5 points verified fixed in the diff (not just taken on trust), and merging. Thank you for the fast, precise turnaround.

Verified:

• macOS — type == "php" || type == "laravel" || type == "wordpress", and the C# files correctly keep C# pattern syntax. The new CI's swift build job confirms it compiles.
• Add app — name entry restored (with hexpand=True); ruff F821 is clean.
• Laravel — mkdir -p "$vhost_root" creates public/ and the landing index lands in the document root. Live-tested: vhost points at …/lartest/public, the directory is created, and the site serves.
• nginx — -s reload is primary with restart only as the fallback, in both engines and Nginx.cs; you kept the good half (dropping the [ -t 1 ] tty gate so GUI changes actually apply). I A/B'd the reload path against master: identical behaviour, no regression.
• Open config — back to _open_editor.

Also checked: your master merge preserved all four of the new document-root guards (valid_site_root, vhost_root_check, vhost_root_read, quoted root "$root";) — laravel + quoting compose correctly, including a spaced root rendering as root "/…/My Lara App/public"; and serving. Supply-chain pass is clean: no new network, download, eval/base64, exec surface or dependencies.

Nice work — this is a genuinely useful feature set.