If I set environment variables like SYMFONY__RABBITMQ_HOST on my server (or in this case docker container, but whatever), then add a rabbitmq-cli-consumer program to my supervisord config, supervisor is kind enough to copy the environment into the process that runs rabbitmq-cli-consumer, but alas when the consumer runs the symfony command, that environment isn't present, so it fails. I hope that makes sense :smile:
Ideally rabbitmq-cli-consumer would copy its environment into the shell running the configured command. Alternatively being able to set environment variables on the command line (or from a config file) would also be ok.
I'll take this into consideration for v2, but can't promise it'll be in the first version. I do see the use case though, so I'll add it to the feature list.
If I set environment variables like
SYMFONY__RABBITMQ_HOST
on my server (or in this case docker container, but whatever), then add arabbitmq-cli-consumer
program to my supervisord config, supervisor is kind enough to copy the environment into the process that runsrabbitmq-cli-consumer
, but alas when the consumer runs the symfony command, that environment isn't present, so it fails. I hope that makes sense :smile:Ideally
rabbitmq-cli-consumer
would copy its environment into the shell running the configured command. Alternatively being able to set environment variables on the command line (or from a config file) would also be ok.