VNOX-Server/deploy/central/VERIFIED.md
loki5512344 c18ccadf99
chore(server): checkpoint deployed services and unfinished forums
User requested a checkpoint and stopped all agents. Deployed artifacts remain the last verified releases; unfinished settings/categories/forums are preserved as WIP. See TODO/roadmap for verification and remaining release/updater work.
2026-11-01 15:31:20 +01:00

7 KiB
Raw Permalink Blame History

Vnox Central: deployment verification

Live profile, onboarding and node administration — 2026-11-01

  • Current Hub 20261101-live-admin-91595d45652a; current gateway/voice daemon 20261101-live-capability-219376accf98; website 20261101-names-monsters-ff473f423565.
  • Signed live profile updates are negotiated with Session.live_profiles. Device and account binding are retained; channel visibility is checked at delivery.
  • Node administrator UUID is explicitly configured for account loki. Creation, rename and deletion of global channels require the verified account of the exact session. Guild permissions remain separate. Channel persistence/reload tested.
  • New accounts receive a generated слово_0000 and a one-time optional name prompt; migration 9 is independent of pending migration 6. Actual versions: 1–5, 7, 8, 9. Existing account loki has no onboarding row and keeps its chosen name.
  • Pixel-monster defaults use new immutable /v1/avatars/default-v2/ URLs. Old v1 URLs remain stable; own uploaded photographs remain authoritative. Public v2 PNG verified over HTTPS using the desktop User-Agent.
  • Final server workspace: 181 tests, Clippy and formatting passed. Website: 28 tests, typecheck/build, formatting and isolated onboarding browser QA passed.
  • Paired backup /var/backups/vnox-central/live-profile-admin-20261101T134328Z; capability-only gateway backup /var/backups/vnox-central/live-capability-20261101T135637Z. Issuer, node identity, TLS and administrator configuration preserved.

Desktop profile update — 2026-11-01

  • Hub release 20261101-desktop-profile-0bc942369c89, binary SHA256 0bc942369c8943177814c4495dfac1b6413d9b7b79a74766f724415ca3acb82a.
  • Added enrollment/device-signature authorized avatar upload/delete and display name mutation. Existing browser account avatar storage is reused.
  • 167 workspace tests, 6 desktop-auth tests, formatting and Clippy passed in the isolated profile-free release workspace. Hub migrations remain 1–5, 7, 8.
  • Both public desktop mutation endpoints return 401 without authentication. Hub readiness and active status verified; gateway stayed running unchanged.
  • Private backup /var/backups/vnox-central/desktop-avatar-20261101T130504Z; issuer/email keys preserved.

Current update — 2026-11-01

  • Hub release 20261101-media-presence-75ff65dc3e7b; SHA256 75ff65dc3e7b045b617b6214cdeb676506584d7d61a1f898f4bfa8f6e7c14dab.
  • Combined gateway/voice release 20261101-media-presence-d4d98bbc2932; SHA256 d4d98bbc2932cb7ef8692e67b11067162e42299451e25e7caed7551f38f502fb.
  • Both services active; gateway health and LNEx v4 version verified. Public Central /v1/info responds over HTTPS. Issuer and node identities preserved.
  • Email/GitHub and desktop account authentication, uploaded/generated avatars, and the public community directory are enabled. Friends, DM and marketplace remain disabled in Central. Earlier entries below describe historical releases.
  • Added signed account/profile metadata, multi-session presence lifecycle and authenticated channel image attachments. Existing desktop proofs remain valid.
  • Paired private SQLite backup: /var/backups/vnox-central/media-presence-20261101T123503Z. Hub migrations remain 1–5, 7, 8; pending profile migration 6 was not deployed.
  • Isolated release workspace: 164 tests passed, formatting and all-target Clippy passed; both binaries built with the locked musl release configuration.
  • Website remains the previously deployed account/directory release. No real account was created or mail sent during this update.

Initial deployment (historical)

  • Endpoint: https://central.loki-code.dev
  • Service: vnox-central (systemd enabled/active, dedicated user).
  • Internal listener: 127.0.0.1:37623; external access goes through Nginx443.
  • Release source: a811de590a; static Linux-musl binary SHA256 1cff8bb453eabb5320020b37401cbdbb16f051c87c288823f0be35da8de21487.
  • Certificate: central.loki-code.dev, expires2027-01-22; Certbot timer active, renewal staging simulation passed.
  • /health, /ready, /version, /v1/info: verifiedHTTPS200.
  • Persistent issuer survives service restart; issuer file0600, data dir0700, root-owned environment0600.
  • Private initial paired SQLite/issuer backup created on the VPS. No external backup destination configured.
  • SMTP TLS/auth/NOOP verified with existing provider credentials, sender Vnox noreply@loki-code.dev; no real mail sent.
  • Other existing Nginx hosts still respond; production SMTP values were never printed or committed.
  • Registered public issuer ID: 47a921b4-b12b-4bb8-864a-a1b76c13714a.

Boundaries

This deployment is a real foundation service, not complete global authentication/social functionality. Email/GitHub auth, server registry, friends, DM and marketplace are explicitly not_enabled. No public send-email endpoint exists. Email HTML previews use dummy tokens and their future verification routes are not active.

Approved logo is the V connection mark. The Hub serves SVG and PNG; mail uses a PNG with text fallback.

GitHub authorization update — 2026-10-24

  • Source: ff9c8f330e15, release ff9c8f330e15-ca84d4e4b6fa.
  • Static binary SHA256: ca84d4e4b6fa6c9aa0f6852e9f1af22465cac1f6e088a1ac93692877a3b10db3.
  • Paired private database/issuer backup created before migration; service restarted and readiness returned 200.
  • GitHub client configuration stored only in protected service environment. App metadata/client identity was verified through GitHub API; private signing key is unnecessary in the running Hub.
  • Authentication paths disable Nginx access/error logging before OAuth was enabled.
  • Public /v1/info reports GitHub enabled; /v1/auth/session reports anonymous without a cookie. Live start endpoint returns 303 to GitHub with the configured callback, state, S256 PKCE and a Secure/HttpOnly/SameSite cookie.
  • Workspace tests: 66 passed; all-target Clippy with -D warnings, formatting and dependency audit passed (zero vulnerabilities/warnings).
  • Complete provider authorization/code exchange still requires an account owner's browser consent. Automated checks verify the local callback/session flow with an injected provider, not real user consent.

Website update — 2026-10-24

  • Separate VNOX-Web source commit 622f396364bb; static release 622f396364bb-9b77c9dbd02c served through /opt/vnox-central/web/current.
  • Static files use 0644 permissions, directories 0755. Both approved SVG/PNG marks remain available for transactional email.
  • / and /account serve the website. /v1/, /health, /ready, /version remain Hub proxy routes; authentication logging suppression is preserved.
  • Nginx configuration validated before reload. Website CSP allows only self-hosted scripts/styles, the GitHub avatar origin for images, and same-origin API connections.
  • Live Chromium checked desktop landing, anonymous account/GitHub link, mobile account overflow, stylesheet MIME, JavaScript console and API/logo responses. No browser errors were observed. No real user authorization was performed.