Skip to content
Snippets Groups Projects
Forked from project / automatic_updates
515 commits behind the upstream repository.
omkar.podey's avatar
Issue #3293150 by omkar.podey, phenaproxima, yash.rode: Test that attended...
omkar podey authored
Issue #3293150 by omkar.podey, phenaproxima, yash.rode: Test that attended updates do apply and post-apply operations in separate requests
ae5ae0c4
History

Automatic Updates

Requirements

  • The Drupal project's codebase must be writable in order to use Automatic Updates. This includes Drupal, modules, themes and the Composer dependencies in the vendor directory. This makes Automatic Updates incompatible with some hosting platforms.
  • The Composer executable must be in the PATH of the web server. If the Composer executable cannot be found the location can be set by adding $config['package_manager.settings']['executables']['composer'] = '/path/to/composer'; in settings.php

Limitations

  • Drupal multi-site installations are not supported.
  • Automatic Updates does not support version control such as Git. It is the responsibility of site administrators to commit any updates to version control if needed.

Updating contributed modules and themes

Automatic Updates includes a sub-module, Automatic Updates Extensions, which supports updating contributed modules and themes.

⚠️ ☢️️ Automatic Updates Extensions is still experimental and under heavy development. We encourage you to test it in your local development environment, or another low-stakes testing situation, but it is emphatically NOT ready for use in a production environment. ☢️ ⚠️

Automatic Updates Initiative