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

How to start the schedule:run command? Already asked on SOF but got no answers. #1318

Closed
oberoivarun opened this issue Dec 21, 2017 · 6 comments
Labels

Comments

@oberoivarun
Copy link

Info:

  • Docker version : 17.09.1-ce, build 19e2cf6
  • Laradock commit : 4e48628
  • System info (Mac, PC, Linux): Windows 10 Pro 64 Bit

Issue:

Scheduler is not running.


Expected behavior:

It should run on its own after running docker-compose up


I'm sure everyone knows the answer to this. But the only thing about cron in the docs is where i can put my own custom cron jobs. Not how i must start the schedule to run indefinitely every minute. So how does one start the schedule?

https://stackoverflow.com/questions/47881421/start-laravel-schedular-on-laradock-cron-jobs

@tjallingt
Copy link

the cron command is in the workspace/crontab/laradock file, it is running by default when you docker-compose up however it doesn't work for me either even though the command shows up in the syslog...

@lulucom
Copy link

lulucom commented Mar 8, 2018

I had a similar issue caused by multiple projects setup.
It was resolved by modifying the path to artisan command in crontab and rebuilding workspace container.

laradock/workspace/crontab/laradock

* * * * * laradock php /var/www/project-1/artisan schedule:run >> /dev/null 2>&1
* * * * * laradock php /var/www/project-2/artisan schedule:run >> /dev/null 2>&1

@tpraxl
Copy link

tpraxl commented Jun 5, 2018

@lulucom That fixed it for me! Thanks.

@NicksonYap
Copy link

turns out i did not notice the path to artisan!

@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants