Projects

+ New page

Meeting — 2026-11-01

Participants: sato + NEO. Long working day; HUTFX dev platform stood up end-to-end.

What was asked

• Create isolated dev environments on hut for sato, petya, testhut with short subdomains, spawnable on demand, Samba-visible homes, per-user docs (ACCESS.md), emails + dev_hutfx group.
• Send plans and workflow docs to the team; save them as project documentation.
• Make docs visible to sato and petya over Samba; later: a doc.hutfx.com subdomain listing the project.
• Organize documentation wiki-style with a first page explaining each directory.

What was done

• Repo: hutfx.com repo switched to github.com/hutfx/lab-engine; hut_thereal = archive only, never touched. Production checkout on main (up to date).
• Dev environments — all three LIVE: http://sato.hutfx.com, http://petya.hutfx.com, http://testhut.hutfx.com (HTTP 200). Each: Linux user, clone at /home/<u>/dev/hutfx/, own PostgreSQL DB, php-fpm pool, nginx vhost, DNS CNAME @, Samba share \\192.168.0.3\<u>, ACCESS.md in home. Engine: /home/sato/bin/dev-spawn + update.sh (spawn is one command now).
• Mail: testhut@hutfx.com mailbox created; mlmmj list dev_hutfx@hutfx.com (sato, petya, testhut) verified expanding; ACCESS.md + plan + workflow docs emailed to the team, incl. from neo@hutfx.com. Thunderbird IMAP/CalDAV/CardDAV settings added to every ACCESS.md.
• Samba: bare-name shares; cross-access enabled (sato→petya/testhut, petya→testhut); HUTFX-project symlinked into both homes (needed wide links = yes, unix extensions = no, full smbd restart).
• Hosts: 192.168.0.6 renamed to petyapc everywhere (hosts files, ssh config); bare petya reserved for the dev DNS name.
• Docs: all project docs moved out of the website repo into ~/workspace/HUTFX-project/DOCS/; restructured wiki-style (web/, technical/, development/, projects/, security/, meetings/) with home page explaining every directory; rendered at http://doc.hutfx.com/ (DNS + vhost + build-wiki builder). Workflow doc written (PR #3 pending).
• Tooling: composer + node 22 installed system-wide on hut (needed by dev-spawn builds).

Decisions (owner)

• Branch model: main=prod, active_work=integration; one task = one new branch from current active_work = one PR — never append to an open branch. PRs→active_work, merge only by hutfx/petya5q.
• Test envs are spawned on request, branch chosen by the requester — no auto-reset.
• petya's own GitHub key deferred (uses hermes key meanwhile).
• Docs live only in the wiki; nothing new into the website repo.
• Samba shares = bare usernames. Never reset existing mailboxes' passwords.

Open items

• PR #3 (workflow doc into repo) — obsolete after docs left the repo; close or merge: owner's call.
• dev-drop <name> (teardown) not implemented yet.
• Windows Explorer access to \\192.168.0.3\petya — reported failing, likely stale saved credentials; not re-tested after today's Samba changes.
• Public SMTP ports 465/587 not forwarded on the router (only :25) — relevant for mail clients outside the LAN.
• XMPP chat: not installed; optional ejabberd later.

Later — editable docs + search (decision pending)

• Request: docs must be editable in the browser + searchable.
• Built option 1 (live): doc.hutfx.com gained web editor (/edit.php — edit + new page, login via existing sato/petya .htpasswd accounts, timestamped backup per save, auto-republish) and client-side search (search box in every page's sidebar, /search.html?q=...). Files stay plain .md.
• Deployed option 2 (live test): DokuWiki 2025 stable at http://doku.hutfx.com/ (flat-file PHP wiki, built-in editor/search/history; no DB). Currently open/no login — test instance only.
• Key trade-off: DokuWiki stores its own syntax (.txt), not markdown — adopting it means converting all docs and losing plain-md source for tools/Samba.
• Decision: user tries both, then picks one front-end.

Decision — editable docs: keep md wiki + web editor (option 1)

• Owner chose the light path over full wiki engines (DokuWiki tested at doku.hutfx.com; Gollum trialed but not deployed).
• Live now: doc.hutfx.com web editor (edit/new via /edit.php, login = existing sato/petya web accounts) + full-text search (sidebar box on every page).
• Every save: timestamped backup in tools/.backups + git commit into DOCS repo (history/diffs) + instant republish. Verified end-to-end (create → commit 2134294 → live page → cleanup).
• DOCS/ is now a git repository (main, author sato20011 noreply). NEO commits doc changes after each session.
• Test instances doku.hutfx.com (+gollum build) to be removed on owner word.

Fix — doc/doku landed on books login page

• Cause: new subdomains had no 443 listener; browsers using https fell to the default 443 vhost (books.hutfx.com) → login redirect.
• Fix: extended shared LE cert (cert-name hutfx.com, webroot /var/www/letsencrypt) to doc+doku, added listen 443 ssl http2 to both vhosts. Pitfall: nginx 1.24 rejects http2 on; — use http2 on the listen line.
• Verified: https doc/doku/search 200, /edit.php 401 without creds, http unchanged.

Multi-project docs restructure + diagrams restored + cleanup

• Owner: "too many home i am lost", "all now is related to hutfx project i want to can start a new project" (name: gio), "do it".
• New layout: single wiki root ~/workspace/DOCS/ with per-project trees. doc.hutfx.com/ = projects page → /hutfx/ (all existing docs, git repo moved intact) and /gio/ (starter, own git repo). One entry point only.
• Mermaid diagrams restored: build-wiki now renders ```mermaid via local mermaid.min.js (9 diagrams across 4 docs verified).
• Editor/Search updated for multi-project root; git commits now target the per-project repo. Search covers all projects with project tags.
• Samba: homes now expose DOCS symlink → ~/workspace/DOCS (old HUTFX-project symlinks removed).
• Removed: DokuWiki test (files, vhost, pool, DNS), Gollum (gem, DNS). doku.hutfx.com/gollum.hutfx.com no longer resolve. Zone serial 2026110103.

petya laptop → hut SSH + ACP access

• Laptop 5q (192.168.0.117, user petya): generated ~/.ssh/id_ed25519 (was missing — VS Code asked for password).
• Public key registered on hut for petya (dev env) and sato (ACP/agent access).
• Her ssh config: Host hut (petya) and Host hut-sato (sato, runs hermes-acp-* launchers). Both verified key-auth OK.
• Agents in VS Code = Remote-SSH to hut-sato + ACP Client extension; petya account has no hermes.
• petyapc (192.168.0.6) got the same petya access: generated petya@petyapc ed25519, registered on hut (petya+sato), ssh config hut/hut-sato, host key added, both logins verified key-auth. ACP from petyapc works via hut-sato + hermes-acp launchers.