stroblmeandClaude Opus 5 e0b7f31fa1 Cloud routes: use timezone.utc, not datetime.UTC ...

The app supports Python 3.10 (requires-python, and the base image is
python:3.10); datetime.UTC only exists from 3.11. Every other module already
uses timezone.utc — this was the one file out of step, and it only passed
locally because the dev venv is 3.13. The container would not import at all.

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

2026-08-19 21:54:44 +02:00

..

app

Cloud routes: use timezone.utc, not datetime.UTC

2026-08-19 21:54:44 +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

Optional remote access: dial out to a Fluksio portal

2026-08-19 16:28:38 +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