stroblmeandClaude Opus 5 17746e5d33 Do not publish the API schema from a production deployment ...

The schema enumerates every endpoint an installation serves, including the
paths HTTP trigger nodes mount at runtime, and api.fluksio.com was serving it
- along with /docs - to anyone who asked. It now follows ENVIRONMENT, which is
the rule the portal's backend already used. The generated client is built from
a local run, so nothing in the workflow depends on the deployed host exposing it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XtBzdDyLsmDaF1W7DLYtYM

2026-08-20 11:29:00 +02:00

..

app

Do not publish the API schema from a production deployment

2026-08-20 11:29:00 +02:00

connector-wheels

Record the connectors and what is still read-only

2026-08-16 10:00:10 +02:00

scripts

Benchmark the startup claim, and write down what a run is

2026-08-18 18:00:36 +02:00

tests

Bump dashboards: bar, icon, forecast and clock widget types

2026-08-20 08:31:36 +02:00

.dockerignore

Vendor backend and frontend into the monorepo

2026-08-09 15:14:54 +02:00

.gitignore

Vendor backend and frontend into the monorepo

2026-08-09 15:14:54 +02:00

alembic.ini

Vendor backend and frontend into the monorepo

2026-08-09 15:14:54 +02:00

Dockerfile

Record the connectors and what is still read-only

2026-08-16 10:00:10 +02:00

pyproject.toml

Remote workers: a GPU box dials in and runs the nodes bound to it

2026-08-18 17:52:42 +02:00