stroblmeandClaude Opus 5.5
48aac3855b
The backend image now builds the SPA and serves it on the API's own origin (fluksio/spa.py), so an instance is a single container with no proxy, DNS, port 80 or .env: `docker compose up -d` with the new compose.yml runs it on localhost:8080. It starts on fluksio serve (persisted secret key, first admin printed once) and brings its own Redis when REDIS_HOST is unset. Slimmer: python:3.13-slim, no dev group, uv once, fastapi without the cloud CLI. Optional features are per-feature extras (mqtt, influx, email, sentry, ml, server for all) picked with the EXTRAS build argument; numpy moved to `ml`. ffmpeg left the image for imageio-ffmpeg via the Modules screen. The operator stack runs the same image with app. and api. routed to it; the nginx frontend service, the LAN nginx proxy and DOMAIN in the backend are gone, and the MCP issuer is FRONTEND_HOST. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
46 lines
2.4 KiB
Python
46 lines
2.4 KiB
Python
"""Redirect the suite at its own database.
|
|
|
|
`fluksio.core.db` builds the engine at import time and several modules bind
|
|
that object, so the URL has to be in the environment before anything imports
|
|
the settings. Overriding it here — the first module pytest imports for the
|
|
package — keeps a test run from touching the development data.
|
|
|
|
A file rather than `:memory:`: the suite starts the engine's own threads (the
|
|
run service, the metrics collector, the portal connector) against this engine,
|
|
and an in-memory database is per connection unless every one of them shares a
|
|
single connection, which those threads would then contend for.
|
|
"""
|
|
|
|
import os
|
|
import tempfile
|
|
|
|
_DB_DIR = tempfile.mkdtemp(prefix="fluksio-test-")
|
|
os.environ.setdefault("DATABASE_URL", f"sqlite:///{_DB_DIR}/app_test.db")
|
|
# Nothing outside this directory: the suite must not pick up a checkout's .env
|
|
# and write into the development data.
|
|
os.environ.setdefault("FLUKSIO_ENV_FILE", os.path.join(_DB_DIR, "env"))
|
|
os.environ.setdefault("DATA_DIR", _DB_DIR)
|
|
# Named here rather than taken from a developer's .env, so the suite is the
|
|
# same run everywhere and a checkout's own superuser is never involved.
|
|
os.environ.setdefault("FIRST_SUPERUSER", "admin@example.com")
|
|
os.environ.setdefault("FIRST_SUPERUSER_PASSWORD", "testpassword")
|
|
# What `emails_enabled` needs; the tests that send mail patch SMTP_HOST on top
|
|
# of it. Nothing is delivered — the sender is faked where it matters.
|
|
os.environ.setdefault("EMAILS_FROM_EMAIL", "noreply@example.com")
|
|
# The MCP session manager can only be entered once per instance, and the suite
|
|
# builds a TestClient — and so a lifespan — per test module. Tests that want the
|
|
# endpoint mount it themselves.
|
|
os.environ["MCP_ENABLED"] = "false"
|
|
# The suite runs from a venv of its own, which "auto" would adopt as if it were
|
|
# a data scientist's — so node code would run on the checkout's environment and
|
|
# the module tests would have nothing of their own to build. The tests that
|
|
# cover adoption ask for it explicitly.
|
|
os.environ["NODE_VENV"] = "managed"
|
|
# The private seeding endpoints are opt-in; the suite is one of the two places
|
|
# (with the dev stack) where they are meant to work.
|
|
os.environ["PRIVATE_API_ENABLED"] = "true"
|
|
# The suite is the development configuration by definition: `/private` is
|
|
# gated on it (app/api/routes/private.py) and the MCP host allow-list admits
|
|
# localhost under it (app/mcp/http.py).
|
|
os.environ["ENVIRONMENT"] = "local"
|