Posted by anarcat on September 17, 2009 at 10:46am
The Aegir project is happy to present the first alpha release of the 0.4 milestone. This is a "developer preview" release following the hugely popular 0.3 release, to allow people to play around with the new features we are developing and is not meant to be production-ready, use at your own risks. It should be fairly stable anyways, as very little major changes were brought in, but a lot of new exciting features!
Installation and upgrade instructions
New features:
- site clone support #448692: site clone support
- SSL support (no certificate management yet) #537004: "SSL site" option
- arbitrary port support #515052: Customizable port field per site
- domain redirection #535098: domain redirection
- arbitrary vhost configuration support (vhost create, vhost delete drush commands, backend only for now)
Bugfixes
- pass extra attributes to hosting_site_form so hosting_site_update doesn't send null parameters to the db #576822: Adding a site alias disables the site
- calculate the number of sites to run cron on properly from enabled sites in hosting_site table #576814: Cron queue not getting cleaned
- enable dependent modules in features, but don't disable features that have dependencies #573438: Proper dependency management in features
- properly hide the Delete button on site node forms except for sites already deleted properly #564038: Make deletion of sites/platforms consistent (Node deletion or Delete task)
- stronger migration validation for platforms with no possible targets. thanks mig5 #558628: Form to migrate from current platform to current platform submits, and shouldn't
API changes
- more parameters to domain validation: instead of just passing nid and port, we now pass an array of parameters, which will usually be a array version of the node object. hooks can now validate against a client and such. now we are certain that client A cannot create a site on a different port than client B for the same domain (but client A can). see #570980: allow vhosts of the same name on a different port
- ditch the confusing hosting_site_exists() in favor of a more generic and consistent hosting_domain_allowed() that also calls the hook_allow_domain, which should all return true for the site to be allowed
- virtual hosts files are now created with the port in the file name so that different vhosts on different can be generated without conflicts.
