Messenger transport names for DEV #60495
-
|
I have a server where I have 2 domains, one for production, one for development. Two document roots, two sets of codes (the same as this is the same app), to databases but one RabbitMQ instance for the whole server. In framework.messenger.transport the prototype for the config is to set the name of the transport as a key for the config. I would like to use it only as a key but inside, add for instance name attribute and here put env variable. Is there a solution for this apart from setting up RabbitMQ on different server? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
RabbitMQ has a concept of vhost, where exchange names and queue names only need to be unique inside the vhost. You can use separate vhosts for your production and development deployments. In the DSN, the |
Beta Was this translation helpful? Give feedback.
-
|
Indeed, work perfectly, thank you very much :) |
Beta Was this translation helpful? Give feedback.
RabbitMQ has a concept of vhost, where exchange names and queue names only need to be unique inside the vhost. You can use separate vhosts for your production and development deployments.
In the DSN, the
vhostcan be configured in the path part of the URI (if you have a/in your vhost name, it must be URL-encoded, as the TransportFactory reads the first segment of the path only)