Changes between Version 5 and Version 6 of web-app-auto-upgrade


Ignore:
Timestamp:
Sep 28, 2017, 11:49:49 AM (2 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • web-app-auto-upgrade

    v5 v6  
    1 = Web Application Auto Upgrade Service =
    2 
    3 [NOTE: Not yet implemented, still under development.]
    4 
    5 May First/People Link provides a service to automatically provide security updates to your web applications. If you opt-in, your web application will be checked every night to see if any security updates are available and, if so, they will be installed.
    6 
    7 By using this service, you will greatly improve the protection of your web site against compromise while also incurring a very small chance that something might go wrong during the upgrade.
    8 
    9 This service is currently available for Drupal and WordPress only.
    10 
    11 The updater will not upgrade all aspects of your site:
    12 
    13  * The automatic upgrader only performs security/minor updates. It does not perform an upgrade from Drupal 7 to Drupal 8, for example. Or from Wordpress 4.5 to 4.6.
    14  * It will not upgrade modules or plugins that are not maintained on the central Drupal or WordPress repositories (for example, CiviCRM is maintained separately, so it won't be upgraded via this script).
    15  * WordPress themes are not updated. Drupal themes are updated.
    16 
    17 [Note: when fully implemented, users can enable via the control panel.]
    18 
    19 An admin can enable this protection by creating a directory in a sites hidden .red directory (e.g. /home/members/mayfirst/sites/mayfirst.org/.red): web-app-auto-upgrade and place one or more files in it.
    20 
    21 To indicate that you want to have your web application automatically upgraded, please create a file or files with the following names to indicate what you want upgraded.
    22 
    23  * drupal-core
    24  * drupal-modules
    25 
    26  * wordpress-core
    27  * wordpress-plugins
    28 
    29 If your web application is directly in your web directory, leave the file empty. If it is in a subdirectory, then put the full, absolute path to the root of your web directory in the file.
    30 
    31 For example, if you want to upgrade both drupal core and drupal modules for a web appication located directly in your web folder, create two files: one called drupal-core and one called drupal-modules in this directory.
    32 
    33 If you have two WordPress installations, one in the web directory and one in a subdirectory called "outreach"  and you just want to auto upgrade the core WordPress code for both of them, create a single file called wordpress-core that contains the absolute path to your main web directory on one line and the absolute path to your outreach directory on the second line (note - when specifying additional directories, you have to specify the web directory if you want it included).
    34 
    35 == Technical Details ==
    36 
    37 All upgrades are run as the user who owns the index.php file in the given directory.
    38 
    39 Drupal core upgrades are run via drush with the following command:
    40 
    41 {{{
    42 drush -y pm-update drupal --security-only
    43 }}}
    44 
    45 Drupal module upgrade are run with the following command:
    46 
    47 {{{
    48 drush -y pm-update --no-core --security-only
    49 }}}
    50 
    51 WordPress upgrades are handled via the following wp-cli commands:
    52 
    53 {{{
    54 wp core update --minor
    55 }}}
    56 
    57 And WordPress plugin updates via:
    58 
    59 {{{
    60 wp plugin update --all
    61 }}}
    62 
    63 NOTE: WordPress sites with a functioning cron job that are higher than version 3.7 already have [https://codex.wordpress.org/Configuring_Automatic_Background_Updates auto-updates enabled] so this step is not necessary, however, it doesn't hurt either.
    64 
     1This page has moved to [wiki:web-app-security].