[Local development]

Local development

Abstract

Local AXIS development is a multi-process topology. AXIS is a Solid app under Vite; evaluation usually hits Flask; optional cloud/storage/stream features hit the Worker.

Conceptual model

Interface surface — commands

Frontend (preferred product path)

cd frontend
bun install
bun run dev          # Vite + Solid → typically http://127.0.0.1:3000

Flask Pro API (engine backend)

From repo root:

make run             # python -m backend.app → :5002
# or hatch / documented backend entry

Set PWA endpoint to http://127.0.0.1:5002 for the server engine.

Worker

cd frontend/worker
npm install          # or bun
npm run dev          # http://127.0.0.1:8787

Point cloud storage / Worker endpoint at http://127.0.0.1:8787. For /api/run proxy, set Worker EXTERNAL_BACKEND=http://127.0.0.1:5002 (works on local wrangler; not on CF edge).

Makefile helpers

For the Solid product, prefer bun run dev / bun run build over the legacy server.ts unless you are debugging the old tree (legacy shell).

Internals — useful paths

Worked loop

1. Terminal A: make run (Flask).
2. Terminal B: cd frontend && bun run dev.
3. Open Vite URL; set engine Server-Side, endpoint http://127.0.0.1:5002.
4. Load mock-walk if venues are blocked.
5. Optional Terminal C: Worker with ALLOW_OPEN_KEYS=1 for cloud library experiments.

Load an example plugin

With Vite or static server:

http://127.0.0.1:3000/plugins/example-coingecko-source.js

Manager → Plugins → Load from URL.

Invariants & edge cases

1. CORS — Flask must allow the Vite origin; Worker pickOrigin allows :3000 and :8081.
2. Pyodide local — needs vendor wheels under public/ (copied to dist on build).
3. Two endpoints — topbar endpoint for engine vs cloud storage plugin config can differ (Flask vs Worker).
4. Legacy Makefile message still mentions SuperChart Lite and :8081 Bun server.

Failure modes

See also

• Build and serve
• Worker local
• Plugin examples