-
Notifications
You must be signed in to change notification settings - Fork 73
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
Fix documentation for cron path #1100
Conversation
@@ -81,7 +81,7 @@ Docker and Unraid | |||
|
|||
docker compose restart | |||
|
|||
The script that will execute automatically is located at ``/config/run-cron``. | |||
The script that will execute automatically is located at ``/config/ytdl-sub-configs/run_cron``. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/config/run_cron
is the path for headless -- doesn't have the ytdl-sub-configs
folder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the .. tab-item
part which separates GUI from headless
@@ -105,14 +105,14 @@ Docker and Unraid | |||
|
|||
.. code-block:: | |||
|
|||
/config/run_cron | |||
/config/ytdl-sub-configs/run_cron |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's actually right above this part that needs to not use ytdl-sub-configs
🙂
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1100 +/- ##
=======================================
Coverage 91.44% 91.44%
=======================================
Files 113 113
Lines 7430 7430
=======================================
Hits 6794 6794
Misses 636 636 ☔ View full report in Codecov by Sentry. |
Much appreciated @dsgnr ! |
Fixes cron paths in documentation.
Spotted these when configuring. Then noticed #1073 was already open.
Resolves #1073