community.aegirproject.org

Release Notes

Archive of release notes and changelogs

3.0 release notes

Tagged:

The Aegir team is very pleased to announce the official release of Aegir 3.0. This release ships with significant stability improvements, Drush 6 and 7 support, improved SSL, subdirectory multisite and nginx support and much, much more!

This release marks the deprecation of the 2.x branch. We will continue to provide security releases through the end of 2015. All Aegir users are strongly encouraged to upgrade to the 3.0 release. The upgrade has been thoroughly tested and has worked reliably for us.

Upgrading from Aegir 2.x moves Aegir from a Drupal 6 platform to a Drupal 7 one. The Debian package will migrate the front-end for you. While we have tested this with Aegir core, we strongly recommend disabling any contributed modules you may be running.

We have a very dynamic community of contrib developers, and various projects built atop Aegir. So if you were waiting for Aegir 3 to be stable, easy to install and production-ready, now is the time. The 3.x branch will be well supported as a lot of shops are running it in production already.

1. Major changes

The front-end has been ported to Drupal 7. We've also raised the minimum Drush version to 6.x, and the Debian package now installs Drush via Composer. Drush 7 is also supported.

We've added several "Golden contrib" modules to the distribution:

  • Hosting Remote Import
  • Hosting Site Backup Manager
  • Hosting Git
  • Hosting Tasks Extra

We're planning to add additional well-supported contrib modules over the course of the Aegir 3.x lifecycle. Along similar lines, we've removed hosting_platform_pathauto, as it's built-in now.

We've introduced initial Drupal 8 support, though this is still a work-in-progress. This mostly depends on Drupal 8 and Drush 8 stabilizing, before we'll be able to more fully manage Drupal 8 sites.

Aegir 3 now supports SNI for SSL.

A number of significant bug fixes and stability improvements have been incorporated. Among them, we've added locking in our task queue, and improved backup reliability significantly.

For more information, please see the slidedeck from the presentation by ergonlogic and helmo at the Aegir Summit: http://community.aegirproject.org/sites/community.aegirproject.org/files...

Back to top

2. Major API changes

The API has not significantly changed, though there are a few additions. See the current API docs in the various repositories for additional details.

Back to top

3. Installing and upgrading

The canonical source of installation documentation is

http://docs.aegirproject.org/en/latest/install/install/

We're in the process of converting our docs, the old version is on http://community.aegirproject.org/installing We're tracking the conversion on https://www.drupal.org/node/2534734

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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

Note that you should upgrade to the latest 2.x release (currently: 2.4) before attempting the upgrade to 3.x..

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.

Back to top

4. 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://community.aegirproject.org/help

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

Back to top

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Changes since 7.x-3.0-rc1:

  • #2494121: Stop servers in clusters from sync'ing back to master.
  • Make the upgrade script slightly more verbose
  • #2377819: Gzipping backups suppresses file permissions errors
Back to top

