Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow other symfony/messenger transports than doctrine #533

Open
dheineman opened this issue Jan 3, 2022 · 1 comment · May be fixed by #535
Open

Allow other symfony/messenger transports than doctrine #533

dheineman opened this issue Jan 3, 2022 · 1 comment · May be fixed by #535

Comments

@dheineman
Copy link

The repman environment file has a section for symfony/messenger to allow you to choose a transport by configuring a DSN.

repman/.env

Lines 41 to 46 in 174c381

###> symfony/messenger ###
# Choose one of the transports below
# MESSENGER_TRANSPORT_DSN=amqp://guest:guest@localhost:5672/%2f/messages
# MESSENGER_TRANSPORT_DSN=doctrine://default
# MESSENGER_TRANSPORT_DSN=redis://localhost:6379/messages
###< symfony/messenger ###

However the symfony/messenger config yaml has the doctrine transport hardcoded instead of using this environment variable

transports:
async: 'doctrine://default?auto_setup=false'
failed: 'doctrine://default?queue_name=failed&auto_setup=false'

Similarly only the symfony/doctrine-messenger is required in the composer.json file.

"symfony/doctrine-messenger": "5.3.*",

It there any specific reason this was hardcoded to doctrine? I would like to use the redis transport as it allows multiple workers consuming the same queue.

@akondas
Copy link
Member

akondas commented Jan 3, 2022

It there any specific reason this was hardcoded to doctrine?

No, and I don't see any obstacles to change it 😉

@dheineman dheineman linked a pull request Jan 5, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants