Running a local relay stopped being the common case — most of the time we're developing against a real one. Move the relay service behind a `relay` profile so plain `docker compose up` only brings up the app. Use `docker compose --profile relay up` when a local relay is wanted. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
30 lines
807 B
YAML
30 lines
807 B
YAML
services:
|
|
app:
|
|
build: .
|
|
ports:
|
|
- "8088:80"
|
|
volumes:
|
|
- ./data:/var/www/html/data
|
|
- ./src:/var/www/html/src
|
|
- ./public:/var/www/html/public
|
|
- ./config.php:/var/www/html/config.php
|
|
|
|
# Relay is opt-in via the `relay` profile. Plain `docker compose up`
|
|
# starts just the app; use `docker compose --profile relay up` when
|
|
# you want to develop against a local relay instead of a remote one.
|
|
relay:
|
|
build: ./relay
|
|
profiles: ["relay"]
|
|
ports:
|
|
- "8081:80"
|
|
volumes:
|
|
- ./relay/index.php:/var/www/html/index.php
|
|
- ./relay/.htaccess:/var/www/html/.htaccess
|
|
- ./relay/fonts:/var/www/html/fonts
|
|
- ./relay/inc:/var/www/html/inc
|
|
- ./relay/ui:/var/www/html/ui
|
|
- relay-data:/var/www/html/data
|
|
|
|
volumes:
|
|
relay-data:
|