Remove MESSENGER_TRANSPORT_DSN from webapp-pack and enable one in messenger (#1175)

This commit is contained in:
Grégoire Pineau
2023-02-08 13:12:27 +01:00
committed by GitHub
parent b1176e36c4
commit e0eb3d6549
3 changed files with 7 additions and 8 deletions
+3 -3
View File
@@ -4,9 +4,9 @@
},
"env": {
"#1": "Choose one of the transports below",
"#2": "MESSENGER_TRANSPORT_DSN=doctrine://default",
"#3": "MESSENGER_TRANSPORT_DSN=amqp://guest:guest@localhost:5672/%2f/messages",
"#4": "MESSENGER_TRANSPORT_DSN=redis://localhost:6379/messages"
"#2": "MESSENGER_TRANSPORT_DSN=amqp://guest:guest@localhost:5672/%2f/messages",
"#3": "MESSENGER_TRANSPORT_DSN=redis://localhost:6379/messages",
"MESSENGER_TRANSPORT_DSN": "doctrine://default?auto_setup=0"
},
"aliases": ["messenger"],
"conflict": {
+4 -2
View File
@@ -4,8 +4,10 @@
* To send messages to a transport and handle them asynchronously:
1. Uncomment the <info>MESSENGER_TRANSPORT_DSN</> env var in <comment>.env</>
1. Update the <info>MESSENGER_TRANSPORT_DSN</> env var in <comment>.env</> if needed
and <info>framework.messenger.transports.async</> in <comment>config/packages/messenger.yaml</>;
2. Route your message classes to the async transport in <comment>config/packages/messenger.yaml</>.
2. (if using Doctrine) Generate a Doctrine migration <info>bin/console doctrine:migration:diff</>
and execute it <info>bin/console doctrine:migration:migrate</>
3. Route your message classes to the async transport in <comment>config/packages/messenger.yaml</>.
* <fg=blue>Read</> the documentation at <comment>https://symfony.com/doc/current/messenger.html</>
-3
View File
@@ -2,8 +2,5 @@
"aliases": ["webapp"],
"copy-from-recipe": {
"config/": "%CONFIG_DIR%/"
},
"env": {
"MESSENGER_TRANSPORT_DSN": "doctrine://default?auto_setup=0"
}
}