[DOCS] Fix documentation for headless cron path (#1100)

This commit is contained in:
Dan Hand 2024-10-27 03:39:15 +00:00 committed by GitHub
parent 88110a816d
commit 102e2a9042
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -21,7 +21,7 @@ Docker and Unraid
.. tab-item:: GUI Image .. tab-item:: GUI Image
The script that will execute automatically is located at ``/config/ytdl-sub-configs/run-cron``. The script that will execute automatically is located at ``/config/ytdl-sub-configs/run_cron``.
Access your container at http://localhost:8443/, then in the GUI terminal run these commands: Access your container at http://localhost:8443/, then in the GUI terminal run these commands:
@ -81,7 +81,7 @@ Docker and Unraid
docker compose restart 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/run_cron``.
Access your container from the terminal by running: Access your container from the terminal by running:
@ -93,13 +93,13 @@ Docker and Unraid
.. code-block:: shell .. code-block:: shell
echo '#!/bin/bash' > /config/ytdl-sub-configs/run_cron echo '#!/bin/bash' > /config/run_cron
echo "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" >> /config/ytdl-sub-configs/run_cron echo "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" >> /config/run_cron
echo "echo 'Cron started, running ytdl-sub...'" >> /config/ytdl-sub-configs/run_cron echo "echo 'Cron started, running ytdl-sub...'" >> /config/run_cron
echo "cd /config/ytdl-sub-configs" >> /config/ytdl-sub-configs/run_cron echo "cd /config" >> /config/run_cron
echo "ytdl-sub --config=config.yaml sub subscriptions.yaml" >> /config/ytdl-sub-configs/run_cron echo "ytdl-sub --config=config.yaml sub subscriptions.yaml" >> /config/run_cron
chmod +x /config/ytdl-sub-configs/run_cron chmod +x /config/run_cron
chown abc:abc /config/ytdl-sub-configs/run_cron chown abc:abc /config/run_cron
You can test the newly created script by running: You can test the newly created script by running: