Insufficient documentation on mail configuration

[akifreak]

Hi @pchurro,

Good catch! The docs didn’t mention the need to run the queue. I assumed those running it in production would be aware, but many users may be new to Laravel. I’ve updated the documentation to clarify this.

Thanks

I can't find much about this in the documentation except this

But I think that there is something missing after Queue system is set up according to.
I have set it up using redis but I still need to run php artisan queue:work manually after the container has started.
What is the recommended way for running the queue automatically and why is it not listed as a separate process in the
supervisord.conf ? (https://github.com/HiEventsDev/Hi.Events/blob/develop/docker/all-in-one/supervisor/supervisord.conf)

Originally posted by @akifreak in #270

[akifreak]

My current solution to avoid executing this command manually is to have my own local copy of supervisord.conf
mounted into the container. It starts the required php process in addition to the other processes.

I guess a better solution would be a separate container that communicates with redis?
If so - how would that look like?

For reference:

docker-compose.yml

---
services:
  allinone:
    image: daveearley/hi.events-all-in-one:v1.0.0-beta.1
    volumes:
      - "./supervisord.conf:/etc/supervisord.conf:ro"

supervisord.conf

[program:php]
command=/usr/local/bin/php artisan queue:work
directory=/app/backend
autostart=true
autorestart=true
stdout_logfile=/dev/stdout
stderr_logfile=/dev/stderr
redirect_stderr=true
stdout_logfile_maxbytes = 0
stderr_logfile_maxbytes = 0