docs(automate): Avoid external link 404 responses

This commit is contained in:
Ross Patterson 2025-09-06 01:45:55 -07:00
parent 23b5be713f
commit 3e10633333
No known key found for this signature in database
GPG key ID: 2EFF7CCE6828E359
4 changed files with 8 additions and 8 deletions

View file

@ -41,8 +41,8 @@ download your YouTube cookie, then add it to your :ref:`ytdl options
...automate my downloads? ...automate my downloads?
~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~
:doc:`This page </guides/getting_started/automating>` shows how to set up ``ytdl-sub`` :doc:`This page </guides/getting_started/automating_downloads>` shows how to set up
to run automatically on various platforms. ``ytdl-sub`` to run automatically on various platforms.
...download large channels? ...download large channels?
~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~

View file

@ -50,5 +50,5 @@ instructions to the letter.
#. Automate downloads: #. Automate downloads:
:ref:`Set up ytdl-sub to run periodically <guides/getting_started/automating:docker :ref:`Set up ytdl-sub to run periodically
and unraid>`. <guides/getting_started/automating_downloads:docker and unraid>`.

View file

@ -7,8 +7,8 @@ on top. There are two flavors or variants to choose from. For a more user-friend
experience editing the `configuration`_, we recommend the `GUI image`_ experience editing the `configuration`_, we recommend the `GUI image`_
variant. :ref:`Docker Compose <guides/install/docker:install with docker compose>` is variant. :ref:`Docker Compose <guides/install/docker:install with docker compose>` is
the recommended way of managing a ``ytdl-sub`` docker container. See :ref:`Automating the recommended way of managing a ``ytdl-sub`` docker container. See :ref:`Automating
Downloads <guides/getting_started/automating:docker and unraid>` for how to automate Downloads <guides/getting_started/automating_downloads:docker and unraid>` for how to
running ``ytdl-sub`` in a container running either variant. automate running ``ytdl-sub`` in a container running either variant.
GUI Image GUI Image
@ -28,8 +28,8 @@ Headless Image
The headless image is based on LSIO's :lsio-gh:`docker-baseimage-alpine`. Once running, The headless image is based on LSIO's :lsio-gh:`docker-baseimage-alpine`. Once running,
the default command just starts services including cron for :ref:`Automating Downloads the default command just starts services including cron for :ref:`Automating Downloads
<guides/getting_started/automating:docker and unraid>` but otherwise doesn't run <guides/getting_started/automating_downloads:docker and unraid>` but otherwise doesn't
``ytdl-sub``. You may run arbitrary ``ytdl-sub`` commands using the run ``ytdl-sub``. You may run arbitrary ``ytdl-sub`` commands using the
``--rm --user="${PUID}:${PGID}" --entrypoint="ytdl-sub"`` options to either ``$ docker ``--rm --user="${PUID}:${PGID}" --entrypoint="ytdl-sub"`` options to either ``$ docker
run`` or ``$ docker compose run``. Overriding the image's ``ENTRYPOINT`` is important so run`` or ``$ docker compose run``. Overriding the image's ``ENTRYPOINT`` is important so
that cron doesn't run ``ytdl-sub`` while you're running it manually. that cron doesn't run ``ytdl-sub`` while you're running it manually.