docker: make relay opt-in via compose profile
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>
This commit is contained in:
1 parent
dce8fa4211
commit
0ac0e34012
1 file changed
+4
@@ -9,8 +9,12 @@ services:
|
|||||||
- ./public:/var/www/html/public
|
- ./public:/var/www/html/public
|
||||||
- ./config.php:/var/www/html/config.php
|
- ./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:
|
relay:
|
||||||
build: ./relay
|
build: ./relay
|
||||||
|
profiles: ["relay"]
|
||||||
ports:
|
ports:
|
||||||
- "8081:80"
|
- "8081:80"
|
||||||
volumes:
|
volumes:
|
||||||
|
|||||||
Reference in new issue
Block a user