stroblmeandClaude Opus 5.5
0ac78764c8
The suite creates and deletes flows, dashboards and users, and ran against whatever stack was up, which is the dev instance's data. make test-stack starts the compose project fluksio-test (compose.test.yml over the local stack's files) with its own containers, volumes and image tags, served by the local Traefik on app.test.localhost and api.test.localhost, and leaves it running. The hostname is fixed, so it no longer comes off the running dev stack, and a LAN stack makes no difference. The suite's default origin is the test stack. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx
24 lines
824 B
YAML
24 lines
824 B
YAML
# The frontend suite's own stack. `make test-stack` layers this on
|
|
# compose.local.yml under the project `fluksio-test`, with DOMAIN=test.localhost
|
|
# and STACK_NAME=fluksio-test. It shares the dev stack's Traefik and nothing
|
|
# else: its own containers, volumes, image tags and hostnames, so the flows,
|
|
# dashboards and users the suite creates never reach the dev instance's data.
|
|
services:
|
|
|
|
# `container_name` ignores the project name, so the dev stack's names would
|
|
# collide.
|
|
redis:
|
|
container_name: !reset null
|
|
|
|
backend:
|
|
container_name: !reset null
|
|
# compose.dev.yml also brings up the broker and the time-series database
|
|
# with it, which no spec talks to.
|
|
depends_on: !override
|
|
redis:
|
|
condition: service_healthy
|
|
restart: true
|
|
|
|
frontend:
|
|
container_name: !reset null
|