6. Known issues

  • Drupal 8 support is (Chasing HEAD) not complete. You would need Drush 8 for that.
  • Drush master has an issue on Debian Wheezy (https://www.drupal.org/node/2491941)
  • When upgrading from 6.x-2.x enable the betterlogin module manually.
Back to top

3.0-rc1 release notes

The Aegir team is pleased to announce the first release candidate of the Aegir 3.x branch, after months of development. Development has been sometimes intermittent, but it is not over yet!

This release is tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

  • None, mostly small bugfixes
Back to top

2. Major API changes

to be determined.

Back to top

3. Installing and upgrading

The canonical source of installation documentation is

http://docs.aegirproject.org/en/latest/install.html

We're in the process of converting our docs, the old version is on http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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

Note that you should upgrade to the latest 2.x release (currently: 2.4) before attempting the upgrade to 3.x..

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.

Back to top

4. 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://community.aegirproject.org/help

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

Back to top

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Changes to hostmaster since 7.x-3.0-beta2:

Changes to provision since 7.x-3.0-beta2:

  • #2530904 by PascalAnimateur: Unknown package version in Drupal 7
  • #2530904 by PascalAnimateur, ybabel: Package version always set to Unknown
  • #2511772 by danwonac - Nginx: Restore support for legacy rewrites non-clean URLs
  • #2497091 - The replacement string in the third line needs to be literal
  • Clarify regex alter function API docs.
  • Replace drupal_set_message by drush_log
  • #2496417: Drupal 6 and PHP 5.6 (Debian Jessie)
  • Match Drush 8
  • Set port properly when generating temporary .my.cnf.

Changes to hosting since 7.x-3.0-beta2:

Back to top

6. Known issues

Back to top

3.0-beta2 release notes

The Aegir team is pleased to announce the forth preview release (beta) of the Aegir 3.x branch, after months of development. Development has been sometimes intermittent, but it is not over yet!

This release is tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More beta releases will be published when there are substantial changes.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

  • Fixed a security issue in the protection of the files directory for multi-site.
  • Improved SSL support
  • Both Drush stable (6.6.0) and 7.x (the master branch) are supported.
Back to top

2. Major API changes

to be determined.

Back to top

3. Installing and upgrading

The canonical source of installation documentation is

http://docs.aegirproject.org/en/latest/install.html

We're in the process of converting our docs, the old version is on http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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

Note that you should upgrade to the latest 2.x release (currently: 2.4) before attempting the upgrade to 3.x..

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.

Back to top

4. 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://community.aegirproject.org/help

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

Back to top

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Changes ho hostmaster since 7.x-3.0-beta1:

  • Add hosting_remote_import to the distro.
  • Update the views version in our makefile.
  • Remove hosting_platform_pathauto, as it's built-in now.

Changes to provision since 7.x-3.0-beta1:

  • Fix protection of files dir for multi-site
  • #2036333: Remove CVS deploy code.
  • Fix queue lock name.
  • Fix syntax error.
  • Rework bypassing of task queue lock.
  • Fix lock waiting for tests.
  • Use Drupal API function for lock waiting.
  • #2479345: Wait for a lock on the tasks queue to be available.
  • #2479885: Remove anchors and double-escaping from regexes.
  • #2479885: Fix mysql filtering regex anchors.
  • Add provision-tests-new-run command to start testing D8.
  • #2474197: Debian package for aegir3 should depend on curl
  • #2475527: Catch additional DB connection failures, and provide more meaningful error messages.
  • Generate an SSL certificate for use in the default SSL vhost.
  • Add NameVirtualHost for SSL, regardless of IP addresses.
  • Merge branch 'dev/mysqldump-error-check' into 7.x-3.x
  • Fix up docs.
  • Anchor regexes, cleanup docs.
  • Split regexes into helper function with alter hook and static caching, and add docs for new hook.
  • Clarify docs.
  • Split mysqldump filtering into a helper function.
  • Dedupe generating descriptors fro proc_open().
  • Document new method and fix typos.
  • Dedupe temporary mysql config generation.
  • Fix up some syntax errors.
  • fix comment typo
  • handle mysqldump errors again
  • #2471805: Add hook_provision_deploy_options_alter() invocations to migrate and restore, and document it in te API.
  • #2471805: Add hook to allow injecting options into clone deploy tasks.
  • Rename incorrect verify method.
  • #2468203: provision-save: default profile from 'default' to 'standard'
  • upgrade.sh: move variables to the top
  • upgrade.sh: move function definition
  • ssue #2460023: Fix existing symlink problem in Ubuntu/Debian upgrades.
  • Cleanup upgrade.sh script
  • Rename DRUSH_VERSION variable to separate current and new
  • Fix Drush version in upgrade script

Changes to hosting since 7.x-3.0-beta1:

  • escape < and >
  • D7 API update
  • code style updates
  • Form API update
  • Allow sites to be installed when SSL is enabled, but no servers provide the SSL service yet.
  • Fix typo in table class.
  • Redirect to home page after deleting a Hosting object.
  • Allow re-use of deleted servers' hostnames.
  • Don't block tasks queue when running queue daemon.
  • Release locks in other shotdown contexts.
  • Move lock acquisition and release outside of main queue daemon loop.
  • Fix queue lock name.
  • #2479345: Refactor queue locking to use Drupal API.
  • #2464949: Avoid needless saving of related nodes on context_import
  • Fix codestyle
  • Log which task starts processing
  • Pass less optionss ... to prevent Unknown option errors.
  • Stop overwriting node titles when importing context data.
  • Fix platform migrate confirmation form status.
  • #2479001 by mwisner: Fix platform migrate task form does not rebuild correctly
  • Fix platform migrate form checks for sites and available target platforms.
  • Provide a default platform.
  • Allow platform paths to have slashes.
  • #2469179: Remove duplicate call to hosting_ssl_filter_key, its in hosting_ssl_nodeapi_site_validate
  • #2469179: Improve saving a new SSL key
  • #2475455: Document the place for am intermediate certificate.
  • Try again to keep warning/error jump links within overlay.
  • Keep warning/error jump links within overlay.
  • #2175619: Add links to first warning or error in task log.
  • Fix check for a platform's path already existing.
  • #2474801: Fix task cancellation.
  • Syntax fix.
  • Add global option to always, never or prompt to delete site backups.
  • #1397798 by chertzog, Dane Powell, et. al.: Optionally delete site backups when a site is deleted.
  • #2471094: Update the site node with the database name after imports.
  • Import site by calling the relevant function directly instead of invoking a sub-process, etc.
  • Revert "properly import db_name after site import"
  • Merge branch 'dev/hosting-import-dbname' into 7.x-3.x
  • partly revert e3bb221: properly save drush output
  • properly import db_name after site import
  • code cleanup
  • Improve ssl description
  • #2453807: Convert clients list block to views
  • Merge backend output.
  • #2470297: Run 'hosting-import' after 'provision-import' on 'import' tasks.
  • Revert portion of last commit, included by mistake. It will be part of the nest commit.
  • Show backend output that was being lost.
  • #2470297: Stop overwriting context prior to import.
  • Set platform path automatically, based on title.
  • Move site SSL fields into fieldset.
  • Merge remote-tracking branch 'origin/dev-sni' into 7.x-3.x
  • #2069431: Indicate next steps after enabling the SSL feature.
  • Fix backup-delete form validation warnings.
  • Fix restore form validation warning.
  • #2460937: Fix backup deletion.
  • Add some checks to backup delete validation.
  • only warn about SNI, do not disable SSL, when IP allocation fails
  • do not set IP address if none provided, this should permit SNI, in the frontend at least
Back to top

6. Known issues

Back to top

2.4 release notes

The Aegir team is proud to announce the forth release in the stable 2.x release branch!

This maintenance release ships with a security fix for Apache installations. Everyone is encouraged to upgrade. Re-verify is required for all sites (Views bulk operations makes this easy)

Also, worth noting is the simultaneous release of our second beta for Aegir 3. Debian packages are now being provided for Aegir 3, so trying it out is easier than ever!

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is at:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

N.B. Issue #2146977: Broken backward compatibility with IP based vhosts may affect those upgrading from 1.x. It appears that running 'verify' tasks on all sites should resolve the issue.

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Known issues

Being really open about our project, we have never hidden the fact that some things, sometimes, do not work in Aegir. Our issue trackers are public, and we've made it a point of honor not only to document clearly what is wrong in our releases as soon as we find out about it, but also to reroll new releases when we fix it.

That being said, 2.4 still has a number of issues and design flaws. This is the list of all issues marked "major" in the queue right now. Most issues are now likely to be fixed in the 3.x development branch, and unlikely to be backported unless considered critical.

As mentioned in the previous section, Issue #2146977: Broken backward compatibility with IP based vhosts is still listed as a 'critical' issue against the 2.x branch. However, it should only affect those upgrading from 1.x, and has a fairly simple work-around. If you come across this behaviour during your upgrade, please post a comment to the issue, so we can confirm that it still exists.

Back to top

4. Features

Back to top

5. Bug fixes

  • Just the mentioned security fix
Back to top

1.12 release notes

Tagged:

The Aegir team is proud to announce the twelfth (and final!) release in the now deprecated 1.x release branch! This release was necessary to cover the new Modalframe security release that made 1.11 uninstallable. Everyone is encouraged to upgrade to the latest 2.x release.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Known issues

The modalframe upgrade broke popups, but the content is visible so it is a minor regression. Upgrade to 2.x to get a real fix.

Otherwise the same as the 1.11 release.

Back to top

4. Features

  • Apache 2.4 is now supported in the 1.x branch, see #2153929 and #2155445 (7 weeks ago)
Back to top

5. Security fixes

Back to top

6. Bug fixes

  • the jQuery download URL was fixed
Back to top

3.0 alphas, betas & release candidates

This section documents all the release candidates towards the 3.0 release.

3.0-alpha1 release notes

The Aegir team is pleased to announce the first preview release (alpha) of the Aegir 3.x branch, after months of development. We have been pretty busy with the maintenance of the 2.x branch, so development has been sometimes intermittent, but it is not over yet!

This release is only a first of a series of alpha releases that are tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More alpha releases will be published when there are substantial changes.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

  • Frontend ported to Drupal 7
  • Raised minimum Drush version to 6.x
    • Drush 7.x is supported, but that's a matter of chasing head.
Back to top

2. Major API changes

to be determined.

Back to top

3. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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

Note that you should upgrade to the latest 1.x release (currently: 1.9) before attempting the upgrade to 2.x. This is especially important if you are running a pre-1.0 release (poor you!).

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.

Back to top

4. 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://community.aegirproject.org/help

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

Back to top

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Back to top

6. Bugfixes

This is a non-exhaustive list.

Back to top

7. Known issues

  • The devel module is listed as dependancy for the hostmaster install profile, but is not included in the drupal.org build.
Back to top

3.0-alpha2 release notes

The Aegir team is pleased to announce the second preview release (alpha) of the Aegir 3.x branch, after months of development. Development has been sometimes intermittent, but it is not over yet!

This release is tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More alpha releases will be published when there are substantial changes.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

  • Improved Drupal 8 support
Back to top

2. Major API changes

to be determined.

Back to top

3. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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

Note that you should upgrade to the latest 2.x release (currently: 2.1) before attempting the upgrade to 3.x..

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.

Back to top

4. 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://community.aegirproject.org/help

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

Back to top

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Back to top

6. Bugfixes

This is a non-exhaustive list.

Changes since 7.x-3.0-alpha1:

  • Improve readability of message
  • #2348173 by helmo: Remove unused vars causing trouble
  • #2372653 by helmo: Add --no-autocommit when dumping MySQL tables
  • typo
  • Fix platform name in demo content
  • don't make the example module warn so much
  • propagate example_field properly to the backend
  • Improve debug messages in Config classes.
  • Nginx: Helper locations to avoid 404 on legacy images paths (subdir only)
  • Nginx: Fix spacing
  • Nginx: Add missing variables in subdirectory config template.
  • don't allow d() to run before drush is fully initialized
  • clarify little debugging markers
  • silence the last warning, it's actually not one
  • add debugging: when no service type is specified from the frontend, yell a warning
  • remove dead code: $base_dir is not used anywhere in that function
  • Split arrays and hooks to alter chmod and chgrp file operations.
  • Add server data example module, which doesn't currently work.
  • Add post_verify hook for site_data module.
  • Remove legacy drush load for site data example module.
  • revert previous commit, it's too noisy
  • clarify traces in site_data module
  • Nginx: Add the fix for known problem with files/imagecache in legacy D6 sites (again).
  • Remove openatrium2 from testcase, build fails too often on external issues
  • Update openatrium2 test platform to new tag
  • Rename makefiles to .make extension
  • #2373835 by helmo | realityloop: 3.x doesn't currently install.
  • Nginx: Fail early if any required db credentials are empty, to never create broken vhost.
  • Nginx: Block semalt botnet (extended boa mode only)
  • Nginx: Batch merge updates from 6.x configuration (2)
  • Nginx: Batch merge from 6.x configuration.
  • Correct package name in changelog
  • Update debian package info to have aegir3 in the name
  • Fix branch name for 7.x-3.x in debian git-buildpackage
  • #2358795: Adding a "$force" parameter to setProperty() to allow overwriting of default context properties.
  • #2358795 Adding a provision-save to provision_verify command.
  • #2361729 by joestewart: Fixed D8 Platform verify doesn't add module version to package.
  • #2365171 by joestewart: Fixed D8 Contrib profiles in /profiles undetected.
  • #2362707 by joestewart: D8: update private and temporary paths after cloning
  • allow overrides to the site-specific drushrc.php file
  • #2163979 - Check if field_info_field_map() is available to not break support for old D7 versions.
  • #1995506 by Jon Pugh: Added Implement "--profile" option for "drush hostmaster-install".
  • Add API doc for new hook.
  • Allow altering the list of directories to recurse into on site/platform creation.
  • Removed a bashism
  • #2348879 by Deciphered, helmo: Fixed Welcome Mail - url() deprecated.
  • Remove a trailing space char
  • refactor
  • Improve error handling, better message and fail earlier.
  • #2300537 by helmo | ergonlogic: Added Merge Provision extensions into Hosting modules.
  • Make sure that db_port is never empty and defaults to 3306.
  • Add drupal 8 to provision-demo-content
  • #2346903 by helmo: Added Always disable allow_authorize_operations.
  • #2311005 by Deciphered, clemens.tolboom: Fixed D8 Site install fails on undefined indexes.
  • #2306055 by Deciphered, realityloop, helmo, clemens.tolboom: Fixed Platform verify fails for Drupal 8 under Aegir 3.x.
  • #2346967 by Deciphered: Fixed Onetime login link broken.
  • Pin test makefile of openatrium to stable version, to avoid build problems.
Back to top

7. Known issues

  • Drupal 8 support is (Chasing HEAD) not complete.
  • Upgrading a hosted site from D6 to D7 has complications with Drush > 7.0.0-alpha6 issue
Back to top

3.0-beta1 release notes

The Aegir team is pleased to announce the third preview release (beta) of the Aegir 3.x branch, after months of development. Development has been sometimes intermittent, but it is not over yet!

This release is tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More alpha releases will be published when there are substantial changes.

In the issue queues the central roadmap issue is: #1261030 [meta] Roadmap: Aegir 3.x (D7 port)

1. Major changes

  • Improved Drupal 8 support
  • Both Drush stable (6.5.0) and 7.x (the master branch) are supported.
Back to top

2. Major API changes

to be determined.

Back to top

3. Installing and upgrading

The canonical source of installation documentation is

http://docs.aegirproject.org/en/latest/install.html

We're in the process of converting our docs, the old version is on http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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

Note that you should upgrade to the latest 2.x release (currently: 2.3) before attempting the upgrade to 3.x..

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.

Back to top

4. 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://community.aegirproject.org/help

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

Back to top

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Changes to hostmaster since 7.x-3.0-alpha2:

  • #2450683 by cweagans: Enable r4032login in the default hostmaster install
  • Update the ctools version in our makefile.
  • Update the entity API version in our makefile.
  • #2421341 by clemens.tolboom, helmo: Add default permissions on install
  • Regular contrib updates for admin_menu, betterlogin and ctools
  • Update the views version in our makefile.
  • #2393567: Betterlogin's anon redirect causes issues with services

Changes to hosting since 7.x-3.0-alpha2:

  • #2448855 by Pol: Makefile field not saved when importing platforms
  • log task processing in drupal
  • #2393579: Signup feature cleanup
  • #2407885: refactor SSL forms - hide other SSL fields when not enabled.
  • SSL code cleanup
  • Rename hosting_ip_delete to _hosting_ip_delete to avoid looking like hook_delete
  • Rename hosting_ip_load to _hosting_ip_load to avoid looking like hook_load
  • Rename hosting_ip_validate to _hosting_ip_validate to avoid looking like hook_validate
  • Rename hosting_ip_save to _hosting_ip_save to avoid looking like hook_save
  • Rename hosting_ip_view to _hosting_ip_view to avoid looking like hook_view
  • Fix typo in variable name
  • Allow numbers in Hosting feature names.
  • Fix logic flaw
  • Fix remaining boolean in access grants.
  • #2410603: Fix default value
  • #2410603: Working copy isn't currently working
  • Remove duplicate reaction to enabling modules.
  • Allow scripts to skip automatic verify tasks when enabling modules by passing '--no-verify'.
  • Hook into module being disabled
  • node_revisions table name changed to node_revision with D7
  • #2430807 by clemens.tolboom, helmo: Roles order is reversed to advised order.
  • Fix default permissions for optional submodules
  • Fix typo in permission name
  • #2432397: Add static cache to hook_node_grants
  • #2430809 by clemens.tolboom: Notice: Undefined variable: grants
  • Do not add validation when the form elements are not added
  • #2430103 by clemens.tolboom: hosting_client: Strict warning: Only variables should be passed by reference
  • Update db placeholders
  • #2410209: Use bigint to store backup size
  • Log which drush task hooks we're invoking.
  • #2210813 by ergonlogic, realityloop: Follow-up from D7 DBTNG changes
  • Rename constant MAX_GROUP_LENGTH to HOSTING_CLIENT_MAX_GROUP_LENGTH
  • #2408365 by clemens.tolboom: Strict warning when adding new client

Changes to provision since 7.x-3.0-alpha2:

  • #2457359: Stop overriding Nginx SSL settings
  • #2396299 by ergonlogic: Stop comparing platform package versions when said package is installed in the site
  • Merge branch '7.x-3.x' of git.drupal.org:project/provision into 7.x-3.x
  • Nginx: Stop the POST flood to /autodiscover/autodiscover.xml generated by MS Office/Outlook
  • Debian: improve setting directory permissions.
  • #2193427 by helmo: Remove Debian package requirement for Drush
  • Make php5-gd a dependency of the aegir3-hostmaster package, as its required to install core
  • Log site installation exception.
  • Update absolute URLs to files for sites cloned/migrated/renamed
  • Nginx: Use dummy db fastcgi_param placeholders if any of them is empty
  • #2350695 by omega8cc, helmo: Profile is registered twice, also as a module, which causes warning
  • Nginx: Remove webform keyword from regex locations - fixes #599
  • Remove Drupal 8 specific stuff from D7/D6 template.
  • Both maintenance_mode and clean_url are ignored in Drupal 8
  • Fix for custom cpuinfo logic.
  • Nginx: Sync configuration improvements.
  • Remove docs for non-existing option
  • Add the working-copy option to hostmaster-migrate, similar to hostmaster-install
  • hostmaster-resume was renamed to hosting-resume
  • #2421543 by notzach: Changing how Apache ServerAliases are defined
  • Drupal 8 requires trusted_host_patterns defined in settings.php
  • Drupal 8 requires container_yamls defined
  • Nginx: Use safe fallback for mysteriously empty $db_port
  • Nginx: Use reliable source for db_port to write in the vhost
  • #2409085 by clemens.tolboom: Use mutatable interface in install_8.inc
  • #2387953: Remove drush-make from Debian suggest line.
  • #2276557 by zxaos, bgm: allow aegir2-provision package to accept mariadb or mysql
  • Nginx: Fix for D8-specific /cron/ location caching (extended mode only).
  • Nginx: Fix for D8-specific /cron/ location regex.
  • Update deploy_8.inc to sync it with improvements in deploy_7.inc
  • Set files paths on D8 install to avoid using system default /tmp if path.temporary is not defined.
  • Nginx: Sync headers configuration in the extended mode.
  • Do not copy CDN aliases to the cloned site --CDN vhost.
  • Detect and update default D8 site name, if needed.
  • #2362703 by joestewart - import_8 ineffective.
  • Sync with 6.x workaround for systems with access to /data/all/cpuinfo instead of /proc/cpuinfo
  • Sync subdirectory support.
  • Force clean URLs for Drupal 8.
  • The /login suffix is no longer supported in Drupal 8 and results with confusing 404 error.
  • Avoid broken install on D8 core where sites/all doesn't exist by default.
  • #2183323 - Remove all remnants of $GLOBALS['conf']
  • Fix for removed drupal_mail() which breaks Drupal 8 head install if used.
  • Restore missing !edit_uri with hardcoded standard URI.
  • Nginx: Drupal 8 with clean urls enabled should use /cron/ URI.
  • Nginx: Sync config templates.
  • Add missing code for subdirectory mode detection and support.
  • Detect if the platform stays the same only when site name changes.
  • Use $new_name instead of $new_uri to avoid confusion.
  • Compare $new_uri with d()->name and not d()->uri in the Site Rename Check.
Back to top

6. Known issues

  • Drupal 8 support is (Chasing HEAD) not complete.
  • The upgrade.sh.txt in provision still had Drush 5.10.0, be sure to change it to 6.5.0 before using that script.
  • The upgrade code in the Debian package could fail on an exsiting /usr/local/bin/drush file, this has been fixed in https://www.drupal.org/node/2460023
Back to top

Older 2.x releases

This section documents all the older releases in the 2.x release cycle.

2.1 release notes

Tagged:

The Aegir team is proud to announce the second release in the stable 2.x release branch!

But first, here's a word from Antoine Beaupré:

This latest release of the Aegir project will be the last one for me as a release manager, as I will be stepping down from the leadership position I have filled in the 7 years of involvement in this amazing project. I will continue to contribute to the project, to a lesser extent. I will remain available, through Koumbit, to provide high-level consulting work for Aegir. We can also now welcome Praxis Labs Coop as a new consulting partner of the Aegir project. Praxis will help to finance ongoing Aegir development by subsidizing part of my salary, in a similar fashion to how Omega8.cc had in the past.

Working with the Aegir project was a huge challenge, both from a technical perspective, but also from a human standpoint, as it is a large and complex project that may seem daunting for new users. But with regular releases and continuous support in the issue queue, I think we have been able to foster a great community of contributors that goes beyond what a single person can do, as Adrian proved when he left the project with the 1.0 release in 2011. Christopher (ergonlogic) and other contributors have shown they are in a good position to take over that leadership role, and will do so from now on.

Now it is my turn to move on, and I am quite proud of what I leave behind. This project allowed me to travel around the world, meet incredible people and learn a lot about hosting and provisioning. It is however time for me to move on. I have been involved with the Drupal community for over 13 years, and things, to put it lightly, have changed. PHP is attempting to become a real programming language, something that I didn't believe could or should happen, and I wish to move on to other paradigms. Python and Haskell are waiting for me around this turn in the road, and even Perl and shell scripting look awesome in comparison to those dreaded PHP years. Besides, since Aegir started, lots of configuration management systems have popped up that we can leverage to host way more than PHP and Drupal: Docker, Chef, Puppet hold lots of promise for those of us who dare to get out of the NIH syndrome. Hopefully, that energy will be reusable in the Aegir project as we head towards Aegir 4!

And so, thank you, Antoine, for all your great contributions as leader of the Aegir project! You have been an inspiration to many of us, and have provided superbly effective technical leadership.

This release ships with support for Apache 2.4, along with updates to Drupal core and ModalframeAPI. A number of bug-fixes are included affecting deployment of Drupal 7 sites, aliases with sub-directory installs, backups, among other things. See below for the full lists of new features and bug fixes. Everyone is encouraged to upgrade.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is at:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. Noone likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Known issues

Being really open about our project, we have never hidden the fact that some things, sometimes, do not work in Aegir. Our issue trackers are public, and we've made it a point of honor not only to document clearly what is wrong in our releases as soon as we find out about it, but also to reroll new releases when we fix it.

That being said, 2.1 still has a number of issues and design flaws. This is the list of all issues marked "major" in the queue right now. Most issues are now likely to be fixed in the 3.x development branch, and unlikely to be backported unless considered critical.

  • hosting-queued doesn't get properly re-enabled on upgrades, see #2114675 for a workaround.
  • previous Debian packages may remove the aegir.conf symlink before being upgraded. this is fixed in 2.0 but will occur (it's inevitable) during upgrades from 1.x releases. details and simple workaround in #2121263
Back to top

4. Features

  • Apache 2.4 is now supported in the 1.x and 2.x branches, see #2153929 and #2155445
  • updated core to Drupal 6.31
  • #2191827 by Jon Pugh: Update modalframe
Back to top

5. Bug fixes

  • #2157785 by helmo: Deploy_7 code lacks functionality from D6 code
  • #2169025 by gboudrias: Fix non-gzipped backups can't be restored
  • #2213387 by Chris Moates: Fix alias handling when using subdirs support
  • Cleanup some file permissions from 755 to 644
  • #2213787 by SocialNicheGuru, helmo: Undefined property: stdClass::$ssl_key_new hosting_ssl.nodeapi.inc:252
  • Fixed reference in comment and cleanup notices
  • #2171075 by helmo: Fix hostmaster-resume command options. (3 months ago)
  • #2189687 Redirect to site-alias not working
Back to top

2.0 release notes

Tagged:

The Aegir team is very pleased to announce the official release of Aegir 2.0.0. This long-awaited release ships with significant stability improvements, Drush 5 and 6 support, subdirectory multisite support, improved nginx support, native views and much, much more! We unfortunately had to drop support for Drupal 5, as Drush 5 and 6 dropped support for this unsupported Drupal release.

This release deprecates the 1.x branch, marking the 1.11 release as the last one of the 1.x branch. All Aegir users are strongly encouraged to upgrade to the 2.0 release. The upgrade has been thoroughly tested and works fairly reliably, except some documented minor issues.

We have a very dynamic community of contrib developers, and various projects built atop Aegir. So if you were waiting for Aegir 2 to be stable, easy to install, production-ready, now is the time. The 2.x branch will be well supported as a lot of shops are running it in production already.

1. Major changes in this release

Since th 1.0 stable release (1.0) in April 2011, we've done an incredible amount of work. The code size nearly doubled as did the development team and user base. We have accomplished a significant number of the release goals we set for 2.0, but not all. Here is a broad breakdown of the most important improvements between the 1.11 and 2.0 releases:

  • Subdirectory multisite support
    • you can now have different sites in example.com/foo and example.com/bar, a great feature if you do not control DNS, as well as for local development!
  • SSL improvements
    • IP allocation improvement: addresses can be changed, added and removed more easily, and are managed from the front-end now.
    • SSL certificate generation now has saner defaults (e.g. 2048bits)
    • better error handling
  • Drush 5 & 6 support
    • includes better support for archive-dump command
    • means we also drop the dependency on drush make 2.3, now included in Drush 5
    • support for Drush 4 has been dropped, the minimum version is now 5.5, but Drush 6 or 5.10+ is recommended.
  • Packaging improvements and changes
    • Nginx support in the Debian package
    • now a "native" debian package
    • package name changed: it is now aegir2, aegir2-provision, etc, to avoid overwriting the previous package - note that aegir 1 and 2 can not be installed in parallel
    • hosting and eldir now split back in their own projects on dripal.org
    • using Drupal.org packaging tools to provide a full tarball for the whole frontend, speeding up installs significantly
  • Nginx improvements:
    • fixed support for nginx 1.3 and newer
    • better defaults for caching
    • SSL and Nginx are now officially supported (not marked as "experimental")
  • New modules:
    • the hosting-queue-runner module is now merged into core as hosting-queued
    • "pack" module, designed as a lightweight replacement to the "cluster" module, now available as an experimental extension
  • Hosting-queued improvements
    • run with a lower priority ("niced")
    • improved portability and reliability of startup script
    • enabled by default in the Debian package
    • improved stability
  • Code refactoring and improvements:
    • now using the Symphony autoloading code
    • fix coding style in a lot of source files
    • improved builtin test suite
  • Frontend improvements:
    • all custom displays ported to Views and VBO
    • nicer frontpage
    • new and improved roles with more useful default permission sets
  • Documentation improvements:

For a more detailed list of new functionalities, bugfixes and API changes, see below.

Some goals of the original 2.0 roadmap have not been accomplished, namely:

  • modular backup, platform and queuing systems - although work has started on Wordpress support, and an overhaul of the Aegir architecture is considered for 4.0, which will affect queuing systems (see below)
  • DNS, PostgreSQL and statistics efforts have mostly stalled
  • clone and migrate optimizations still have to be completed
  • completely automatic upgrades have not been implemented, although the Debian package upgrades are working generally well
  • the release was about 2 months late from the october 31st estimate
Back to top

1.1. 2.x branch maintenance policy

With the 2.0 release, the Aegir project wished to adopt the growing standard of Semantic Versioning. Unfortunately, the tools on Drupal.org do not allow 3-digits version numbers in contrib, something of a blocker to allow us to use that great numbering scheme. So we will stick to our previous scheme for now, but we'll consider a switch to semver for 3.0.0.

No API change will be done in the 2.x branch. All core development will now happen on the 3.x branch, which shifts the focus of development to the port of the frontend to Drupal 7 (almost complete).

Note that the 2.x API has already been frozen for some time, since the first release candidate, to be more precise. Major changes to 2.x will not be committed unless they are first tested in 3.x and merged back. However, we wish the 2.x branch to be relatively short-lived, and it is more likely that major changes will not be backported from 3.x unless absolutely necessary for users needing a Drupal 6 Aegir frontend.

The 1.x branch is now deprecated and the 1.11 release will be the last release of that venerable branch, unless we need another release to fix the upgrade path to the 2.x branch. This is considered very unlikely. Security fixes or critical issues will therefore not be backported to the 1.x branch.

Back to top

1.2. The future

While we're very proud of what we've accomplished in Aegir 2.0, we've also been working in parallel to port Aegir to Drupal 7. Aegir 3.0 has already begun as a fairly straight-forward port. As such, we'll be releasing our first alpha of Aegir 3 shortly. We would like to have a stable Aegir 3.0 release before the release of Drupal 8, to allow for users to transition as Drupal 6 enters its end-of-life phase.

The reason for the change to semantic versioning is that we've been discussing a full re-write of Aegir for some time, and would like to do so with Aegir 4. The changes are likely to be fairly drastic, and so we want to be able to keep moving Aegir 3 forward in the mean time. By moving to Drupal 7, we expect to have bought ourselves 2+ years of breathing room within which to accomplish this re-architecture and the semantic versioning system allows us to integrate major changes in the 3.x branch progressively.

When the Aegir project started (back in 2008), the free software options for systems management software were very limited. As a result, we wrote our own code to do things like deploying code, writing configuration files, starting and stopping services, and so forth. Now, as 2014 begins, there are a wealth of tools that perform these functions (e.g. Puppet and Chef, but also Openshift, Docker, etc), each with their own communities supporting them. We are exploring how we might be able to leverage these tools, rather than maintaining our own partial implementations, that will never likely be as robust as these more specialized projects.

We feel that the time is opportune since Drupal 8 will require significant re-writing of the front-end components. In addition, re-writing the backend so completely will allow us to seriously consider moving to a programming language other than PHP; one that would be better suited to the project's long-term goals, such as Python or Ruby.

Back to top

2. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

For users coming from the 2.0 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Note that you should upgrade to the latest 1.x release (currently: 1.9) before attempting the upgrade to 2.x. This is especially important if you are running a pre-1.0 release (poor you!).

Back to top

2.1. 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://community.aegirproject.org/help

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

Back to top

2.2. Known issues

Being really open about our project, we have never hidden the fact that some things, sometimes, do not work in Aegir. Our issue trackers are public, and we've made it a point of honor not only to document clearly what is wrong in our releases as soon as we find out about it, but also to reroll new releases when we fix it.

That being said, 2.0 still has a number of issues and design flaws. This is the list of all issues marked "major" in the queue right now. Most issues are now likely to be fixed in the 3.x development branch, and unlikely to be backported unless considered critical.

  • hosting-queued doesn't get properly re-enabled on upgrades, see #2114675 for a workaround.
  • Ubuntu saucy has some changes in apache config wich breaks Aegir #2155705
  • previous Debian packages may remove the aegir.conf symlink before being upgraded. this is fixed in 2.0 but will occur (it's inevitable) during upgrade. details and simple workaround in #2121263
Back to top

3. Complete list of changes

Her is the complete list of changes, since the 1.x branch, some of which were already mentioned in previous release notes for alpha/beta/rc releases.

Back to top

3.1. API changes

Those changes are, as usual, more explicitly documented in the upgrade path documentation.

  • hosting-task now needs a --force argument to run a non-queued task
  • the '--force' option also allows running tasks that appear to be running in the queue
  • functions that were deprecated in 1.x are now removed
  • the email and client_email database fields are now removed from client and site node types
  • numerous changes to the IP allocation and SSL management code
  • deprecate hosting_ip_delete_revision(), dupe of hosting_ip_delete() now that revisions are gone (8 weeks ago)
  • remove deprecated DEBUG flag in debian package
  • #1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
  • #1945950: Rename provision_drupal_sync_site_back()
  • #1083366: Make the spokes authoritative for files/ and private/ directories
  • #1812338: Refactor sync back
  • a new control file has been introduced in /etc/nginx/basic_nginx.conf to force the nginx configuration to be the "simpler" one (see #1635596)
  • #1987026: Move generated platform drushrc.php to sites/all/drush
  • Multiple files can be managed in a single context now (see issue #2000038, issue #1784108)
  • #1034520: Cleanup package instances when deleting sites and platforms.
  • #1830220: Drop support for Drupal 5.
  • #1975086: Move log parsing and status updates to seperate functions and call them from a shutdown function.
  • Pass the entity type when we're sync'ing package instances.
  • Save the platform field when creating a package instance record.
  • Move to individual operation callbacks for VBO tasks.
  • #2022849: Record disable and delete backups in the database.
  • #2031491: Rename SSL permission to be more descriptive.
  • Fix node grants so that proper permissions are respected on all Aegir node types.
  • Add 'administer' permissions for platforms and servers, and allow platforms to be viewed.
  • #1283738: Allow other commands to add or alter the directories to be created.
  • remove version pinning in hostmaster, our release process now again needs to modify only one makefile (#2002114)
  • #1986928: Provide 2.x upgrade guidance for services
  • #2099889: More hosting_features checks in _drush_load hooks?
  • #1882708: Unused 'release_id' field in 'hosting_platform'
  • #2012508: hosting_context_name returns '@' if node not found
  • #1283738: Add new hook provision_drupal_create_directories in _provision_drupal_create_directories
  • There is now a registry in the backend of the features enabled in the front-end (in /var/aegir/.drush/drushrc.php) which allows backend components to better determine if they should act
  • If /var/aegir is a symlink, it will be destroyed by the debian package, make sure the Aegir $HOME is properly set to work around that, see issue #2118857
Back to top

3.2. New features

In addition to the "major changes" mentioned above, the following should also be noted.

Back to top

3.3. Bugfixes

This list only shows bug fixes since the last release candidate (RC5), since the list of all bugfixes in Aegir 2 is truly enormous. Please review the individual release notes for more details, if you are curious.

  • Improve the subdir related description in the site add/edit forms, to explain the most important details clearly enough.
  • Do not allow duplicate subdir aliases - use hosting_alias_allow_domain() in hosting_alias_validate_subdir() directly.
  • Update the inline how-to for sites in subdirs.
  • #2020089 by ergonlogic - Allow example.com and example.com/foo domains (Hosting)
  • #2151475 by helmo: Extra comment.
  • #2151371 by helmo: Allow custom platform tasks.
  • security fix: SA-CORE-2013-003, fix files/ protection
  • #1220062 fix mild security issue with login-reset links.
  • fix SSL certificate garbage collection, it was simply not working
  • reformat complex query to be more readable
  • also free SSL certificate when SSL is disabled on a site
  • check only client nodes for duplicates, closes #2123355
  • #2119101: Fix tasks are not sorted properly.
  • don't verify deleted sites, fixes #2119111
  • properly populate the SSL cert / IP association map
  • properly count the aegir hosting aliases, fixes #2118917
  • Fix malformed @defgroup.
  • #2085077 by chertzog | ergonlogic: Fixed Invalid argument supplied for foreach() hosting.ip.inc:39.
  • #2126895 by helmo: Upgrade.sh not compatible with Drush 6.
  • #2020089 by ergonlogic - Allow example.com and example.com/foo domains (improved to fix a few dangerous errors) plus comments.
  • Nginx: Use text/xml mime type for .xml URLs to restore defaults.
  • Fix the check for parent site existence - we should look for drush alias file and not a vhost (which can be dummy subdir vhost).
  • Nginx: Fix aliases in redirects on the fly.
  • Nginx: Convert subdir alias name properly when used as server_name in redirection.
  • #2020089 by ergonlogic - Allow example.com and example.com/foo domains (Apache)
  • Nginx: Redirect to working homepage for subdir based site.
  • #2100181 by ergonlogic - Symlink missing for D6 subdir sites.
  • #2146711 by helmo: PHP 5.3 compatible (Nginx).
  • #2038891 by drastik: add missing --client-email option
  • #2020091 by ergonlogic - Support subdirs with Nginx.
  • fix redirection for non-ssl hosts, issue #2148671 by logaritmisk
  • #2157785 by helmo: Remove unused variables, these get written to the site's settings.php anyway.
  • #2157783 by helmo: Deploy_7 code has an unused old_uri.
  • don't go around destroying apache configs on upgrades or removal
  • get the aegir home directory dynamically
  • rename VARLIB variable to AEGIRHOME for clarity
  • fix drush dependency: we need 5.10 to treat hostmaster as core in drush make
  • Further fixes for strict options checking in Drush 6.
  • #2135999: Fix for strict options checking in Drush 6.
  • Update site_data example extension with new load method.
  • Fix naming of hook in api docs.
  • be more tolerant about the way the alias gets passed from the frontend
  • #2117227 by Ogredude - Missing newline causes syntax errors in vhost.d nginx config when redirects are enabled.
  • Copy all makefiles into Debian package.
  • Conditinally add subdirs/ to the debian package.
  • Fix .deb dependency.
  • #2113463: Fix take hosting_platform_pathauto out of experimental.
  • #1376466 by Dane Powell: Fixed path not generated when copy/paste is used.
  • #1898252 by Dane Powell: Fixed Edit option displayed on existing platforms.
Back to top

3.4. Other issues

  • #1923552: Rename 'Queue runner settings' tab to 'Queue daemon'
  • #1834036: Add 'hosting platform pathauto' to the .gitignore
  • #1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
  • #1979496: Update upgrade.sh.txt for Drush 5
  • #1974752: Document old_uri option for provision-deploy
Back to top

2.2 release notes

2.2 was an abortive release, due to missing updates to contrib modules. Use 2.3 instead.

See: http://community.aegirproject.org/2.3

2.3 release notes

Tagged:

The Aegir team is proud to announce the third release in the stable 2.x release branch!

This maintenance release ships with a huge number of bug fixes since our last stable release, almost a whole year ago. There are also some security improvements for nginx users. See below for the full list of bug fixes. Everyone is encouraged to upgrade.

Also, worth noting is the simultaneous release of our first beta for Aegir 3. Debian packages are now being provided for Aegir 3, so trying it out is easier than ever!

N.B. The 2.2 release was invalid, as the contrib modules included in the drupal-org.make had not been updated.

1. Security improvements for nginx

Previously, Aegir stored SSL cipher and protocol settings per site in Nginx virtualhost configuration files. This included the enabling of SSLv3, which is vulnerable to POODLE attacks [1].

Because these settings were stored via templates, permanently removing SSLv3 support on Aegir-based Nginx SSL environments was not possible. These settings have now been removed from the templates that generate Nginx virtualhost files under Aegir. If you wish to either re-enable SSLv3, or otherwise alter SSL cipher and protocol settings in Nginx, we recommend you do so in the http {} context (e.g, in /etc/nginx/nginx.conf), which are applied globally and are never manipulated by Aegir.

Sites that were running on Nginx and had SSL enabled, should be re-verified to remove those settings.

Apache users (including those using SSL) were not affected.

[1] http://en.wikipedia.org/wiki/POODLE

Back to top

2. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is at:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade.

N.B. Issue #2146977: Broken backward compatibility with IP based vhosts may affect those upgrading from 1.x. It appears that running 'verify' tasks on all sites should resolve the issue.

Back to top

3. 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://community.aegirproject.org/help

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

Back to top

4. Known issues

Being really open about our project, we have never hidden the fact that some things, sometimes, do not work in Aegir. Our issue trackers are public, and we've made it a point of honor not only to document clearly what is wrong in our releases as soon as we find out about it, but also to reroll new releases when we fix it.

That being said, 2.2 still has a number of issues and design flaws. This is the list of all issues marked "major" in the queue right now. Most issues are now likely to be fixed in the 3.x development branch, and unlikely to be backported unless considered critical.

As mentioned in the previous section, Issue #2146977: Broken backward compatibility with IP based vhosts is still listed as a 'critical' issue against the 2.x branch. However, it should only affect those upgrading from 1.x, and has a fairly simple work-around. If you come across this behaviour during your upgrade, please post a comment to the issue, so we can confirm that it still exists.

Back to top

5. Features

#2267057: Pre-upgrade add ctools to 6.x-2.x

Back to top

6. Bug fixes

Changes to hosting since 6.x-2.1:

  • Make it clear that subdomain (foo) and subdirectory name (foo) must be identical.
  • #2333911 - Restore the pre-views order of tasks in the queue blocks/lists.
  • #2313327 by helmo | tvl: Fixed Unknown options for provision-verify.
  • #2163525 by helmo | daften: Fixed Aegir doesn't delete old alias on migration of site.

Changes to provision since 6.x-2.1:

  • #2457359: Stop overriding Nginx SSL settings
  • Nginx: Stop the POST flood to /autodiscover/autodiscover.xml generated by MS Office/Outlook
  • Nginx: Use dummy db fastcgi_param placeholders if any of them is empty
  • #2350695 by omega8cc, helmo: Profile is registered twice, also as a module, which causes warning
  • Nginx: Remove webform keyword from regex locations - fixes #599
  • Nginx: Sync configuration improvements.
  • Fix for custom cpuinfo logic.
  • #2421543 by notzach: Changing how Apache ServerAliases are defined
  • Nginx: Use safe fallback for mysteriously empty $db_port
  • Nginx: Use reliable source for db_port to write in the vhost
  • #2276557 by zxaos, bgm: allow aegir2-provision package to accept mariadb or mysql
  • Nginx: Fix for D8-specific /cron/ location caching (extended mode only).
  • Nginx: Fix for D8-specific /cron/ location regex.
  • Nginx: Drupal 8 with clean urls enabled should use /cron/ URI.
  • Nginx: Sync config templates.
  • Detect if the platform stays the same only when site name changes.
  • Standardize inline comments.
  • #2372653 by helmo: Add --no-autocommit when dumping MySQL tables
  • Use $new_name instead of $new_uri to avoid confusion.
  • Compare $new_uri with d()->name and not d()->uri in the Site Rename Check.
  • Nginx: Helper locations to avoid 404 on legacy images paths (subdir only)
  • Nginx: Fix spacing
  • Nginx: Add missing variables in subdirectory config template.
  • don't allow d() to run before drush is fully initialized
  • Nginx: Add the fix for known problem with files/imagecache in legacy D6 sites (again).
  • Nginx: Fail early if any required db credentials are empty, to never create broken vhost.
  • Nginx: Block semalt botnet (extended boa mode only)
  • #2358977 by mrP - [nginx] Aegir redirection to non-install url leads to sites/$server_name/files 404 errors (sub-dir config sync)
  • #2373923 by griz - https redirect problem with Nginx (fix tested)
  • Nginx: Avoid redirect loops (really fixed).
  • Nginx: Avoid redirect loops (fixed).
  • Nginx: Avoid redirect loops.
  • #2358977 by mrP - [nginx] Aegir redirection to non-install url leads to sites/$server_name/files 404 errors.
  • Nginx: Simplify imagecache/styles support.
  • Nginx: Remember real site name in $main_site_name and MAIN_SITE_NAME.
  • Sync new lines.
  • Nginx: proper sync with Apache redirects.
  • Revert "Issue #2373923 by griz - https redirect problem with Nginx"
  • #2373923 by griz - https redirect problem with Nginx
  • Merge remote-tracking branch 'origin/6.x-2.x-backports' into 6.x-2.x
  • #2163979 - Check if field_info_field_map() is available to not break support for old D7 versions.
  • Make sure that db_port is never empty and defaults to 3306.
  • #2266997 by helmo, cweagans: Added Do not automatically enable update module when installing a site.
  • Nginx: Update vhosts templates to match BOA improvements #unforkboa
  • Nginx: Sanitize aliases in vhost_disabled.tpl.php to avoid: 'nginx: [warn] server name "foo.com/bar" has suspicious symbols'
  • Fix spacing in config lines.
  • Nginx: Update config includes to match optional BOA features improvements #unforkboa
  • Manage extra GRANTS to allow SQL remote access via SSH tunneling which depends on '127.0.0.1' and will not work with GRANTS for 'localhost'.
  • Add support for file generated from /proc/cpuinfo on system with no access to /proc #unforkboa
  • Ignore paths from OS X
  • Backport provision_hosting_feature_enabled (2)
  • Backport provision_hosting_feature_enabled()
  • Fix typo.
  • Shorten and simplify the subdirs checks code.
  • Remove legacy subdir code and update checks.
  • Remove whitespace.
  • Use is_readable() instead of file_exists() when checking alias existence.
  • Use is_dir() instead of file_exists() when checking directory existence.
  • Use is_readable() check instead of insufficient file_exists() for config includes.
  • Remove redundant file_exists() if is_readable() is also used.
  • Add little debugging markers.
  • Use strict checks: is_file() and/or is_link() instead of file_exists() before attempting unlink()
  • Fix for mysterious warning "Could not create directory ." on Hostmaster site Verify.
  • Nginx: Fix typo in vhosts templates.
  • #2330781 - Use Drush native dt() wrapper instead of not always available t()
  • #2329131 by dagomar: Fixed Uninstalled block module causes errors.
  • Allow usage with Drush7, now that *.drush.load.inc's aren't being included.
  • #2177315 by pwatzeels: Fixed Group permissions on private/temp folder not correct on remote server.
  • #2296089 by ergonlogic, cosmicdreams: Fixed Installer can detect incorrect default web group.
  • #2169287 by cableman0408: Fixed Setting user name twice (fails non-default installation profile).
  • #2275467 by kristofferwiklund: Fixed incorrect variable in Debian postinstall script for Apache 2.4
  • Stop false-positive warnings when SSL uses a wildcard.
  • #2259461 by Liam McDermott - Remove too aggressive limit_conn directive in the Nginx config templates.
  • Revert "change version information for release 2.1"
  • #1168758 by helmo | acrollet: Optionally add --include-vcs argument when using drush rsync to sync remote platform.
  • Extend provision_drupal_fetch_site with a parameter to specify site to fetch.
Back to top

2.0 alphas, betas & release candidates

Tagged:

This section documents all the release candidates towards the 2.0 release.

2.0-rc5 release notes

The Aegir team is is pleased to announce the fifth release candidate for the upcoming Aegir 2.0 release!

This release ships a ton of bugfixes we have found in RC4. We also finalised subdirectory support which, while it still has some issues, is now actually working correctly, even on multiple servers. The IP allocation code for SSL on multiple servers was also fixed, making this probably the most solid multi-server Aegir release ever. We also did some API cleanups that seemed necessary before the final 2.0 release.

Finally, we should also mentionned that the install process was significantly sped up thanks to the use of Drupal.org distributions to ship a single tarball for the hostmaster platform instead of using a makefile to build it from its parts all the times. During out tests, the platform make step went from 60 seconds to 1.5 seconds, an amazing improvement!

Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes, with 2.x-specific instructions outlined in bold.

It is still imperative that you read the the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. You should be able to upgrade to 2.x releases from any release in the 1.x series, but it's better to upgrade to the latest 1.x release first.

Known issues

Those are the critical bugs that were found in this release that you may encounter and should watch out for.

  • There was a problem in the Debian package, the original uploads were missing some critical files (subdir support and some makefiles). This was fixed in an intermediate package named 2.0~rc5.1.
  • If /var/aegir is a symlink, it will be destroyed, see issue #2118857 for a workaround.
  • hosting-queued doesn't get properly re-enabled on upgrades, see #2114675 for a workaround.
  • Some upgrades fail with mysterious redirection failures, see #2118061 for details.
  • Some upgrades may loop over one of the update_N() functions, see #2118917 for details and workaround.
  • Upgrading through Debian packages removes the aegir.conf Apache configuration file, dropping all sites, during the upgrade, see #2121263.
  • Ubuntu sausy has some changes in apache config wich breaks Aegir #2155705

Detailed list of changes

API CHANGES

NEW FEATURES

BUG FIXES

2.0-rc4 release notes

An error in the manual portion of our release process resulted in the incorrect version of the code-base being built. See the release notes for 2.0-rc3 for relevant changes since 2.0-rc2.

Known bugs

In addition to those listed in the release notes for 2.0-rc3, note that some people have experienced problems with downloading a patch in the main Aegir makefile. This is most likely due to problems with drupal.org's SSL certificate. If you are experiencing such an issue, there is a simple work-around: edit the aegir.make file in the provision/ directory to make the path use http:// instead of https://.

For a Debian-based system (including Ubuntu), this would look something like:

$ sudo vi /usr/bin/drush/commands/provision/aegir.make

For 'manual' installs on other OS's, it would probably be:

$ sudo vi /var/aegir/provision/aegir.make

Change the line:

projects[drupal][patch][] = "https://drupal.org/files/common.inc_6.28.patch"

to read:

projects[drupal][patch][] = "http://drupal.org/files/common.inc_6.28.patch"

Then re-run the install. On Debian/Ubuntu machines:

$ sudo apt-get install aegir2

On manually installed systems (CentOS, etc.) as the aegir user:

$ drush hostmaster-install

Detailed list of changes

API CHANGES

None.

NEW FEATURES

None.

BUG FIXES

  • Fixed makefiles to point to proper versions of projects.

2.0-rc3 release notes

Tagged:

The Aegir team is pleased to announce the third release candidate for the upcoming Aegir 2.0 release.

This release mainly fixes a couple critical bugs in 2.0-rc2 that were causing problems when sites were being cloned or renamed. We've added a couple small features, such as additional options during hostmaster-install, and allowing the redirect to the Welcome page to be turned off. Also, we've made a small addition to the API, in that there is now a hook available (hook_provision_drupal_create_directories_alter()) to allow altering the directories created when a site installed.

In order to better support PHP 5.4, we have added a patch to Drupal core to suppress E_STRICT warnings. These were harmless, but annoying. They were caused by a changed in PHP error-reporting in PHP 5.4, and the Views module's maintainers' desire to remain backward compatible with PHP 4. For more details, see: #2060727: Patch Drupal core to suppress E_STRICT warnings on PHP5.4.

A number of pending issues require a new stable release of Drush (5.10), so we will work with the maintainers to help get a new release out.

Known issues

Our release process is still done by hand instead of being more automated because we can't use our aegir distribution as core (issue #1991764).

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs a number of issues to be fixed before completion, see #2046167 for details. Note that this will not block a stable release, since this feature is 'experimental', and additional re-factoring can occur during the stable release cycle.

Detailed list of changes

API CHANGES

  • #1283738 by halcyonCorsair, cweagans: Allow other commands to add or alter the directories to be created.

NEW FEATURES

  • #2069387 by cweagans, mstenta: Support nonstandard ports on hostmaster-install command.
  • #2067617: Allow hostmaster-install to accept '--working-copy' option.
  • Allow the redirect to the welcome page to be turned off.

BUG FIXES

  • Add E_STRICT patch to test openatrium makefile so tests will pass on PHP 5.4.
  • #2067603: Fix original and cloned site pointing to the same database.
  • #2048653: Ensure mysql is secure before proceeding with hostmaster install.
  • #2060727: Patch Drupal core to suppress E_STRICT warnings on PHP5.4.
  • #2038279: Warn of invalid account email on site install.
  • #2055949: Fix migrate drops wrong database when domain name changes.
  • #2074681 by cweagans, mstenta: Fixed ports are hardcoded in hostmaster.profile.
  • Use custom functions for block visibility.
  • #1940378: Fix PHP 5.4 warning by initializing an object variable prior to assigning properties.
  • #2050881: Call drush.php via php, since it isn't executable when installed via PEAR.
  • Enable platform site-list block, since it had to be renamed.

2.0-rc2 release notes

Tagged:

The Aegir team is pleased to announce the second release candidate for the upcoming Aegir 2.0 release.

This release mainly fixes our project makefile that, due to an error in our build process, did not pull in the latest code. As a result, installing 2.0-rc1 actually installed a 2.0-beta2 codebase. While changes between 2.0-rc1 and 2.0-rc2 have otherwise been minimal, we invite you to explore all the new features and bugfixes in 2.0-rc1.

Note that we have taken this opportunity to update our external dependencies, as well.

Known issues

Our release process is still done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764).

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs those issues to be fixed before completion, see #2046167 for details.

Issue #2046783: Task dialogs won't open after clearing the cache was the result of updating our dependencies. Refreshing the page is usually sufficient to make modal dialogs work again. It looks like this was probably specific to the development environment, as we can no longer reproduce it.

A critical bug was discovered: Issue #2055949: Migrate drops wrong database when domain name changes. It has been fixed in 6.x-2.x, and a patch for 2.0-rc2 is available.

Detailed list of changes

API CHANGES

  • Update external dependencies.

NEW FEATURES

none

BUG FIXES

  • Add dependency on jquery_update, so we can use the more recent version of modal_dialog.
  • Enable login and nav blocks explicitly.
  • treat symlinks as existing, fixes #2046249

2.0-rc1 release notes

Tagged:

The Aegir team is pleased to announce the first release candidate for the upcoming Aegir 2.0 release.

This release mainly targets a few critical bugs that were found in the second beta, mostly related to ongoing Views, Drush integration and access control. We also introduce a number of new features and finally drop support for provisioning Drupal 5 sites completely (for real this time!). Along the way, we did quite a bit of API cleanup.

While we are in feature freeze, we have continued to add some UI improvements, since they don't affect the API. We've added some long-standing UI enhancements, and fixed a number of bugs in the views integration and other usability problems, as well as overhauling our access control. Significant improvements to the package-management system have also been introduced.

Our only remaining critical bugs are basically waiting on a new release of Drush, upgrade testing on Nginx and some contrib upgrade guidance documentation. If no other critical bugs are discovered during the time it takes us to fix these, we should move on to a full release of Aegir 2.0!

Known issues

Our release process is still done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764).

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs those issues to be fixed before completion, see #2046167 for details.

Detailed list of changes

API CHANGES

  • #1034520: Cleanup package instances when deleting sites and platforms.
  • #1830220: Drop support for Drupal 5.
  • #1975086: Move log parsing and status updates to seperate functions and call them from a shutdown function.
  • Pass the entity type when we're sync'ing package instances.
  • Save the platform field when creating a package instance record.
  • Move to individual operation callbacks for VBO tasks.
  • #2022849: Record disable and delete backups in the database.
  • #2031491: Rename SSL permission to be more descriptive.
  • Clean up hosting_node_grants().
  • Add 'administer' permissions for platforms and servers, and allow platforms to be viewed.

NEW FEATURES

  • #905326 by ergonlogic, crea: Improve file path changes.
  • #1201174: Make UID1 username configurable.
  • #1345118: Make platform access control an autocomplete form.
  • #1515416 by ergonlogic, helmo, Deciphered: Replace listing of sites and platforms using a package with a view.
  • #1975086: Add 'update status' button to tasks.
  • #2005310: Add VBO operations to platforms view.
  • #2006074 by Deciphered: Enable backups via VBO.
  • #2025787 by omega8cc, ergonlogic, anarcat: Open site goto link in a new window/tab.
  • #2022813 by Deciphered: Expose backups to Views.
  • #2027269: Update a task's status after all Drush operations are complete.
  • #2031491: Review and update permissions for all roles.
  • #2031765: Clean up VBO operations with Action Permissions.
  • #2035873: Show package 'popularity' on platform package view
  • #2036283: Make Aegir aware of site-specific packages.
  • #2036793 Ignore hidden modules and profiles.
  • #2037045 by helmo, ergonlogic: Change some log statuses to better match Drush's log styling.
  • #2037965: Clean up hosting-pause.
  • #2038279 by ergonlogic, Jon Pugh: Validate email during site install.
  • Display all validation errors when adding a client, and limit to 20 suggestions.
  • Flag rollbacks as warnings in our task logs.
  • Handle package page views separately for sites and platforms.
  • Update default hosting_site views to use new access plugin for blocks, and add a couple more displays for non admin listings.
  • Add Views access plugin for hosting_site and hosting_package.
  • Add views handler to filter packages by status.

BUG FIXES

  • #1238618: Fix client form validation.
  • #1263264 by ergonlogic, recidive, anarcat: Specify a type when getting a package, to avoid collisions.
  • #1647830 by sambonner: Fix Incorrect ownership of directories under sites/example.com/private/files/.
  • #1861898 by ergonlogic, Jon Pugh: Don't hardcode the types of entities to which we can attach tasks.
  • #1975086 by helmo | anarcat: Fixed updating a task when there is none.
  • #2025355: view platform' permission broken
  • #2026417: Disambiguate site operations.
  • #2031491: Fix roles.
  • #2031747: Fix Views block placement and visibility.
  • #2038891: Add 'client_email' option to 'provision-install-backend'.
  • #2038891: Switch from '--invoke' to '--strict=0' for backend calls.
  • #2040285 debian: properly detect webserver, again
  • #2044251 drush command '@none provision-save' could not be found
  • #2045907: Remove extra tabs from deleted platforms.
  • Fix php 5.4 issue
  • Add missing unicode include for UID1 name validation.
  • Fix update hook name.
  • Only register shutdown function to update task status in the context of a front-end task.
  • Don't display package block on profiles.
  • Only show link to add clients on site form to those with proper permissions.
  • Override hook_access functions for node_grants when hosting_client is enabled.
  • Register node type in hosting_task's Hosting feature.
  • Clean up Views exposed forms.
  • Fix Views block placement and visibility.
  • Only display client sites block on the 'view' tab.

2.0-beta2 release notes

Tagged:

The Aegir team is pleased to announce the second stabilization (beta) release of the Aegir 2.x branch.

This release mainly targets a few critical bugs that were found in the first beta, namely IP allocation on non-SSL and non-cluster sites which was completely broken and bugs the Debian package. We also introduce a few new features and finally drop support for provisionning Drupal 5 sites completely.

While we are in feature freeze, we have continued to add some UI improvements, since they don't affect the API. We've added some long-standing UI enhancements, and fixed a number of bugs in the views integration and other usability problems.

We are down to only one active critical bug. If no other critical bugs are discovered during the time it takes us to fix it, we should move on to our first release candidate!

Known issues

Our release process is still done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764)

Issue #1931000: Missing drush backend output in frontend log has been fixed, but may require a patch to Drush for the use of hosting-queued.

Subdirectory support is still very preliminary and needs those issues to be fixed before completion:

  • Nginx support missing (issue #2020091)
  • If example.com/foo is created, the example.com virtual will be overwritten and the site inaccessible under that domain (issue #2020089)
  • Multi-server support is untested (issue #2020079)
  • Code needs to be refactored to the new 2.x API (issue #2020075)

The move to Views has highlighted some additional issues:

Fixing #2027269: warnings and errors in front-end pre- and post- hooks are ignored for task status required a new Drush commandfile, and thus a 'drush cc drush' if upgrade between an alpha/beta release and HEAD.

The debian package still doesn't properly configure the webserver, a patch has been committed and a workaround is available in issue #2040285.

New features

Bug fixes

2.0-beta1 release notes

Tagged:

The Aegir team is pleased to announce the first stabilization (beta) release of the Aegir 2.x branch, after nearly 3 weeks of development since our second alpha release. While we had expected an additional alpha release prior to the beta cycle, development on outstanding features went smoother than foreseen. We've added some significant features, and fixed a couple bugs and (again) made some important improvements to our API.

This release marks our feature freeze. The intention is to limit any further changes to only critical and major bug fixes. However, exceptions may be granted on a case by case basis. Our development efforts will now move to tackling all release critical bugs. Once all of these are fixed, we'll move on to our release candidate (RC) phase. That said, we expect this release to be sufficiently stable that we intend to run it in production at Koumbit soon.

Release overview

This release introduces a major new feature into Aegir core: support for installing sites in subdirectories (example.com/foo, example.com/bar, etc.). This has been our number one feature request from higher education institutions, and so we hope that this will enable greater adoption within that sector. While categorized as an "experimental" feature, we feel our approach is sufficiently strong that we're considering merging this into our core site functionality.

Additional new features include a nice homepage, fixes to SSL support and IP allocation on clusters, and we've added a couple new roles.

We've also tackled a number of bugs, especially in the Debian package, which now supports installing Aegir on Nginx servers. We've also fixed some issues introduced with the new views code, and improved nginx support.

The project's Debian repo now includes Drush 5.9, and we have migrated the 'aegir2' packages to the Testing repository.

Known issues

  • the debian package shows a lot of garbage when installing from scratch, which is almost harmless except that we don't see the login URL, use drush @hostmaster uli to get a new one, fixed in issue #2002076
  • SSL support was severely broken for single servers and could lead to loss of the SSL certificate copies when a non-SSL site is installed. See commits f0980e0..9b86038 in Provision for fixes. (fixed in issue #2023621)
  • the Debian package is severely broken - in most configuration (e.g. clean installs but not upgrade) the install will just fail with a permission denied. See commits d4efa37 and 56d1718 for fixes.

These are related to drush:

  • some warnings and errors may not show up in Aegir's task logs, making it believe tasks succeeded when the actually failed. this affects only hosting-queued. (issue #1931000 / issue #1982502)
  • our release process is now done by hand instead of automated because we can't use our aegir distribution as core (issue #1991764)

Subdirectory support is still very preliminary and needs those issues to be fixed before completion:

  • Nginx support missing (issue #2020091)
  • If example.com/foo is created, the example.com virtual will be overwritten and the site inaccessible under that domain (issue #2020089)
  • Multi-server support is untested (issue #2020079)
  • Code needs to be refactored to the new 2.x API (issue #2020075)

API changes

New features

  • Support for installing in subdirectories (issue #705026)
  • Proper homepage on startup so non-logged-in users don't see an error page, and new users have basic instructions (issue #1793740)
  • SSL support for clusters should now work properly (issue #2000964)
  • New roles added: 'aegir platform manager', 'aegir administrator' (issue #1403208)
  • Convert list of platforms to use views (Issue #1876350)

Bugfixes

  • Debian package support for nginx was severely broken issue #2001142
  • the views bulk operations version shipped with alpha2 had security issues, see issue #2001964
  • an update hook was incorrectly named, and has since been fixed. The updates should not be destructive, but may output errors.
  • Placement of a number of our new Views-based blocks was omitted from the install profile, and so won't appear on a fresh install. These can be manually placed on the blocks page.
  • fix warning "Invalid argument supplied for foreach()" (issue #2005698)
  • fix "Unknown options for provision-save" error (issue #1972286)
  • removed hardcoded checks for IP addresses in settings.php that belong to core (issue #2013683)
  • Views filter for status does not tell what to filter for (issue #1997088)
  • nginx cloaks database credentials properly now
  • configure nginx to properly talk to the default php-fpm configuration in Debian (issue #1635622)
  • lots of fixes for the Debian package, including

2.0-alpha2 release notes

The Aegir team is pleased to announce the second preview (alpha) release of the Aegir 2.x branch, after nearly 3 months of development since our first alpha release. We've squashed a number of tenacious bugs, added some nifty features, and made some important improvements to our API. We expect at least one more alpha release before we call a feature-freeze, and begin out stabilizing and cleanup (beta) release cycle.

During this release cycle, we also began work on Aegir 3, a more-or-less straight port of Aegir 2 to Drupal 7. We continue to sync changes in 2.x to our 3.x branch, and look forward to continuing the port (and beginning to add new features) as soon as we've released our first stable 2.x release.

Our next alpha release will target getting sub-site support (example.com/site1, example.com/site2, etc.) into Aegir core as an experimental feature. This has been our number one feature request from higher education institutions, and so we intend to incorporate it into Aegir 2, in order to enable greater adoption within that sector. We have a fairly detailed implementation plan, and so feel confident that we can incorporate this major feature, in fairly short order.

Release overview

This release features improvements to the IP management mechanisms that were broken in the last alpha1 release. We now manage IP addresses individually, and check if an IP is in use before allowing it to be deleted.

We also finally leave the files alone on spokes in the multi-server model, a long-standing bug in the 1.x series that led to data loss. A lot of work was done to standardize the Nginx configuration to allow for simpler, yet optional, configurations that leave the admin in charge of choosing the optimisation methods.

Also, we've moved Hosting and Eldir back to their own projects, and are now included via our makefiles. This simplifies building custom install profiles, though it complicates our release process somewhat. We've also added a drupal-org.make that will eventually allow proper distribution bundling of Aegir.

Finally, we've moved to using Views and View Bulk Operations for our lists of sites, platforms and packages. While there remain some rough edges, this will allow much easier customization of our principal UIs. It has also significantly reduced the custom code we have to maintain, in favour of exported Views, which simplifies maintenance.

Known issues

  • the Debian package support for nginx is severely broken #2001142
  • the views bulk operations version shipped with alpha2 has security issues, see #2001964
  • the debian package shows a lot of garbage when installing from scratch, which is almost harmless except that we don't see the login URL, use drush @hostmaster uli to get a new one, fixed in #2002076
  • an update hook was incorrectly named, and has since been fixed. This may cause the hook to be run again, if the site is upgraded to a newer version. The updates should not be destructive, but may output errors.
  • Placement of a number of our new Views-based blocks was omitted from the install profile, and so won't appear on a fresh install. These can be manually placed on the blocks page.

API changes

  • deprecate hosting_ip_delete_revision(), dupe of hosting_ip_delete() now that revisions are gone (8 weeks ago)
  • allow running tasks that appear to be running with --force
  • remove deprecated DEBUG flag in debian package
  • #1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
  • #1945950: Rename provision_drupal_sync_site_back()
  • #1083366: Make the spokes authoritative for files/ and private/ directories
  • #1812338: Refactor sync back
  • a new control file has been introduced in /etc/nginx/basic_nginx.conf to force the nginx configuration to be the "simpler" one (see #1635596: nginx: do not decide the policy for users)
  • #1987026: Move generated platform drushrc.php to sites/all/drush

New features

  • #1929372: Flag tasks with logged warnings
  • #1515416: On a package page, show table listing sites and platforms using the package
  • #1853620: Add db_name to site summary
  • #1681904: Ability to configure a url to redirect to in site configuration.
  • #1968226: manage each IP individually on the server level - manage IPs individually
  • add uninstall command
  • Nginx Security: BEAST attack protection and fix for PCI compliance.
  • #1980136: Allow setting default profile from the front-end.
  • #588728: Replace custom lists with Views and VBO for sites, platforms and packages.

Bugfixes

  • #1930670: Duplicate entry 0 for key PRIMARY in hosting_ip_addresses when installing / upgrading
  • #1907028: user warning: Table 'XXX.hosting_ip_addresses' doesn't exist
  • #1961920: nginx: [emerg] invalid number of arguments in "limit_conn_zone" directive in /etc/nginx/conf.d/aegir.conf
  • #1923490: Incorrect error message in aegir-provision2.preinst
  • #1901508: "gzip --rsyncable" is invalid on OS X
  • #1678528: Database deleted on edge cases
  • #1930740: provision-delete leaves a drushrc.php lying around
  • Nginx: Do not override Nginx name with fake Apache name.
  • #1990370: Enable Hosting feature dependencies.

Other

  • #1923552: Rename 'Queue runner settings' tab to 'Queue daemon'
  • #1834036: Add 'hosting platform pathauto' to the .gitignore
  • #1785624: Some Drupal API changes in D7 (and D8) are not used/respected properly
  • #1979496: Update upgrade.sh.txt for Drush 5
  • #1974752: Document old_uri option for provision-deploy

2.0-alpha1 release notes

The Aegir team is pleased to announce the first preview release (alpha) of the Aegir 2.x branch, after almost 2 years of development. We have been pretty busy with the maintenance of the 1.x branch, so development has been sometimes intermittent, but it is not over yet!

This release is only a first of a series of alpha releases that are tailored to make upcoming changes available to a wider audience than people ready to install from git, but also to make features more widely available and tested. More alpha releases will be published on a more regular basis in the weeks to come as more features from the new provisional roadmap are implemented. We are still considering the following:

We have set the following priorities:

  1. subsite support (#705026) - now that mig5 did most of the work ;)
  2. nginx cleanup (#1635596, #1635622, #1622846, #1635586, #1608910) and Nginx Debian package (#1348560)
  3. files/ sync settled (#1083366)
  4. SSL code cleanup (#941870, see also this report) - done! Now onto testing and fixing the actual bugs linked from #941870

We would like to get those in 2.x, but since no one has really started significant work on those, we are more likely to simply postpone those to 3.x at this point.

  1. standard archive support (#1138882, original roadmap description)
  2. intersite security (the infamous #762138)
  3. more intelligence in spokes (original roadmap description)

Also, since every single attempt at providing a proper timeline for the final 2.0 release has failed miserably, we'll just stop trying our luck and just give up on a formal timeline. Instead, we'll just do the freaking work. :) Also remember that the port to Drupal 7 has been postponed to Aegir 3. Aegir 1 and 2 both support provisionning Drupal 7 sites, but the frontend is running Drupal 6. We are aiming for a "straight port" (no rewrite) of the frontend for Aegir 3.

1. Major changes

This first alpha already packs a lot of changes. Those release notes detail the changes since the 2.x branch was first created, all the way back two years ago, when 1.0 was released. Of course, we are not detailing all the changes made in the 1.x series that are all part of the 2.x, but only the changes specific to the 2.x release.

  • SSL improvements:

  • Drush 5 support

    • includes better support for archive-dump command
    • means we also drop the dependency on drush make 2.3, now included in Drush 5
    • support for Drush 4 has been dropped, the minimum version is now 5.5

  • Debian package improvements and changes

    • Nginx support in the Debian package
    • now a "native" debian package
    • package name changed: it is now aegir2, aegir-provision2, etc, to avoid overwriting the previous package - note that aegir 1 and 2 can not be installed in parallel
  • Nginx improvements:
    • fixed support for nginx 1.3 and newer
    • better defaults for caching
    • SSL and Nginx are now officially supported (not marked as "experimental")
  • New modules:
    • the hosting-queue-runner module is now merged into core as hosting-queued
    • "pack" module, designed as a lightweight replacement to the "cluster" module, now available as an experimental extension
  • Hosting-queued improvements
    • run with a lower priority ("niced")
    • improved portability and reliability of startup script
    • enabled by default in the Debian package
  • Code refactoring and improvements:
    • now using the Symphony autoloading code
    • fix coding style in a lot of source files
    • improved builtin test suite
    • eldir is split in its own module again, allowing for porting it more easily to Drupal 7

A more detailed log of bugfixes and improvements is available below.

Back to top

2. Major API changes

Those changes are, as usual, more explicitly documented in the upgrade path documentation.

  • hosting-task now needs a --force argument to run a non-queued task
  • functions that were deprecated in 1.x are now removed
  • the email and client_email database fields are now removed from client and site node types
  • numerous changes to the IP allocation and SSL management code

Please note that the 2.x API is still not considered stable and may change without warning until 2.x is fully stabilized, see our release process for more information.

Back to top

3. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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

Note that you should upgrade to the latest 1.x release (currently: 1.9) before attempting the upgrade to 2.x. This is especially important if you are running a pre-1.0 release (poor you!).

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.

Back to top

4. 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://community.aegirproject.org/help

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

Back to top

5. Features and improvements

In addition to the "major changes" mentioned above, the following should also be noted.

Back to top

6. Bugfixes

This is a non-exhaustive list.

Back to top

7. Known issues

The Debian packages were not uploaded correctly on the release day, and have been unblocked only on 2013-12-12 14:45 (UTC-5).

Back to top

Older 1.x releases

Tagged:

This section documents all the older releases in the 1.x release cycle.

1.10 release notes

Tagged:

The Aegir team is proud to announce the tenth release in the stable 1.x release branch! This release ships a moderately critical security fix (see the Security fixes section below) and a number of bugfixes that have accumulated in the issue queue since the 1.9 release. Everyone is encouraged to upgrade.

We also want to announce that ergonlogic and helmo have joined the list of core maintainers supporting the core development of the Aegir project. Along with the existing commitments of the Aegir core maintainer team, Aegir is well assured of continuous development and long term maintenance.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Known issues

Upgrades may fail if the SSL certificates are actually symlinks to files not readable by Aegir, a rare but legitimate use-case. A fix is available in git, see #2046249 for more information.

Aegir 1.x depends on Drush 4.5 or 4.6, which are available only in Debian squeeze backports (old stable!), which may make fresh installs or careless upgrades impossible. To workaround this issue, install the Drush package directly from backports:

wget http://backports.debian.org/debian-backports/pool/main/d/drush/drush_4.5...
dpkg -i drush_4.5-2~bpo60+1_all.deb

See this page for other mirrors.

Because of a little fumble in the 2.0-rc2 release process documentation, a development build of Aegir 1.x has overwritten the 1.10 official release in the stable repository. Since that development build only has the fix for #2046249, we haven't restored the previous build and thefore the version number of the Debian package is 1.10+246.efcd0a3 instead of 1.10. However, this also means that the hostmaster platform directory will be named hostmaster-1.x instead of hostmaster-1.10, which will make upgrades to other development releases require manual creation of the platform.

Back to top

4. Features

  • #1781832 by Steven Jones: Added hosting_available_tasks() should invoke alter.
  • #1760962 by Jon Pugh: Added Allow any hosting task to flag itself for needing a provision-save.
Back to top

5. Security fixes

  • Fix access control to sites.

See also the security advisory (SA-CONTRIB-2013-059) for more information.

Back to top

6. Bug fixes

  • #1990370 by ergonlogic: Enable Hosting feature dependencies.
  • #1435098 by Steven Jones: Fixed Client name validate sometimes gives erroneous results.
  • #1585820 by Steven Jones: Fixed Can't disable the 'client" feature.
  • #1573162 by mig5, Steven Jones: Fixed Drush hosting_task_()%task_rollback() invocations are never executed.
  • #1513678 by Jon Pugh, fastangel: Fixed Hooks based on TASK_NAME should handle task names with dashes in them.
  • #913228 by Steven Jones: Fixed Unresponsive submit button in platform migration form.
  • #1441970 by Steven Jones: Fixed Client Block assigned by default to non-existing region.
  • #1441970 by jlscott: Fixed Client Block assigned by default to non-existing region.
  • #1597648 by jlscott: Fixed Hosting Queues Summary Block is stale.
  • #2044251: Remove '@none' from call to drush_invoke_process(), since it isn't supported in Drush 4.5.
  • #1678528 by helmo: Fixed Database deleted on edge cases.
  • #1912666 by ergonlogic: Fixed Stable manual 6.x-1.x install test failure.
  • #1912666 by ergonlogic: Fix command to run tests for 6.x-1.x.
  • Nginx: Fix typo in the location regex.
  • Nginx Security: BEAST attack protection and fix for PCI compliance.
  • #1906900 by fall_0ut - Nginx microcaching not disabled on localized/prefixed admin URIs.
  • Nginx: Make upload progress configuration compatible with latest release of Nginx extension and integration module for Drupal 7.
  • Nginx: Move some dynamic directives up in the location.
  • Nginx: Better protection for private URLs from bots/spiders (2)
  • Nginx: Improve locations for static files.
  • Nginx: Better protection for private URLs from bots/spiders.
  • Nginx: Add support for http://drupal.org/project/js module.
  • Nginx: Improve no-cache exceptions for known AJAX and webform requests.
  • Nginx: Improve performance for dynamic requests and reduce logging 404 errors.
  • Nginx: Remove duplicate location - already protected in the server template.
  • Nginx: Do not use device-specific, never working paths for Boost cache.
  • Nginx: Make json compatible with boost caching but dynamic for POST requests.
  • Nginx: Add Wysiwyg Fields support.
  • Nginx: Do not block spiders on URIs with event/calendar regex match.
  • Nginx: Avoid breaking WordPress import when WP-specific URI is used.
  • Nginx: Avoid caching /civicrm* and protect it from bots.
  • remove perlism in sed which would never match (\s).
  • explain why we do the crazy sed on dump (mysql bug)
  • #1786702 by clemens.tolboom - be nice to non-aegir backups like drush archive.
  • #1788398 by marvil07: Fixed Force dependency to drush < 5.
  • add missing robots and files/ rules to SSL hosts.
  • remove redundant paramenters to the CSR, fix email to use a standard default.
  • clarify comment on self-signed certificates.
  • #941870 - check for errors when copying certificates.
  • improve error handling in SSL key generation.
  • bump up the SSL key size to 2048 bit.
  • clarify the SSL key signing code.
  • don't encrypt SSL keys only to decrypt them after.
  • #1741814 by wamilton: Fixed Support For Non-Alphanumeric MySQL Passwords in provision-backup, migrate, and clone.
  • #1612252 by mig5, Steven Jones: Fixed 'site_offline()' variable needs to be 'maintenance_mode()' in Drupal 7.
  • #1440646 by tstoeckler, cafuego, mig5: Make Drush be runnable as Root with Provision installed.
  • #1734500 by Steven Jones: Fixed Can't run tests with Drush 4.6.
  • move files and robots.txt rewrite rules to the vhost.
  • #1108810 - protect the complete private files directory.
Back to top

1.9 release notes

The Aegir team is proud to announce the ninth release in the stable 1.x release branch! This release ships two minor security fixes and various bugfixes that have accumulated in the issue queue since the 1.8 release.

We also want to announce that Omega8.cc is joining the growing list of organisations financially supporting the core development of the Aegir project. In a partnership with Koumbit.org, Omega8.cc is dedicating money to make sure Antoine Beaupré, one of the core team members, can dedicate one day a week of his time on raw Aegir development. Along with the existing commitments of Computerminds (Steven Jones), mig5 (Miguel Jacq) and the existing commitment of Koumbit.org, Aegir is well assured of continuous development and long term maintenance.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Features

No features were added in this release.

Back to top

4. Security fixes

  • Filter Drush log messages properly when viewing task logs.
  • Properly exit after calling drupal_access_denied() on package/task nodes.

See also the security advisory (SA-CONTRIB-2012-080) for more information.

Back to top

5. Bug fixes

Back to top

6. Known issues

No know issues at this time.

Back to top

1.8 release notes

The Aegir team is proud to announce the eighth release in the stable 1.x release branch!

This release ships various bugfixes that have accumulated in the issue queue since the 1.7 release, including a lot of fixes on Nginx support.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Features

No features were added in this release.

Back to top

4. Bug fixes

Back to top

5. Known issues

No know issues at this time.

Back to top

1.7 release notes

Tagged:

The Aegir team is proud to announce the seventh release in the stable 1.x release branch!

This release ships various bugfixes that have accumulated in the issue queue since the 1.6 release, including a lot of fixes on Nginx support. We also ship a new clustering module aimed at lightweight slave deployments named the pack module, designed to replace the cluster module which has performance and configuration issues.

Also note that 2.x development is moving ahead with Drush 5 and Drupal 7 support, along with code refactoring and other features. Debian package builds will be available shortly in a separate Debian repository.

We also want to take this opportunity to welcome to our core team omega8cc, a long time contributor that will now be responsible for the maintenance of the Nginx code. Welcome on board Grace!

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Features

Back to top

4. Bug fixes

Back to top

5. Known issues

Back to top

1.6 release notes

The Aegir team is happy to release the seventh stable release in the 1.x branch.

This release fixes a regression introduced in the 1.5 release that stopped users from being able to compare sites when migrating. It also contains a number of small bug fixes and documentation fixes.

We recommend you upgrade your Aegir system.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Bugfixes

Back to top

4. Known issues

See also the 1.0 release notes for known issues in the 1.x series.

Back to top

1.5 release notes

Tagged:

The Aegir team is happy to release the sixth stable release in the 1.x branch.

This release fixes not being able to install Drupal 7.8 sites on PHP 5.2, an issue causing automatic installations to fail and other minor fixes.

We recommend you upgrade your Aegir system.

1. Another special note for users of the Debian packages

We've moved the location of the Aegir packages, so you must update your apt configuration. Further details can be found the in original announcement of this change: Debian archive migrated to debian.aegirproject.org.

The Debian packages also install Drush Make using a package rather than a manual download. If upgrading, you may be prompted to remove your current installation of Drush Make to continue.

Back to top

2. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

3. 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://community.aegirproject.org/help

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

Back to top

4. Bugfixes

Back to top

5. Known issues

See also the 1.0 release notes for known issues in the 1.x series.

Back to top

1.4 release notes

Tagged:

The Aegir team is happy to release the fifth stable release in the 1.x branch.

This release fixes the security vulnerability as announced by the Drupal Security Team

This release contains no other fixes or changes: this is simply a hotfix release to fix the security vulnerability.

We strongly recommend you upgrade your Aegir system.

Note that this security issue affects the Eldir theme only. The security issue does not affect your hosted sites that are managed by Aegir, and no re-verification of sites or platforms is necessary.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Bugfixes

Back to top

4. Known issues

See also the 1.0 release notes for known issues in the 1.x serie.

Back to top

1.3 release notes

Tagged:

The Aegir team is happy to release the fourth stable release in the 1.x branch. We have found only one critical bug (Drush 4.5 support) but have also fixed so many little bugs that we figured it was about time to make a new release. Also, it's becoming a bit of a tradition at DrupalCons :)

The major changes from 1.2 are a bunch of bug fixes for clients functionality, and a fix for the wget cron method.

Thank you to those who donated to the project since the previous release: harley, lol, rink & arielqgold. We continue to accept donations in order to cover various project costs. As an open source project, we need the support of the community to ensure ongoing development and support. Koumbit is pleased to provide administrative support for this, and you can find the donation page on their site: http://membres.koumbit.org/en/civicrm/contribute/transact?reset=1&id=5, which is also linked to directly from the front page of the community site.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. New features

As per our maintenance policy, we have not added any new features in this release.

Back to top

4. Bugfixes

Back to top

5. Known issues

See: http://community.aegirproject.org/1.0#Known_issues

Back to top

1.2 release notes

Tagged:

The Aegir team is happy to release the third stable release in the 1.x branch. We have found only one critical bug (in Nginx support) but have fixed so many little bugs that we figured it was about time to make a new release.

The major changes from 1.1 are that we now support the wget cron method for D7, and have fixed a lot of issues in the Nginx support. In addition, there is now the ability to "purge" platforms that Aegir might not otherwise recognize as eligible for deletion, and have robots.txt on a per-site basis. Finally, the "wget" support for cron.php has been rewritten with drupal_http_request(), so it's much faster and will detect errors properly - no more discrepancies between Aegir's idea of when cron was ran and the site's.

We've put in place a continuous integration server (Jenkins), which has allowed us to start automated testing of the Debian packages. This helps to ensure that automated installation of the software is stable. People wishing to test the latest development version of the 1.x tree can now install packages from the "unstable" repository; more information can be found here: http://community.aegirproject.org/debian#Package_versionning

While not specific to this release, we have made extensive improvements to the documentation that can be found at http://community.aegirproject.org/handbook, as well as API documentation on http://api.aegirproject.org

Also, we've begun to accept donations in order to cover various project costs. As an open source project, we need the support of the community to ensure ongoing development and support. Koumbit is pleased to provide administrative support for this, and you can find the donation page on their site: http://membres.koumbit.org/en/civicrm/contribute/transact?reset=1&id=5, which is also linked to directly from the front page of the community site.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. New features

As per our maintenance policy, we have keep new functionalities to a minimum. We did however, give in and merged the exportable backups feature in 1.1.

Back to top

4. Bugfixes

Back to top

5. Known issues

Back to top

1.1 release notes

The Aegir team is happy to release the second stable release in the 1.x branch. We have found two critical bugs during the more massive deployment of 1.0 and figured we could share the fixes with the community.

The major changes here are that 1.0 had broken the upgrade of Drupal 5 sites and was still allowing duplicate sites to be created under some circumstances.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. New features

As per our maintenance policy, we have keep new functionalities to a minimum. We did however, give in and merged the exportable backups feature in 1.1.

Back to top

4. Bugfixes

Back to top

1.0 release notes

Tagged:

The Aegir team is very pleased to announce the first official stable release of Aegir - 1.0. While it's been a mostly "open secret" that most of our releases are production ready, this one has been tested through no less than 15 alpha releases, 2 beta releases and 7 release candidates, for a grand total 24 test releases before we deliver this stable version.

Speaking of open secrets, here's a word from our founder, Adrian Rossouw:

The Aegir 1.0 release marks the end of my association with the Aegir project, as I am officially stepping down as project leader, handing the reins to Antoine, Miguel and the rest of the team.

Nearly 8 years ago, I left my job to help found Bryght, one of the first Drupal service companies, with the intention of building a hosted service with Drupal. I had a dream, and that dream was called "hostmaster". Over the next several years, the system I developed to accomplish this dream evolved into Aegir.

I started the Aegir project, in it's current form, out of a desire to ensure that my dream would be able to survive beyond my ability to dedicate myself to it. The very fact that I am writing this is evidence that it has succeeded beyond my wildest dreams.

Aegir is bigger than just one person, and I am incredibly happy and proud of the progress made, so I feel completely comfortable leaving you in the hands of my very capable co-maintainers.

Thank you to everybody for their support, and I wish nothing but the best for the project and it's future victories!

And thank you, Adrian, for this great project you have given to the Drupal community, it means a lot to us!

Now onto the release. This actual release isn't much different from the previous release candidates - you can see the list of changes from the previous RC7 release at the end of those notes. However, since this is our first major release in a long time, we figured it would be important to outline how things have changed since the old days of 0.3. For those of you who weren't there, back then installing Aegir was hard. There was no "clone", no SSL, no multiserver. You had to migrate sites one at a time and you had to create platforms yourself (no drush make!). We were still using CVS.

With 1.0, we have multiserver support, Debian packages, DNS, we're using git, drush make and we have a very dynamic community of users and shops using the project. We have ambitious goals for 2.0 and we're eager (pun intended) to start moving again! So if you were waiting for Aegir to be stable, easy to install, production-ready, now is the time. The 1.x branch will be well supported as a lot of shops are running it in production already. What are you waiting for?!

1. Major changes in this release

Since our last stable release (0.3) in august 2009, we've done an incredible amount of work. The code size nearly doubled as the development team and user base, although we don't clearly know yet how many installs there are out there.

We can already say that we've been pretty successful at fulfilling our release goals for 0.4 and the 1.0 roadmap. Even though we're missing bits and pieces, especially in DNS, and multi-server support is not as robust as we'd like it to be, there's still space for improvements and bugfixes in the 1.x branch, and we'll also start on the 2.0 roadmap once this release is out the door.

  • Multi-server support
    • External and multiple DB support
    • External and multiple webserver support
    • Webserver cluster support
    • Server and services abstractions
  • DNS
    • Master zones created on the fly with sites
    • Manual modification allowed through the provision-zone command
    • Slave servers
    • Support for Bind and dnsmasq
  • SSL support
    • multi-domain/wildcard support
    • use of HTTPS can be enabled or required
  • Migration improvements
    • Batch migrations
    • Site migration fixes your body and teaser for sites/community.aegirproject.org/ changes
    • No more rebuilding the whole node_access table
    • Cloning
    • Site rename support
    • Inter-profile migration
    • Ignoring site-specific modules so that mass-migrations are easier
  • Improved task management
    • Limit how many tasks run at a time
    • task revisions and timing
    • canceling tasks
    • possibility of queuing tasks from the backend
  • Improved platform management
    • Automated platform creation through Drush makefile or even a URL
    • access control and locking
    • deletion
    • platforms are stored in ~/platforms
  • Site management improvements
    • Named backups
    • Password resets
    • Inter-site security (storing passwords outside of settings.php AKA cloaking)
    • stopped hardcoding page cache
    • bulk operations
    • Views support
    • local.settings.php overrides
    • backup file size
    • .htaccess customization
    • Clean database names and users (instead of site_X)
  • Other improvements
  • Install and upgrade process improvements
    • Aegir can upgrade and install itself, no need to go through the frontend wizards in install.php or upgrade.php
    • Remote DB server support for installs and upgrades
    • Debian packages - apt-get install aegir
    • The Aegir install went from being a known nightmare to a total breeze, with 46 seconds to 5 minutes install times with the debian packages and 15 minutes installs on manual installs (for unsupported platforms)
  • Support for 7 operating systems and counting, we added:
    • Solaris support
    • CentOS support
    • Ubuntu support
    • Gentoo support
    • FreeBSD support
    • ... and that's just the confirmed installation reports, if it's UNIX, it can probably run Aegir!
  • Project management
    • Migrated to our own git repositories
    • ... then migrated back to Drupal.org when they switched to git
    • We now have our own OpenAtrium site (this site!) for the community (this means you!) to participate in
    • A handbook has been created and expanded to provide solid, collaborative documentation for the project, that anybody can contribute to (it's a wiki!)
    • We now have clear maintainers for different sections of the code, with 4 maintainers and counting
    • We now have continuous integration with a Jenkins server testing Aegir after commits and also testing the upgrade path
  • An explosion of third party modules
Back to top

2. API changes, documentation, 1.x maintenance policy and 2.0

The API changes since 0.3 are too numerous to list here. However, we are now committed to maintain the whole 1.x series with a stable API. There will be no change in the existing API, although we may add in some stuff if it is really necessary. All future API changes between 1.x and 2.x will be clearly defined so that third party module can be supported.

A documentation initiative has been launched to better document the Hostmaster API. In addition, a dedicated API site (along the lines of api.drupal.org) has been put in place to ease exploring the code-base of the Aegir Project. Much work remains, so you can track progress or help out here.

Major changes to 1.x will not be committed unless they are first tested in 2.0 and merged back. We will however keep the branch opened for documentation fixes and non-invasive changes like performance enhancements and cosmetic changes to the frontend. Major problems and "aegirWTF" may also be corrected in the 1.x branch, after a shakedown in the 2.x branch.

From now on, major development will take place in the 2.x branch, which will be created shortly after this release. The roadmap for that branch is ambitious but we'll tackle things one at a time, again on feature branches for major changes so that even that branch will stay stable throughout its development cycle. We will there keep in making stable alpha releases for your testing pleasure.

Back to top

3. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

4. 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://community.aegirproject.org/help

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

Back to top

5. New features

Since this is like a release candidate, we tried to limit the changes to this release to avoid breaking too many things, so not many new features. Of course, since 0.3, there are tons (see above) but this is only since rc7.

Back to top

6. Bugfixes

We did fix a lot of things however, with the upgrade path and the remaining critical issues.

Back to top

7. Known issues

Being really open about our project, we have never hidden the fact that some things, sometimes, do not work in Aegir. Our issue trackers are public, and we've made it a point of honor not only to document clearly what is wrong in our releases as soon as we find out about it, but also to reroll new releases when we fix it.

That being said, 1.0 suffers from a number of significant issues and design flaws. This is the list of all issues marked "major" in the queue right now. Some of those issues can be fixed within the 1.x branch, some can only be fixed by refactoring, and so they will be fixed in 2.x.

Back to top

1.0 Release candidates

This section documents all the release candidates towards the 1.0 release.

1.0-rc7 release notes

Tagged:

The Aegir team is very pleased to announce the seventh release candidate of Aegir 1.0.

This release primarily fixes issues with our drush makefile which have prevented installations and upgrades of the last couple of releases. We have also fixed issues with the upgrade.sh script and the Debian packages.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or recent rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Bugfixes

Back to top

4. Known issues

Back to top

1.0-rc6 release notes

Tagged:

The Aegir team is very pleased to announce the sixth release candidate of Aegir 1.0, aka "are we there yet?"

This is yet another hotfix release to fix an issue in the upgrade.sh script and Drupal 7 support.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or rc1/2, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Known issues

The Debian package are still in testing mode and feedback there is appreciated.

Back to top

4. New features

We have now specific maintainers for specific project areas.

A documentation spree has been started by the newly documentation team and merged in this release, so the API documentation should be more complete. In particular, we have deprecated hosting_queues_get_arguments() and hook_provision_args() that weren't used anywhere.

Back to top

5. Bugfixes

Back to top

1.0-rc5 release notes

The Aegir team is very pleased to announce the fifth release candidate of Aegir 1.0!

This is a hotfix release to fix a major issue in the upgrade path. All users are strongly encouraged to skip the rc4 release and upgrade here instead.

Changes in 1.0-rc5

  • fix the upgrade path (#1118558)
  • fix upgrade.sh to have the right older version all the time and automatically detect drush (#1117776)

Known issues

  • Drupal 7 support is broken (hotfix available in #1119850)
  • upgrade.sh is broken again, use this version instead until rc6 comes out

This release is otherwise mostly identical to 1.0-rc4.

1.0-rc4 release notes

Tagged:

The Aegir team is very pleased to announce the fourth release candidate of Aegir 1.0!

We have again found critical issues in rc3, detailed below, and a few key features that we wanted to slip into 1.0 that were just low-hanging fruits that deserved to be released. We hope this release candidate will be all shiny and without any critical issues so we can release it as 1.0.

Update: because of a last minute API change, the upgrade path is broken and it is not recommended to upgrade to this release. A new release has been published, so use 1.0-rc5 instead. See #1118558 for more information.

Key changes in 1.0-rc4

  • There is now a ~/clients directory in which symlink are automatically created to allow easy access to all your client sites (#1115960)
  • A variable is now set in settings.php (aegir_api) to allow contrib modules to inspect what Aegir version they are dealing with, if any. The setting is removed on export, that is, if dbcloaking is off (#1027358)
  • We fixed a big regression where the mass migrate form stopped working in rc3 (#1111532)
  • The private directory of Drupal 7 is now properly protected (#1108810)
  • The Debian package has been tested over and over again and is now the prefered install method for people on Debian
  • Consequently, install.sh has been removed and the manual install instructions have been revamped to be clearer, see this post for more information about the reasoning behind that change

Known issues

  • DNS has no access control - anybody can create any zone (#922252)
  • The site form suffers from some performance issues when you have a lot of platforms (#955854)
  • Cluster servers are probably broken right now (#1016890)
  • Aliases are not persisted across Migrate, (Rename), Clone (provision-deploy) (#1004526)
  • Upgrade path is broken (#1118558)

See all the issues tagged as aegir-0.4 and issues marked as 'major' for our comprehensive list of outstanding issues.

Installing and upgrading

The canonical source of installation documentation has moved from the usual INSTALL.txt to the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation has now been moved to the community site at

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes. You can download the upgrade.sh.txt script from http://community.aegirproject.org/node/431.

It is still imperative that you read the the Upgrade Guide (http://community.aegirproject.org/upgrading) and follow all version-specific upgrade instructions located at the end of the document before trying to run the upgrade script. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or rc1/2, there are unlikely to be any version-specific manual steps required to upgrade to 1.0-rc4, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

The upgrade.sh script attempts to backup the existing backend components, download new versions, and then run the hostmaster-migrate command. It assumes you are upgrading from the previous release (hostmaster-6.x-1.0-rc3). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

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://community.aegirproject.org/help

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

New features

Bug fixes

1.0-rc3 release notes

Tagged:

Aegir 1.0-rc3 release notes

The Aegir team is very pleased to announce the third release candidate of Aegir 1.0!

This is the third Release Candidate from which we will test fixes to critical bugs from rc2, as well as fix any additional critical bugs found since, until we have no criticals and will then roll out the official 1.0.

This release also includes a fix for a security vulnerability (see below). We recommend you upgrade your Aegir instance to apply this fix.

Key changes in 1.0-rc3

  • A security vulnerability was fixed that prevents arbitrary configuration from being injected into Apache vhosts by way of the Site Aliases form. See #1098304

  • The 'Client' feature / node type has been significantly refactored and simplified, with the ultimate aim of hooking it into other CRM/databases (e.g. for LDAP support), and better Aegir-managed site/user security. This involved an exception to our current 'API freeze' for the sake of getting this important refactoring in. See this summary of the changes this imposes

  • We've upgraded to use Drush 4.4 and Drush Make 2.2 on fresh installs and upgrades. These have been tested and should work without any problems.

Known Issues

  • DNS has no access control - anybody can create any zone (#922252)
  • The site form suffers from some performance issues when you have a lot of platforms (#955854)
  • Cluster servers are probably broken right now (#1016890)
  • Aliases are not persisted across Migrate, (Rename), Clone (provision-deploy) (#1004526)
  • The provision.info version tag wasn't updated properly and still reads 1.0-rc2
  • See all the issues tagged as aegir-1.0 and issues marked as 'major' for our comprehensive list of outstanding issues.

Installing and upgrading

The canonical source of installation documentation has moved from the usual INSTALL.txt to the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation has now been moved to the community site at

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes. You can download the upgrade.sh.txt script from http://community.aegirproject.org/node/431.

It is still imperative that you read the the Upgrade Guide (http://community.aegirproject.org/upgrading) and follow all version-specific upgrade instructions located at the end of the document before trying to run the upgrade script. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or rc1/2, there are unlikely to be any version-specific manual steps required to upgrade to 1.0-rc3, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

The upgrade.sh script attempts to backup the existing backend components, download new versions, and then run the hostmaster-migrate command. It assumes you are upgrading from the previous release (hostmaster-6.x-1.0-rc2). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

Bugs fixed

New features

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: http://community.aegirproject.org/help

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

1.0-rc2 release notes

The Aegir team is very pleased to announce the second release candidate of Aegir 1.0!

Yes, you read that right: 1.0! We've decided to rename the 0.4 branch to 1.0.

This is the second Release Candidate from which we will test fixes to critical bugs from rc1, as well as fix any additional critical bugs found since, until we have no criticals and will then roll out the official 1.0.

Key changes in 1.0-rc2

There are a lot of bug fixes and features added into this release.

INSTALL.txt and UPGRADE.txt, along with the various architecture hints, and other developer docs, have been moved to the community site under:

http://community.aegirproject.org/administrator-manual

The Aegir git repositories have moved back to drupal.org, we're back in the family!

We have fixed some key issues that were discovered during testing, including sites that were not put offline during migrations and data loss issues in multiserver migration. We have also worked on the upgrade path for legacy (pre alpha9) installs, which should be able to upgrade to this release directly.

Finally, we fixed a CSRF attack on the task form that allowed an attacker to force a user to run tasks on existing sites and platforms. This is non-critical as only tasks with no confirmation dialog (ie. safe tasks) could be triggered.

Also, we've moved to Drush Make 2.1!

Known Issues

  • DNS has no access control - anybody can create any zone (#922252)
  • The site form suffers from some performance issues when you have a lot of platforms (#955854)
  • Cluster servers are probably broken right now (#1016890) *Aliases are not persisted across Migrate, (Rename), Clone (provision-deploy) (#1004526)
  • See all the issues tagged as aegir-1.0 and issues marked as 'major' for our comprehensive list of outstanding issues.

Installing and upgrading

The canonical source of installation documentation has moved from the usual INSTALL.txt to the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation has now been moved to the community site at

http://community.aegirproject.org/upgrading

Within those sections you'll find step-by-step instructions for performing both manual and automatic upgrade processes. You can download the upgrade.sh.txt script from http://community.aegirproject.org/node/431 (note, we point to the version in the 6.x-1.x branch because we accidentally rolled the tagged release before changing the AEGIR_VERSION number in the script. So use this version of the upgrade.sh script, or pay close attention to what version the script says it will upgrade to.)

It is still imperative that you read the the Upgrade Guide (http://community.aegirproject.org/upgrading) and follow all version-specific upgrade instructions located at the end of the document before trying to run the upgrade script. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

For users coming from 0.4-beta1, beta2 or rc1, there are unlikely to be any version-specific manual steps required to upgrade to 1.0-rc2, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

The upgrade.sh script attempts to backup the existing backend components, download new versions, and then run the hostmaster-migrate command. It assumes you are upgrading from the previous release (hostmaster-0.4-rc1). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

Bugs fixed

New features

No Drush 4?

Some people might be wondering why we haven't changed the install.sh or upgrade.sh scripts to fetch the latest Drush 4.2 release.

Drush 4.2 has a bug which breaks rsync and possibly other stuff when using multiserver.

It's been fixed in Drush, but we are awaiting a 4.3 release before we roll with it. If you see 4.3 come out, you can probably upgrade your Drush if you wish (we tested this morning and are in fact compatible with Drush HEAD at time of writing).

See this ticket for more: http://drupal.org/node/1041386

We are working with the Drush developers to attempt to 'sync' our releases in future, but we wanted to roll out rc2 to all you good folk sooner rather than later this time :)

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: http://community.aegirproject.org/help

Thanks to our awesome community for their help, support and encouragement as always!

0.4-rc1 release notes

The Aegir team is very pleased to announce the first release candidate of Aegir 0.4!

This is the first rc from which we will go into crazy bugfixing mode until we have no criticals and will then roll out the official 0.4.

Key changes in 0.4-rc1

There are a lot of bug fixes and features added into this release.

Significantly, a major data-loss bug was fixed in Multiserver environments, that was causing a remote site's 'files' directory contents to be deleted if those files didn't already exist on the 'master' copy of the site on the hostmaster system.

Also, we stopped hardcoding "$conf['cache'] = 1" in sites' settings.php, returning control over the caching function back to the user by way of:

  • inserting the preferred setting into a file called 'local.settings.php' alongside the settings.php so it won't be clobbered by the template, or
  • same as above but in /var/aegir/config/includes/global.inc to set it globally for all sites, or
  • setting it in /admin/settings/performance on your site, and having that setting stick instead of being reset by the hardcode.

Known Issues

  • DNS has no access control - anybody can create any zone (#922252)
  • The site form suffers from some performance issues when you have a lot of platforms (#955854)
  • Cluster servers are probably broken right now (#1016890)
  • Aliases are not persisted across Migrate, (Rename), Clone (provision-deploy) (#1004526)

See all the issues tagged as aegir-0.4 and issues marked as 'major' for our comprehensive list of outstanding issues.

Installing and upgrading

The canonical source of installation documentation is as usual the excellent INSTALL.txt. The hostmaster and provision tarballs have the following checksums:

  • provision-0.4-rc1.tgz: 6f4da4ba7dcfaa1bcc3c44f96beb3eda
  • hostmaster-0.4-rc1.tgz: b2a42b151b817c1ea6cdf15462aa2e15

For users who have Rackspace Cloud accounts and want to install Aegir in the cloud, you are welcome to try mig5's Frigg script, which automatically creates a new virtual server and installs Aegir, with one command!

For users of 0.4-beta2 and earlier, we offer an upgrade.sh script in Provision, which tries to automate much of the steps outlined in the UPGRADE.txt.

It is still imperative that you read the UPGRADE.txt and follow all version-specific upgrade instructions located at the end of the document before trying to run the upgrade script. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

For users coming from 0.4-beta1 or beta2, there are unlikely to be any version-specific manual steps required to upgrade to 0.4-rc1, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

The upgrade.sh script attempts to backup the existing backend components, download new versions, and then run the hostmaster-migrate command. It assumes you are upgrading from the previous release (hostmaster-0.4-beta2). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

Bugs fixed

New features

No Drush 4 or Drush Make 2.0?

Some people might be wondering why we haven't changed the install.sh or upgrade.sh scripts to fetch the latest Drush 4.2 release or Drush Make 2.0.

Drush

Drush 4.2 has a bug which breaks rsync and possibly other stuff when using multiserver.

It's been fixed in Drush, but we are awaiting a 4.3 release before we roll with it. If you see 4.3 come out, you can probably upgrade your Drush if you wish (we tested this morning and are in fact compatible with Drush HEAD at time of writing).

See this ticket for more: http://drupal.org/node/1041386

Drush Make

Drush Make 2.0 has a bug that prevents building platforms from distributions that didn't come from drupal.org.

This has also been fixed in HEAD, but we are awaiting a 2.1 release before we roll with it. If you see 2.1 come out, you can probably upgrade your Drush Make if you wish.

See this ticket for more: http://drupal.org/node/1059238

We are working with the developers of these projects to attempt to 'sync' our releases in future, but we wanted to roll out rc1 to all you good folk sooner rather than later this time :)

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: http://community.aegirproject.org/help

Thanks to our awesome community for their help, support and encouragement as always!

1.11 release notes

The Aegir team is proud to announce the eleventh release in the stable 1.x release branch! This release ships a moderately critical security fix and one small upgrade bug with secret SSL certificates. Everyone is encouraged to upgrade.

1. Installing and upgrading

The canonical source of installation documentation is on the community site at:

http://community.aegirproject.org/installing

In a similar fashion, the upgrade documentation is:

http://community.aegirproject.org/upgrading

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 the upgrade path and version-specific information and follow all version-specific upgrade instructions before trying to run the upgrade script or manual upgrade. This especially applies to users upgrading from releases prior to 0.4-alpha8, including 0.3.

For users coming from the 0.4 betas or rc releases, there are unlikely to be any version-specific manual steps required to upgrade, but you should make a habit of reading them anyway just to make sure. No-one likes a nasty surprise!

Back to top

2. 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://community.aegirproject.org/help

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

Back to top

3. Known issues

Aegir 1.x depends on Drush 4.5 or 4.6, which are available only in Debian squeeze backports (old stable!), which may make fresh installs or careless upgrades impossible. To workaround this issue, install the Drush package directly from backports:

wget http://backports.debian.org/debian-backports/pool/main/d/drush/drush_4.5...
dpkg -i drush_4.5-2~bpo60+1_all.deb

See this page for other mirrors.

Back to top

4. Features

No new feature.

Back to top

5. Security fixes

  • fix mild security issue with login-reset links (#1220062)
  • security fix: SA-CORE-2013-003, files/ protection (#2141799)
Back to top

6. Bug fixes

  • fix upgrades if the SSL certificates are symlinks to files not readable by Aegir, a rare but legitimate use-case, see #2046249 for more information.
Back to top

0.4-beta2 release notes

Tagged:

The Aegir team is proud to announce the second beta release of Aegir 0.4.

This release primarily is a bugfix release.

There have also been quite a few patches sitting in our issue queues for review for a very long time, and we have attempted to commit a whole bunch of those in this release. Things have been moving a bit slowly and we're sorry for that.

Key changes in 0.4-beta2

There are a few changes in this release that are new, such as the presence of an early 'bulk operations' feature. We do not expect this to be bug free, but hope that by committing some of this new code and making it present in a new release, we'll get some community users testing this stuff and reporting back / patching it to make it better. Otherwise this stuff just gets lost in the queue!

After this release we will be looking strongly at a release candidate for 0.4.

Known Issues:

Some of our issues from beta1 are still actually present:

  • DNS has no access control - anybody can create any zone (#922252)
  • Inter-server migration may fail under some circumstances (#976300)
  • The site form suffers from some performance issues when you have a lot of platforms (#955854)

Also, an issue has been identified with remote web servers: in some cases, when the 'master' server syncs the site contents to a remote, it can delete the files/ of a site because it doesn't sync a site's files back to the master server except in the case of backups/migrations.

We would like to warn users that are making use of Aegir's multiserver features to be aware of this issue: http://drupal.org/node/976300 .

The road to 0.4 and Aegir contributors

Our core dev team is small and various demands for our time have been slowing development to a degree. We have a decent-sized community with a wide range of skills, and would like to take this opportunity to encourage our users to attempt to contribute to the project where they see fit - whether this be code development (bug fixes, new features), documentation, or even promotion / talks at Drupal events.

We will potentially be seeking new core developers to the project soon as well. If you'd like to chat with us about contributing to Aegir, don't hesitate to write on the mailing lists or come and see us on IRC in #aegir at irc.freenode.net. Aegir's core developers are Adrian Rossouw (Vertice), Antoine Beaupré (anarcat) and Miguel Jacq (mig5).

We know the barrier to entry can be a little high with hacking on Aegir, and will be refocusing our efforts to try and make that easier for new starters. An API site will be along soon!

See all the issues tagged as aegir-0.4 and issues marked as 'major' for our current outstanding issues.

Installing and upgrading:

The canonical source of installation documentation is as usual the excellent INSTALL.txt.

For users who have Rackspace Cloud accounts and want to install Aegir in the cloud, you are welcome to try mig5's Frigg script, which automatically creates a new virtual server and installs Aegir, with one command!

For users of 0.4-beta1 and earlier, we offer an upgrade.sh script in Provision, which tries to automate much of the steps outlined in the UPGRADE.txt.

It is still imperative that you read the UPGRADE.txt and follow all version-specific upgrade instructions located at the end of the document before trying to run the upgrade script. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

The upgrade.sh script attempts to backup the existing backend components, download new versions, and then run the hostmaster-migrate command. It assumes you are upgrading from the previous release (hostmaster-0.4-beta1). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

Bugs fixed

New features

0.4-beta1 release notes

After more than a year of (15!) alpha releases, we're finally out of the darkness and into the light! The Aegir project is pleased to announce the first beta of the 0.4 series. This release is primarily a bug fix release, but also new features that were the last targets for the 0.4 release goals.

The beta marks the beginning of the final cycle in the release of the 0.4 branch. We consider this release to be mostly feature complete. It still has bugs and problems, but since we are using it in production, we feel it's more appropriate to call it a beta, to invite wider testing and stabilise the codebase.

This is also an opportunity to test the upgrade path from pre alpha9 releases, which seem to be suffering from bitrot. You should be able to upgrade to this release from 0.3 and above.

Key changes in 0.4-beta1

  • Installer now support remote db servers (#973910)
  • Some work was done to improve the usability of the hostmaster-install command, which should be usable out of the box once provision and drush are installed
  • By default, we setup local MySQL server to use sockets, which creates a separate server but improves security significantly, as we do not force people to open their database server to the network (#977024)
  • The upgrade path for pre-alpha9 releases has been fixed

Known Issues:

The following are known critical issues with the current release, for which there are tickets, but we didn't feel were critical enough to prevent the beta release.

Some of the issues have been present since prior to alpha15, they aren't all new issues.

  • DNS has no access control - anybody can create any zone (#922252)
  • Inter-server migration may fail under some circumstances (#976300)
  • The site form suffers from some performance issues when you have a lot of platforms (#955854))

See also the complete list of critical issues.

The road to 0.4

We are not yet in a code freeze, as we still have critical issues opened (see below) and are aiming at a few more features to be really complete (see all the issues tagged as aegir-0.4 and issues marked as 'major').

We also have still a lot of issues to review before our final 0.4 release. If people are interested in contributing, a good and painless way of doing so is to take issues in the needs review queue and test the patches. Don't forget to change the status accordingly!

Installing and upgrading:

The canonical source of installation documentation is as usual the excellent INSTALL.txt.

For the first time, we offer an upgrade.sh script in Provision, which tries to automate much of the steps outlined in the UPGRADE.txt.

It is still imperative that you read the UPGRADE.txt and follow all version-specific upgrade instructions located at the end of the document before trying to run the upgrade script. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

The upgrade.sh script attempts to backup the existing backend components, download new versions, and then run the hostmaster-migrate command. It assumes you are upgrading from the previous release (hostmaster-0.4-alpha15). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

The script is in its infancy and has not been tested except by the developer writing it. We urge caution (make backups!) but encourage feedback. If in doubt, just follow the UPGRADE.txt steps and perform all the manual commands as you usually would. Some users report problems using the script on servers with really old versions of drush_make: the script stalls after upgrading Provision. You can try to run the upgrade process manually to fix that issue, which should now be fixed in beta1.

Bugs fixed

New features

0.4-alpha15 release notes

Tagged:

Aegir 0.4 Alpha15 released

The Aegir project is pleased to announce our 0.4 alpha 15 release. This release is primarily a bug fix release, which aims to tie off a huge amount of outstanding bugs and other tasks.

We did aim to release beta1 but decided that there were a few critical bugs still lingering that we wouldn't want to overshadow in such a momentous release. Instead we've chosen to push out one last alpha before (finally) heading out into beta and RC stages of the 0.4 cycle.

community.aegirproject.org

In our biggest news, which we've chosen to announce in this release, we are very proud and excited to announce the launch of our new community site, http://community.aegirproject.org !

Much preparation and planning has gone into building a clean, feature-rich community portal for our ever-growing Aegir users. We hope you'll agree that the documentation space, development information and community resources are long-awaited and desperately needed features to help users understand how Aegir works and how to use it.

The community portal features:

  • News area (blog, announcements)
  • Almost all the Aegir documentation has been re-written and dramatically improved in a new Aegir handbook, covering all aspects of installing, using, understanding and developing Aegir.
  • Screencasts and videos from sessions and tutorials (all the historical ones have been collated and added)
  • Events calendar
  • Shop resources (to be completed)
  • Feed syndication of the Aegir universe (twitter, articles, git commits)

The Documentation on groups.drupal.org is largely out of date and not in any sane order, and will be decommissioned in favour of the new documentation. Some of the still relevant and well-written documentation was dragged across and cleaned up where necessary.

The documentation area on the new site is still a wiki so we would like to encourage users to continue to keep them up to date and add more to help improve the experience for other users.

We'd like to thank all the contributors to the existing docs for their hard work and initiatives and hope you'll enjoy the new space and structure to keep helping make Aegir awesome.

Key changes in 0.4-alpha15

In our 0.4 alpha 15 release, these notable changes/improvements have occured:

  • The DNS feature has been implemented and is available in /admin/hosting/features (Experimental)
  • install.sh script has been changed considerably - most of the MySQL tests and user creation have been moved into provision to be handled by drush/php. There is no longer an 'aegir_root' user required for MySQL, we simply use your MySQL root user, which must have a password. You are required to supply a valid FQDN on installation, so that remote web servers can theoretically resolve the Aegir server if connecting to it for databases.
  • upgrade.sh script added (see below, adventurous people please test)
  • UPGRADE.txt updated to be a provide a little more clarity
  • There's a new /admin/hosting/settings area with misc settings/customisations, including:
    • ability to run wget instead of drush cron
    • delete sites without having to disable them first
    • when selecting a core profile, hide platforms that incidentally have those core profiles but are intended as distributions (i.e OpenAtrium)
  • backup task saves site's settings.php with uncloaked creds. Useful for exporting to non-aegir servers or for importing into new aegir servers

Installing and upgrading:

The canonical source of installation documentation is as usual the excellent INSTALL.txt.

For the first time, we offer an upgrade.sh script in Provision, which tries to automate much of the steps outlined in the UPGRADE.txt.

It is still imperative that you read the UPGRADE.txt and follow all version-specific upgrade instructions located at the end of the document before trying to run the upgrade script. This especially applies to users upgrading from before 0.4-alpha8, including 0.3.

The upgrade.sh script attempts to backup the existing backend components, download new versions, and then run the hostmaster-migrate command. It assumes you are upgrading from the previous release (hostmaster-0.4-alpha14). If you are not, you may have to edit the script to change the OLD_DRUPAL_DIR variable.

The script is in its infancy and has not been tested except by the developers while writing it. We urge caution (take backups!) but encourage feedback. If in doubt, just follow the UPGRADE.txt steps and perform all the manual commands as you usually would. Edit: some users report problems using the script on servers with really old versions of drush_make: the script stalls after upgrading Provision. Either run the upgrade process manually or apply this fix to your upgrade.sh.txt

Known Issues:

The following are known issues with the current release, for which there are tickets, but we didn't feel were critical enough to prevent another alpha release. Some of the issues have been present since prior to alpha14, they aren't all new issues.

  • DNS - currently there is no access control
  • Hostmaster install doesn't yet support remote db servers
  • 'Save' button on forms under some versions of Firefox/Iceweasel on Linux is greyed out

Bugs fixed:

  • #868896 : INSTALL.TXT needs updates
  • #880712 : install.sh.txt not prompting for the root MySQL password on Fedora 13
  • #882970 : settings.php should not be updated before a vhost file is created and verified
  • #888210 : Undefined variable: missing_requirement install_6.inc:214
  • #894004 : install.sh lies about mysql listen AKA move the mysql creds handling to hostmaster-install
  • #896492 : Anonymous users can't view the 'hosting/disabled/$site' disabled page
  • #897326 : Typo in provision.config.inc
  • #898732 : Deleted sites are counted against quotas
  • #911392 : Cloned site shows wrong database in UI
  • #913486 : Database server service stores port '0' in the hosting_service table
  • #914040 : Server crashed because hosting_site_alias table was huge
  • #919848 : verifying a server queues platform verification before the server verification
  • #922716 : Expand link opens new window when used from modal frame.
  • #928570 : Modal Frame font is inconsistent
  • #931136 : You can't delete the D7 alpha7 and beta1 sites.
  • #934830 : no width limit of 320px for div#navigation ul.links
  • #937490 : Fix Platform access control to deal with profile > platform paradigm
  • #940816 : SSL Enabled Settings do not trigger insertion of Rewrite rules in vhost file unless domain aliases specified
  • #942144 : Warnings when deleting a site
  • #944450 : Saving a Package Node removes attached data
  • #945894 : Enabling DNS service on server node gives MySQL errors
  • #946422 : cannot sync platform to remote
  • #947898 : Code in global.inc not picked up by settings.php
  • #949044 : It is possible to create broken site or duplicate sites nodes because there is not enough strtolower(trim(domain)) used
  • #950976 : Update hints for OS X
  • #950980 : New OpenSSL breaks install script
  • #951296 : @localhost no longer allowed in email addresses in Drupal 7
  • #955184 : Backup task breaks any site by replacing settings.php with version working only with Apache
  • #958094 : Disabling a site through Aegir front-end doesn't make it inaccessible
  • #960106 : That the 'Publish path' for a new platform should be absolute is not obvious (usability)

various others not reported in the queue

Feature requests fixed:

  • #366420 : DNS slave server support
  • #366814 : manage DNS records properly when creating/restoring/verifying/disabling/deleting sites
  • #826840 : Save settings.php with uncloaked credentials on backup (for using on non-aegir hosts)
  • #896914 : Migrate form displays current platform as a target
  • #897982 : Limit choice of install profiles to those on available platforms
  • #903884 : Delete task should be visible and inactive, not hidden.
  • #922278 : configure the master server to allow slaves to do zone transfers
  • #955550 : Improve Documentation to Reduce IRC Support Requests

various others not reported in the queue.

This was a mammoth and long-awaited release. Thanks to all our users for their continuing support, patience and contributions!

-- The Aegir core devs

Previous release notes

Release notes prior to Aegir 0.4-alpha15 were published on groups.drupal.org and can be read there.