Aegir 3.16.0

The Aegir team is proud to announce a new release in the stable 3.x branch!

This release ships with a number of bug fixes and UI improvements.

Project Description Links Status
Provision Drush commands drupal.org
github.com
gitlab.com
build status
Hosting Drupal Modules drupal.org/project/hosting
github.com/aegir-project/hosting
Hostmaster Drupal Install Profile drupal.org/project/hostmaster
github.com/aegir-project/hostmaster
Dockerfiles Docker image definitions. Used for all tests. github.com/aegir-project/dockerfiles
hub.docker.com/r/aegir/hostmaster
Tests Behat tests and Travis tools github.com/aegir-project/tests
Development Environment Local docker-based development environment. github.com/aegir-project/development Build Status

Installing and upgrading

The canonical source of installation documentation is

http://docs.aegirproject.org/en/3.x/install/

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes.

It is still imperative that you read the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

Need help?

If you struggle to install or upgrade your Aegir system, you have a number of options available to you for getting help.

Consult this page for more information: http://docs.aegirproject.org/en/3.x/community

Thanks to our awesome community for their help, support and encouragement as always! Enjoy the new release :)

Changes

Changes to hostmaster since 7.x-3.150

  • Update libraries API module
  • #2969210: Aegir: Avoid count() calls on uncountable variables (PHP 7.2)
  • Updateed versions of betterlogin and views_bulk_operations
  • Update tfa_basic to 1.1
  • #2962836: Fixup makefile

Changes to provision since 7.x-3.150

  • Adding a $throw_drush_error parameter to provision_process(), to allow implementors to avoid crashing drush if a process fails. Also adding doc block.
  • Default the "error message" to NULL. Once the logs are rendered nicely, we don't need an extra "Process failed" message.
  • Do nothing if the command is empty.
  • #2991769: When I disable a site that has letsencrypt enabled I cannot restart the webserver
  • Save the Process component to drush context so implementors can get access.
  • #2974291 by fastangel: Add Symfony Process component and a provision_process() method
  • #2791095 by nwom, bgm, colan: Allow for dynamic PHP 7 socket file locations.
  • #2952366 by helmo, antoine.guichard, memtkmcc: Exclude /.well-known/acme-challenge from "HTTPS Required"
  • #2980946 by lunatic: Allow access to /modules/statistics.php
  • #2979542 by andkar: Drupal 8 sub-sites gets error message: ”The provided host name is not valid for this server”
  • #2979947 by kienan: Debian package for aegir3-hostmaster always asks for db_password during install
  • #2567173 by helmo: docs, change to the selected alias ... to match hosting_https
  • #2567173 by captainack: No redirect to site alias if SSL required
  • #2976164 by daften: Installation with a remote db server fails
  • Fix publish_path to root in two more places, similar to what @valkum found
  • change publish_path to root for platform settings
  • #2962836 by colan, helmo: The each() function is deprecated in PHP 7.2

Changes to hosting since 7.x-3.150

Changes to eldir since 7.x-3.150

Changes to hosting_civicrm since 7.x-3.150

  • _provision_civicrm_upgradedb: show the code/db versions before starting the upgrade.
  • hosting_civicrm_cron: use time() instead of mktime().
  • Drupal8: Better fix for the crmpath. We should always use an absolute path (required for the REST API endpoint, which will WSoD otherwise).
  • Drupal8: Fix _provision_civicrm_codebase_version() to correctly fix the CiviCRM code version (fixes 'verify' calling the upgrade, then failing because no upgrade was necessary).

Changes to hosting_git since 7.x-3.150

  • Add a display of the current git reference to the Git Checkout and Git Tag form. Cleanup ordering, form element titles and descriptions, and allow a ?create=1 URL parameter to the Checkout task to change the UI to specifically target "Creation".
  • Converting Git Tag task to use provision_process().
  • Refactoring Git and Features code out of devshop and into aegir. Adding Git Commit module, removing aegir_commit from devshop, and fixing everything.
  • Add form alter to Hosting_Git module to allow commits after Features update task.
  • After a git checkout task, schedule a verify task in hostmaster for the platform, don't just run it on the back end. This is so the front-end receives the info about the branch.
  • Standardizing options and arguments for Hosting Git Checkout and Tag modules.
  • Removing unneeded drush log, provision handles it all.
  • #2989954 by fastangel: Implement new 'provision_process()' method for git clone
  • Allow editing of repo URL, docroot and git ref if the platform has not been verified.
  • #2981195 by c_archer: Update IP ranges whitelist for BitBucket
  • Change the logic used on the form to allow editing if the platform has not been verified yet.
  • #2971666 by abhinand-gokhala-k: Platform verification failed if we use Git repo

Changes to hosting_remote_import since 7.x-3.150

Changes to hosting_site_backup_manager since 7.x-3.150

  • None

Changes to hosting_tasks_extra since 7.x-3.150

  • Default to not revert features.
  • Use exact terminology.
  • Upgrading Hosting Tasks Extras "Features Update & Revert" tasks with: - Ability to specify which features to update or revert. - Add "Force" option to "revert" task. - Migrate all to provision_process(). - Creating a hosting_tasks_extra.drush.inc file because that is the only place drush_hook_pre_hosting_task() works. - Improving the form page: adding a form alter for easy page title renaming for other tasks.
  • #2982704 by fastangel: Bug loading info for http auth

Changes to hosting_logs since 7.x-3.150

  • None

Changes to hosting_https since 7.x-3.150

Known Issues

  • There is a regression in 3.16.0 that makes migrations fail 'There are no valid install profiles on the target platform to migrate to'. See #3001670 for that patch.
  • When the MYSQL password policy was set to MEDIUM creating databases can fail, see issue 2868803 for more info.
  • When upgrading from Aegir 2.x be aware of these notes.

For a full list of issues, see our combined issue queues