From b2f808e528842ca74f132783d907f1c3ea272eaa Mon Sep 17 00:00:00 2001 From: Threepwood-7 Date: Fri, 13 Nov 2026 04:48:15 +0100 Subject: [PATCH 1/2] RUST-CI-043: align the public FAQ with ready-profile startup --- faq/index.html | 6 +++--- tools/render_pages.py | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/faq/index.html b/faq/index.html index 3b4c8d4..e4f6cf6 100644 --- a/faq/index.html +++ b/faq/index.html @@ -63,7 +63,7 @@ "name": "How do I open the browser console?", "acceptedAnswer": { "@type": "Answer", - "text": "The implicit native first launch creates a private profile and prints the API key once. Open http://127.0.0.1:4711/ and enter that key. Keep all packaged WebUI files beside the client; existing profiles keep their existing key." + "text": "Direct daemon launches keep the profile beside the executable. Installed and container launchers use the writable profile documented in their package notes. Open http://127.0.0.1:20017/ and use rest.api_key from emulebb-rust-settings.toml. Ready packages provide the shared starter change_me_123change_me_123change_me_123; replace it before remote exposure. Existing profiles retain their own key. Keep the complete packaged WebUI layout." } }, { @@ -154,8 +154,8 @@

Which package should I download?

How do I open the browser console?

-

The implicit native first launch creates a private profile and prints the API key once. Open http://127.0.0.1:4711/ and enter that key. Keep all packaged WebUI files beside the client; existing profiles keep their existing key.

-Read more: First-launch guide +

Direct daemon launches keep the profile beside the executable. Installed and container launchers use the writable profile documented in their package notes. Open http://127.0.0.1:20017/ and use rest.api_key from emulebb-rust-settings.toml. Ready packages provide the shared starter change_me_123change_me_123change_me_123; replace it before remote exposure. Existing profiles retain their own key. Keep the complete packaged WebUI layout.

+Read more: Package and startup notes

How do networking and interface settings work?

diff --git a/tools/render_pages.py b/tools/render_pages.py index 4ae80d2..b50a491 100644 --- a/tools/render_pages.py +++ b/tools/render_pages.py @@ -884,7 +884,7 @@ def prepare_english_faq(routes: dict[str, Any]) -> None: "items": [ faq_item("What is eMuleBB Rust?", "A headless IPv4 eD2K/Kad client with a packaged browser console and authenticated REST API. It manages search, transfers and monitored shared folders.", "First-launch guide", user["url"]), faq_item("Which package should I download?", "Choose the matching Windows, Linux or macOS package. Linux also has static-musl archives and container images. Android bundles are experimental developer artifacts, not an APK or a supported Android app.", "Platforms and downloads", user["downloads_url"]), - faq_item("How do I open the browser console?", "The implicit native first launch creates a private profile and prints the API key once. Open http://127.0.0.1:4711/ and enter that key. Keep all packaged WebUI files beside the client; existing profiles keep their existing key.", "First-launch guide", user["url"]), + faq_item("How do I open the browser console?", "Direct daemon launches keep the profile beside the executable. Installed and container launchers use the writable profile documented in their package notes. Open http://127.0.0.1:20017/ and use rest.api_key from emulebb-rust-settings.toml. Ready packages provide the shared starter change_me_123change_me_123change_me_123; replace it before remote exposure. Existing profiles retain their own key. Keep the complete packaged WebUI layout.", "Package and startup notes", user["downloads_url"]), faq_item("How do networking and interface settings work?", "Review server/Kad status, the chosen P2P interface and TCP/UDP reachability. REST control and P2P routing are separate; a loopback console does not imply offline networking or guarantee VPN safety.", "Network setup", user["url"]), faq_item("How do I share files?", "Add deliberately chosen folder roots, review ignore patterns, and let recursive scanning and hashing finish. Sharing is managed as monitored folder trees. Add roots gradually rather than exposing an entire home directory.", "Sharing workflow", user["url"]), faq_item("Can I automate the client?", "Yes. Authenticated /api/v1 requests use the X-API-Key header and the documented REST contract. The beta API can change; protect credentials and use the API consumer guide for requests and error handling.", "REST API guide", develop["api_url"]), From 695c4831ca763aaab40315687948bea717bd2e07 Mon Sep 17 00:00:00 2001 From: Threepwood-7 Date: Fri, 13 Nov 2026 05:03:57 +0100 Subject: [PATCH 2/2] RUST-CI-050: distinguish fast Pages checks from full staging proof --- docs/SITE-HANDBOOK.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/SITE-HANDBOOK.md b/docs/SITE-HANDBOOK.md index 3efe5d6..6aad757 100644 --- a/docs/SITE-HANDBOOK.md +++ b/docs/SITE-HANDBOOK.md @@ -268,10 +268,16 @@ python tools\render_pages.py --lastmod $lastmod --check git diff --check ``` -Run the normal push gate from the selected Build checkout through +Run the normal fast push gate from the selected Build checkout through `python -B -m emule_workspace local-check --repo ---stage push`. The manager checks renderer capabilities, performs source drift -checks without writes, and stages into a unique inherited +--stage push`. It runs applicable fast source checks, including privacy and +hygiene, against clean selected sources. A pushed checkpoint still requires +full public-presence staging proof before merge and publication. + +The parent schedules `python -B -m emule_workspace local-check +--repo --stage full` under the shared heavy-validation +lock. This checks renderer capabilities, verifies clean source identity and +generated-output drift without source writes, and stages into a unique inherited `EMULEBB_WORKSPACE_OUTPUT_ROOT/artifacts/public-presence//site` child. It validates the staged site, documentation links and stable installer checksum. Do not precreate that `site` child or use source-local `.local` output. Explicit