aegir

NOTE: this is an old thread, with now outdated information regarding using Nginx with Aegir. While as a standalone Nginx configuration it may still work fine, it was greatly improved in the meantime and now Nginx is natively supported in Aegir, no more hacks/patches etc. You can install (and upgrade) Aegir based on Nginx, with all enhancements thanks to available now Barracuda & Octopus installers, hosted on GitHub and Gitorious: https://github.com/omega8cc/nginx-for-drupal and http://gitorious.org/aegir/barracuda-octopus.

--------

The shortest answer is: YES.

Aegir has been of great help in managing my sites, there are a few things that would be nice to have though. One of these in automated backups, I did some searching thinking I could put some modules together to do this. I would ideally like to schedule them by hour, day, week etc.

Can anyone inform me on how do configure this?

It would also be great if backups could be sent to a different server, but for now an rsync or scp done by crontab will be fine.

I'm not sure if this has been discussed, but one of the things that I would love is to have subversion support. My workflow involves creating new sites for dev work or testing, and I would be great if I could have each site be it's own setup instead of being installed as a multisite, and then have the code automatically added to a new subversion project. Then I can deploy the completed sites out to their respective servers from svn (or have aegir do this for me??? :) So has any discussion around these ideas happened yet?

We're proud to announce the fourth release candidate of the 0.3 branch of the Aegir hosting system for Drupal.

Ægir is a set of contributed modules for Drupal that aims to solve the problem of managing a large number of Drupal sites. It does this by providing you with a simple Drupal based hosting front end for your entire network of sites. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.

This is the fourth release candidate of the 0.3 branch. This release is a maintenance release and the only project goal is the porting of Aegir 0.2 to Drupal 6. As such the code base is already feature complete and only bug fixes will be accepted before the final release is made.

Fixes in this release include :
- fix lots of documentation: [#553230], [#553202], [#550352]
- fix tasks permission: [#535562]
- fix install_profile_api dependency: [#550696], [#545168]
- fix add site tab in client form [#525676]

I have finally got around tackling git-cvsimport. After a little bit of tweaking around, I've been able to import the entire history of the various Aegir projects on Drupal.org in our git repositories. This will enable much easier collaboration and decentalised development.

There has been some talks in the issue tracker recently about implementing SSL support in Aegir. It's an exciting feature I've been thinking about for a while, and I'm at the point of trying to figure out how it would actually be implemented. I wrote up a first spec draft of what it would look like and I would like to seek wider discussion on the subject. How do you think this should be handled? How does your provider deal with SSL right now? Any specific issues we need to think about?

Aegir is so totally freaking awesome!!
New sites in a matter of seconds. Maintaining modules profiles updates .. everything is so much smoother & streamlined!
I have been watching you geniuses build this bad mama jama for months and couldnt be happier with the results!

I can hardly contain myself ... I have more than a dozen sites on my todo list and Aegir is taking a huge bite out of the workload!

Thankyou! Thankyou! Thankyou!!
^_^

As announced a long time ago, I have remove the old 0.1 install instructions from the tabs above that were confusing a lot of people. A lot has changed since 0.1, especially in the way Aegir is installed and the proper way to figure out how to install Aegir is to read

When running drush.php provision verify, it seems provision is unable to find the master_db_host, master_db_user and master_db_passwd, resulting in an error: Could not connect to the master database. An error occurred at function : drush_provision_mysql_provision_verify_validate. If I pass the three options to the verify command as arguments, (eg. drush.php provision verify --master_db_host=localhost --master_db_user=user --master_db_passwd=passwd), provision verify works, and proceeds to creating the drushrc.php file, with NULL values for master_url and master_db.

To celebrate the launch of Drush 2.0, we’re handing out several I <3 Drush t-shirts.

If you want a shirt, what you need to do is make a screencast or blog post about how Drush has made your life easier. Show or explain how you used to do something manually, and how it’s much quicker and simpler with Drush. Once you’ve posted about Drush, tweet about it with the #drushrush tag, and we’ll select the top three posts and those authors will receive a t-shirts in the mail.

So start posting and happy drush’ing. Oh yeah, you can also buy the shirt over here but what fun is that.