Fluksio/app - app

358 Commits 1 Branch 6 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
stroblmeandClaude Opus 5	d4a9406c51	Fix the CI gates: Python 3.13, concurrency groups, hook violations Docs / docs (push) Successful in 49s Details Playwright Tests / test-playwright (1, 2) (push) Failing after 1m11s Details Playwright Tests / test-playwright (2, 2) (push) Failing after 23s Details pre-commit / pre-commit (push) Successful in 3m2s Details Test Backend / test-backend (push) Successful in 2m22s Details Compose Smoke Test / test-compose (push) Failing after 22s Details Playwright Tests / merge-reports (push) Canceled after 1s Details The gates have never gone green on the new runners. Three separate reasons: - backend/Dockerfile shipped Python 3.10 while the code imports typing.Self and datetime.UTC, so the container exited on import and the suite could not even load its conftest. The image moves to 3.13 and the packages declare >=3.12, which is the floor the tests actually pass on; ruff's target follows and rewrites timezone.utc and asyncio.TimeoutError accordingly. Relocking drops the 3.10 branch, which bumps FastAPI and so regenerates the SDK. - frontend/README.md had no trailing newline and two dashboard widgets used arbitrary text-[…] sizes. Both are em-relative on purpose, so they move to the inline style the neighbouring ramp already uses. - Every commit left its own run queued: without a concurrency group a runner that was offline for a while works through a backlog nobody reads. A stack that fails to come up now prints its logs before the teardown removes it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-24 14:55:59 +02:00
stroblmeandClaude Opus 5	60d7ec81c0	Rename the import package app to fluksio A wheel whose top-level module is `app` collides with anything else in a user's venv, so the package that is about to be published takes the name it is published under. Only the Python package moves; the repo, the Docker WORKDIR and the compose project keep theirs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-21 21:48:05 +02:00
Melvin StroblandClaude Opus 5	8a221bfe50	Add the Gitea Actions workflows Ports n3xd's four: pre-commit, backend tests, sharded Playwright and a compose smoke test. Everything comes from the committed .env.example, so no repository secrets are needed; Actions still has to be enabled per repository and a runner registered with the ubuntu-latest label. container_name, published ports and image tags are all daemon-global, so two shards on one runner would fight over them. compose.ci.yml resets them and tags per project. test-backend keeps the fixed names because it reaches Postgres from the runner host. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KkmeRiyeYmVZqJVwuyHq9o	2026-08-15 21:20:05 +02:00

Author

SHA1

Message

Date

stroblmeandClaude Opus 5

d4a9406c51

Fix the CI gates: Python 3.13, concurrency groups, hook violations

Docs / docs (push) Successful in 49s

Details

Playwright Tests / test-playwright (1, 2) (push) Failing after 1m11s

Details

Playwright Tests / test-playwright (2, 2) (push) Failing after 23s

Details

pre-commit / pre-commit (push) Successful in 3m2s

Details

Test Backend / test-backend (push) Successful in 2m22s

Details

Compose Smoke Test / test-compose (push) Failing after 22s

Details

Playwright Tests / merge-reports (push) Canceled after 1s

Details

The gates have never gone green on the new runners. Three separate reasons:

- backend/Dockerfile shipped Python 3.10 while the code imports typing.Self
  and datetime.UTC, so the container exited on import and the suite could not
  even load its conftest. The image moves to 3.13 and the packages declare
  >=3.12, which is the floor the tests actually pass on; ruff's target follows
  and rewrites timezone.utc and asyncio.TimeoutError accordingly. Relocking
  drops the 3.10 branch, which bumps FastAPI and so regenerates the SDK.
- frontend/README.md had no trailing newline and two dashboard widgets used
  arbitrary text-[…] sizes. Both are em-relative on purpose, so they move to
  the inline style the neighbouring ramp already uses.
- Every commit left its own run queued: without a concurrency group a runner
  that was offline for a while works through a backlog nobody reads. A stack
  that fails to come up now prints its logs before the teardown removes it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-24 14:55:59 +02:00

stroblmeandClaude Opus 5

60d7ec81c0

Rename the import package app to fluksio

A wheel whose top-level module is `app` collides with anything else in a
user's venv, so the package that is about to be published takes the name
it is published under. Only the Python package moves; the repo, the
Docker WORKDIR and the compose project keep theirs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-21 21:48:05 +02:00

Melvin StroblandClaude Opus 5

8a221bfe50

Add the Gitea Actions workflows

Ports n3xd's four: pre-commit, backend tests, sharded Playwright and a
compose smoke test. Everything comes from the committed .env.example, so
no repository secrets are needed; Actions still has to be enabled per
repository and a runner registered with the ubuntu-latest label.

container_name, published ports and image tags are all daemon-global, so
two shards on one runner would fight over them. compose.ci.yml resets
them and tags per project. test-backend keeps the fixed names because it
reaches Postgres from the runner host.

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

2026-08-15 21:20:05 +02:00