Fluksio/app
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename the workspace layout: fluksio -> app, website -> index

Browse Source 
The repo moves to git.stroblme.de:Fluksio/app.git and its sibling to
Fluksio/index.git, so every cross-repo path reference moves with it. The
architecture sources the roadmap cites now live in the docs repo under
architecture/, and the brand marks in the index repo's src/assets.

Also replaces the placeholder README with one that reflects the actual layout.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Melvin Strobl
2026-08-09 16:16:08 +02:00
co-authored by Claude Opus 5
parent 0c3e6081f2
commit 4aa2705d34
8 changed files with 60 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ROADMAP.md
+7 -7
View File
@@ -1,8 +1,8 @@
# Roadmap
Implementation strategy and record of existing/planned features. Completed items are
terse checklists — the requirement detail lives in `org/README.md` (software requirements,
evaluated tooling, hardware) and `org/structure.canvas` (the four-way component split).
terse checklists — the requirement detail lives in `docs/architecture/overview.md` (software requirements,
evaluated tooling, hardware) and `docs/architecture/structure.canvas` (the four-way component split).
Remaining tasks keep enough scope to be actionable.
Legend: `[x]` done · `[ ]` planned · sub-lists split done vs. remaining for partial items.
@@ -12,7 +12,7 @@ existing flow engine reachable and persistent precedes new feature breadth.
## Phase 0 — Workspace and platform
- [x] Root orchestrator repo with `fluksio`, `website`, `docs`, `org` as submodules
- [x] Root orchestrator repo with `app`, `index` and `docs` as submodules
- [x] `make init` bootstrap: secrets generation, per-stack `.env` propagation, shared
`proxy` docker network
- [x] Layered compose (`compose.yml` → `compose.dev.yml` → `compose.local.yml`) for both
@@ -24,7 +24,7 @@ existing flow engine reachable and persistent precedes new feature breadth.
## Phase 1 — Backend: management
Python, optimised for development speed. Owns the graph structure, persistence and the
external interfaces. See `org/structure.canvas` → *Backend – Management*.
external interfaces. See `docs/architecture/structure.canvas` → *Backend – Management*.
- [x] FastAPI + SQLModel + Alembic + Postgres base with JWT auth and user management
- [x] Flow engine prototype in `backend/app/flow/`: `Node` / `Pipeline` / `StateBackend`
@@ -51,7 +51,7 @@ external interfaces. See `org/structure.canvas` → *Backend – Management*.
## Phase 2 — Backend: processing
Rust, optimised for throughput. Executes nodes and distributes them across workers. See
`org/structure.canvas` → *Backend – Processing*.
`docs/architecture/structure.canvas` → *Backend – Processing*.
- [ ] Extract node execution from the Python prototype into a Rust engine
- [ ] Worker distribution and load balancing across capable devices
@@ -60,7 +60,7 @@ Rust, optimised for throughput. Executes nodes and distributes them across worke
## Phase 3 — Frontend: admin view
React + Vite, primarily desktop but usable on mobile. See `org/structure.canvas` →
React + Vite, primarily desktop but usable on mobile. See `docs/architecture/structure.canvas` →
*Frontend – Admin View*.
- [x] Dashboard SPA shell: TanStack Router, floating frosted sidebar, auth flows,
@@ -75,7 +75,7 @@ React + Vite, primarily desktop but usable on mobile. See `org/structure.canvas`
## Phase 4 — Frontend: dashboard view
Shares components with the admin view. See `org/structure.canvas` →
Shares components with the admin view. See `docs/architecture/structure.canvas` →
*Frontend – Dashboard View*.
- [ ] User-defined dashboard layout with edit and view modes