ifURI / urirun — roadmap

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

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.

• Brand: unified palette (indigo/emerald/slate) + theme-aware logo; copy buttons on code; PWA, SEO (sitemap/robots), 404, a11y, contact+privacy.
• urirun: renamed tellmesh/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).

What's next (by priority)

• P0 — finish release pipeline so downloads on ifuri.com are always fresh & trustworthy:

50-cicd (sha256 + signing + urirun release wheels), 40-urirun.

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

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

• P1 — seed the connector hub with real integrations: 30-connect-connectors.
• P2 — broaden reuse / integrations to other platforms: 60-reuse.

Files

• 10-app-desktop.md — ifURI desktop app (packaging, Tauri, updates)
• 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

Open decisions (need owner sign-off)

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

Synced from GitHub · last update 2026-06-19 21:54 UTC · source: cache. Edit on GitHub; this page refreshes once a day.