From 506f1f9a67c29eb162a8b0b7dc1e93f8d7497e5a Mon Sep 17 00:00:00 2001 From: Hugo Alliaume Date: Tue, 8 Jun 2021 14:34:48 +0200 Subject: [PATCH] [Symfony CLI] Docker integration and MailCatcher prefix Hi :wave: Given my `docker-compose.yaml`: ```yaml version: '3.6' volumes: db-data: redis-data: services: database: image: 'mysql:5.7' ports: [3306] environment: MYSQL_USER: 'app' MYSQL_PASSWORD: 'app' MYSQL_DATABASE: 'app' MYSQL_ALLOW_EMPTY_PASSWORD: 'yes' TZ: Etc/UTC volumes: - db-data:/var/lib/mysql - .manala/init-db:/docker-entrypoint-initdb.d healthcheck: test: mysqladmin ping --silent interval: 10s timeout: 5s retries: 5 phpmyadmin: image: phpmyadmin ports: [80] environment: PMA_HOST: 'database' PMA_USER: 'app' PMA_PASSWORD: 'app' redis: image: 'redis:alpine' ports: [6379] environment: TZ: Etc/UTC volumes: - redis-data:/data phpredisadmin: image: erikdubbelboer/phpredisadmin ports: [80] environment: REDIS_1_HOST: 'redis' mailcatcher: image: 'schickling/mailcatcher' ports: [1025, 1080] environment: TZ: Etc/UTC ``` When running `docker-compose up` and `symfony var:export --multiline`, the env vars for MailCatcher are prefixed (by default) by `MAILCATCHER_` but not by `MAILER_`. --- setup/symfony_server.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup/symfony_server.rst b/setup/symfony_server.rst index 7420a822ab6..087622036a2 100644 --- a/setup/symfony_server.rst +++ b/setup/symfony_server.rst @@ -352,7 +352,7 @@ RabbitMQ 5672 ``RABBITMQ_`` (set user and pass via Docker ``RABBITMQ_D Elasticsearch 9200 ``ELASTICSEARCH_`` MongoDB 27017 ``MONGODB_`` (set the database via a Docker ``MONGO_DATABASE`` env var) Kafka 9092 ``KAFKA_`` -MailCatcher 1025/1080 ``MAILER_`` +MailCatcher 1025/1080 ``MAILCATCHER_`` or 25/80 Blackfire 8707 ``BLACKFIRE_`` ============= ========= ====================== pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy