ifURI / urirun — roadmap

Cross-repo plan for the ifURI ecosystem. One file per area; check items as done.

Latest audits: 05-analysis-2026-06-20.md and 06-structure-audit-2026-06-20.md. Execution planning now lives in the root /home/tom/github/if-uri/.planfile so tasks can cover all repos together.

Where we are (done)

Sites live on Plesk with repeatable deploy (scripts/deploy-plesk.sh + make deploy):

ifuri.com, examples.ifuri.com, docs.ifuri.com, logo.ifuri.com, get.ifuri.com, connect.ifuri.com.

Marketing & content stack (new): marketing.ifuri.com (webinar scheduler),

meet.ifuri.com (Jitsi redirect + booking), live.ifuri.com (YouTube + webinar live). blog.ifuri.com (markdown → WordPress) in progress. See 70-marketing.

Brand: unified palette (indigo/emerald/slate) + theme-aware logo; copy buttons on code; PWA, SEO (sitemap/robots), 404, a11y, contact+privacy.
urirun: moved under if-uri/urirun; v1/v2 runtime; integrated into the app

(ifuri-app urirun-info|scan|call|serve, urirun-first dispatch).

App CI: ci.yml (pytest 3.10–3.13 + wheel) and build-release.yml

(PyInstaller binaries for linux/windows/macos-arm64 → GitHub Release).

Connectors: browser-control, http-check, time-tools, planfile,

domain-monitor, namecheap-dns and sqlite-context have local Makefiles, tests Docker smoke environments and urirun.bindings entry-point discovery; the next proof is a shared host-node matrix.

Planfile tooling: local sprint files validate with

planfile validate schema .planfile/sprints/current.yaml --file-type sprint, and planfile health check no longer crashes on generated issue buckets.

What's next (by priority)

P0 — make install/release/test deterministic: keep active install paths on

if-uri/urirun, prove every connector in Docker, remove compatibility modules from core after downstream migration, and keep release pins synchronized. See 05, 06, 40, 50.

P1 — simplify the runtime boundary: keep urirun core small, move

app/host/domain integrations into app packages or connector packages, and standardize @urirun.command discovery. See 30, 40, tickets IFURI-015 and IFURI-016.

P1 — make runtime failures searchable and actionable through built-in

error:// diagnostics: stable codes, categories, fix hints, registry routes and ticket creation. See 40, ticket IFURI-021.

P1 — desktop packaging decision + Tauri shell, node installer parity:

10-app-desktop, 20-get-node.

P2 — broaden reuse / integrations to other platforms: 60-reuse.
P1 — turn on the marketing funnel: publish blog (WordPress key), configure

SMTP, redeploy meet/live, dogfood connectors to monitor our own sites. See 70-marketing.

Status board

Live ticket status — planned, in-progress, verified, released — is generated from the shared execution backlog and published as 90-planfile.md. Tickets cover app, get, ifuri-com, urirun and connector work together, aligned with the work summary.

Demos and shipped features

Each entry links its repository, docs page and a demo command.

Area	Status	Repo	Docs	Demo
noVNC LAN flow (four computers)	released	examples/11-novnc_lan_flow	docs.ifuri.com/novnc-demo.html	`make test-full`
Connector install / discovery	released	if-uri/connect.ifuri.com	docs.ifuri.com/connectors.html	`urirun discover --registry-out .urirun/connectors.registry.json`
Runtime error diagnostics	verified	if-uri/urirun	docs.ifuri.com/errors.html	`urirun errors recent`
get.ifuri.com node installer	released	if-uri/get	docs.ifuri.com/host-node-lan.html	`get.ifuri.com/node.sh`
Planfile validation / health	released	semcod/planfile	90-planfile.md	`planfile validate schema .planfile/sprints/current.yaml --file-type sprint`

Files

10-app-desktop.md — ifURI desktop app (packaging, Tauri, updates)
05-analysis-2026-06-20.md — current cross-repo findings
06-structure-audit-2026-06-20.md — repository map and next refactor/test priorities
20-get-node.md — get.ifuri.com node installer
30-connect-connectors.md — connect hub + connectors
40-urirun.md — urirun packaging & releases
50-cicd.md — CI/CD for multiplatform builds + integrations
60-reuse.md — where ifURI/urirun can be re-used
70-marketing.md — marketing & content surfaces (marketing/meet/live/blog)
90-planfile.md — generated ticket status from the execution backlog

Open decisions (need owner sign-off)

Desktop shell: PyInstaller (now) vs Tauri (next) vs both. → 10
urirun distribution: GitHub Release wheels only, or also PyPI + npm. → 40
Code signing budget: Apple Developer ID ($99/yr) + Windows cert (EV/OV). → 50
Site deploy: keep manual make deploy, or GitHub Actions over SSH (secret key). → 50

Synced from GitHub · last update 2026-08-03 10:36 UTC · source: cache. Edit on GitHub; this page refreshes once a day.