This site is a static archive of the Aegir community site. Documentation has moved to http://docs.aegirproject.org. Other community resources can be found on the Contacting the community page.
Skip navigation

Revision of 3.0-beta1 release notes from Tue, 03/24/2015 - 14:55

Help

3.0-beta1 release notes

CONCEPT

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

2. Major API changes

to be determined.

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.

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 :)

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:

  • 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:

    ...

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

<

ul>

  • #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.
  • 6. Known issues

    • Drupal 8 support is (Chasing HEAD) not complete.
    Need help?

    Documentation

    The notebook section provides a way for you to store and share information with your group members. With the book feature you can:

    • Add book pages and organize them hierarchically into different books.
    • Attach files to pages to share them with others.
    • Track changes that others have made and revert changes as necessary.
    • Archive books that are no longer of interest to the group. Archived books can be reactivated later if needed.

    The revisions let you track differences between multiple versions of a post.