From 66b1118a34990f8b738540008ab50519a4e6741b Mon Sep 17 00:00:00 2001 From: Ross Patterson Date: Sat, 6 Sep 2025 02:06:16 -0700 Subject: [PATCH] docs(automate): Revert run start non-recommended --- .../getting_started/automating_downloads.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/source/guides/getting_started/automating_downloads.rst b/docs/source/guides/getting_started/automating_downloads.rst index b9148166..ceb5d85a 100644 --- a/docs/source/guides/getting_started/automating_downloads.rst +++ b/docs/source/guides/getting_started/automating_downloads.rst @@ -38,13 +38,13 @@ schedule. .. warning:: - Using ``CRON_RUN_ON_START`` is not recommended because it may cause your cron script - to run too often and may trigger throttles and bans. When enabled, your cron script - will run *whenever* the container starts including when the host reboots, when ``# - dockerd`` restarts such as when upgrading Docker itself, when a new image is pulled, - when something applies Compose changes, etc.. This may result in running ``ytdl-sub`` - right before or after the next cron scheduled run. Instead, run your cron script - manually inside the running container as needed: + Using ``CRON_RUN_ON_START`` may cause your cron script to run too often and may + trigger throttles and bans. When enabled, your cron script will run *whenever* the + container starts including when the host reboots, when ``# dockerd`` restarts such as + when upgrading Docker itself, when a new image is pulled, when something applies + Compose changes, etc.. This may result in running ``ytdl-sub`` right before or after + the next cron scheduled run. Instead, run your cron script manually inside the + running container as needed: .. code-block:: console