Create documentation for using the auto-update terminal command

Created on 25 May 2023, over 1 year ago
Updated 8 December 2023, about 1 year ago

Problem/Motivation

We created πŸ“Œ Add Drush command to allow running cron updates via console and by a separate user, for defense-in-depth Fixed but we have docs for setting it up and the reasoning why you would want to do this.

Steps to reproduce

Proposed resolution

Create a hook help entry for the drush command and basics of how it should be set up. it should detail

  1. Advantages for using it vs background updates: timeouts, file permissions, guaranteed frequency
  2. setting up via server cron tab. Maybe we could copy some samples from current core cron docs?
  3. Suggested frequency. Lets start with 1 hour

We won't actually link to the help page until πŸ“Œ Enable unattended updates Fixed creates the form for selecting the which method will be used to run cron but we can make the doc page now.

If the help text needs to describe the other method of running updates that is not drush it should described as "background updates" not "cron" because πŸ“Œ For web cron updates run each stage life cycle phase in a different request Closed: won't fix will separate this from cron(but works in similar way)

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Active

Version

3.0

Component

Documentation

Created by

πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024