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.

Sign up for GitHub

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

Add notes for the scheduler setup #163

Merged
merged 4 commits into from
Jul 30, 2024
Merged

Add notes for the scheduler setup #163

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4c32854
[fix] scheduler code example
AIC-BV Oct 17, 2023
bb56a71
Update installation.md
AIC-BV Oct 17, 2023
a12ad4b
Update setup/installation.md
LukeTowers Jul 30, 2024
debdbe8
Update setup/installation.md
LukeTowers Jul 30, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion setup/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ If you intend to use scheduled tasks, or install plugins that use scheduled task
* * * * * php /path/to/artisan schedule:run >> /dev/null 2>&1
```

Be sure to replace `/path/to/artisan` with the absolute path to the `artisan` file in the root directory of your Winter installation. This cron task will call the command scheduler every minute, to which Winter will evaluate any scheduled tasks and run the tasks that are due for execution.
Be sure to replace `php` with the absolute path to the `php` file and also replace `/path/to/artisan` with the absolute path to the `artisan` file in the root directory of your Winter installation. This cron task will call the command scheduler every minute, to which Winter will evaluate any scheduled tasks and run the tasks that are due for execution.
LukeTowers marked this conversation as resolved.
Show resolved Hide resolved

LukeTowers marked this conversation as resolved.
Show resolved Hide resolved
> **NOTE**: If you are adding this to the system crontab (`/etc/cron.d`), you'll need to specify the user to run the command as immediately after `* * * * *`.

Expand Down