Posted by Flying Drupalist on October 8, 2009 at 3:58am
Can the maintainers of the pantheon AMIs please update the Aegir AMIs?
I'm quite eager to use it, but would like it to be using the latest version please.
Thanks!
Can the maintainers of the pantheon AMIs please update the Aegir AMIs?
I'm quite eager to use it, but would like it to be using the latest version please.
Thanks!
Comments
This would be great
The existing version works well although I would love to see this updated to the latest release as well.
Such an awesome combination Aegir/Drush/EC2
Thanks to all involved
Yes
We're working hard on getting a beta release of Mercury done in the next week or so, but will update the Aegir instance also soon.
https://pantheon.io | http://www.chapterthree.com | https://www.outlandishjosh.com
Could there be an aegir +
Could there be an aegir + mercury together ami? Or does that not make sense?
Sorta
Aside from the general upsides of running a reverse-proxy in front of the web-side, these two systems are fundamentally different in their purpose and outlook. Making aegir responsive is nice, but it's likely to only really be used by one person (an admin) at a time, and its requirements are much more on the system level.
However, what DOES make a ton of sense (and which will be coming) would be allowing Aegir to manage installs on a Mercury instance (or many instances). That's where I think the big-picture vision for these things really fits together. It's a ways off though.
https://pantheon.io | http://www.chapterthree.com | https://www.outlandishjosh.com
I'm also interested in Aegir
I'm also interested in Aegir managing Drupal on a Mercury instance but I know that the majority of my clients would want Aegir running on the same instance because $62 a month is a lot for an instance that won't really be doing a hell of a lot. I've never run Aegir with a large number of sites 10,000+, does it really need it's own instance? Just trying to work out the use case.
I am doing this tonight .. I
I am doing this tonight .. I have decided to keep Aegir as is though. Im trying different things but its looking like I will install Aegir inside the mercury instance and then have my other platforms utilize pressflow or at least most of them. I dont see any reason really to have Aegir as a pressflow site so I will leave the Aegir platform as its designed for the most part.
I cant think of any good reason in smaller scale implementations to have a separate instance for aegir, however I will likely pull the db into its own instance and other aspects such as mail server etc when the time is appropriate, for starters I like having everything together though.
There really should be no reason this will not work, afterall Aegir is mostly a beast in drupal multisite clothing with all sorts of other good stuff of course; but were talking about putting a round peg in a round hole, really it should just work as expected. The focus should be on your platforms taking advantage of the solr varnish and other cache Mercury goodness, and consequently the sites within them.
I hope im right I want this to work! Mercury is blazing fast and well I'm addicted to Aegir.
Aegir running off of EBS - startup/shutdown
Couldn't you run Aegir on an EC2 server that you start up when you need and shut it down when you don't? An EC2 small server is only $15 or so per month if you only have it up M-F, 8-5 for example (and no I don't work those hours obviously :)
I've not started playing with Aegir yet, but it's getting to be top of my list to check out.
Its working perfectly for me.
Thats an interesting idea but you would have to get around the cron maintenance .. well actually I think you can disable the cron feature in the Aegir settings. The main factor is that dealing with multiple servers and provisioning sites on other servers is still in the experimental category and not feature complete so Aegir needs to be in place along with the sites. Aegir is framed as a drupal multisite rig, but it allows multiple "Platforms" which are essentially Drupal multisites themselves. The really cool part is that updating sites per platform is a breeze and creating sites etc is super fast plus many more cool features.
I am now using Aeigr inside Mercury successfully so far all things seem to be running perfectly. There really is no reason to have a separate instance for Aegir unless maybe your wanting Aegir to provision whole instances per site or other such interesting things that could be done by automating the AWS api's from within Aegir or someasmuch.... could be very cool!
You really should give Aegir a whirl ... its fantastic!
Sorry a bit confused
I'm loving Mercury and am intrigued by Aegir. But, I'm a bit confused about the ideal way to get the two to work together. So, is the idea to first set up a Mercury instance on AWS and then install Aegir inside Mercury so that you can use it's abilities to manage multiple sites? If that is the case, would Aegir then install those new sites within your AWS instance or does in create new instances?
Does anyone know if that Aegir install instructions work for installing inside a Mercury AMI on AWS?
Thanks kindly!
Aegir install works great in
Aegir install works great in Mercury.. ive only tested latest alpha5. Aegir will not mess any of the cool Mercury features. You make pressflow platforms inside aegir and leave Aegir as its designed with drupal core. The sites are installed in your mercury instance along with Aegir. If you want more than one site to use solr, memcache/apc etc you will have to take some additional steps to do that; Solr is the only one ive not figured yet but its not urgent for me as I have only one site using solr at the moment anyhow, for memcached and apc you add a prefix in the conf step. Aegir handles the conf step a bit different since you cannot directly edit the settings.php file and instead need to place your tweaks in an Aegir global.conf file.
There are some non-exhaustive Mercury + Aegir notes & ramblings over here... http://groups.drupal.org/node/35984
waiting for the update too :)
waiting for the update too :) thnxk
Probably not going to do alpha release updates
Hey guys; we're probably not going to do updates of the AMI until there's a real 0.4 release. In the mean-time, you can probably get there with the shell install script.
https://pantheon.io | http://www.chapterthree.com | https://www.outlandishjosh.com
subscribing
subscribing