I had been trying to install aegir on my ubuntu server and its the manual installation which i am trying to do and i am stuck at this error below:
Unable to download http://drupal.org/files/common.inc_6.28.patch. [error] Could not download platform using drush make.
Most of what I have read about Aegir seems to deal with maintaining many sites in a multisite installation. Is it also possible to manage multiple sites which are all single site installations? Is Aegir even an ideal solution for that scenario?
I have tried to install drush 7 in CentOS 6.5 as commands below:
curl -sS https://getcomposer.org/installer | php
mv composer.phar /usr/local/bin/composer
ln -s /usr/local/bin/composer /usr/bin/composer
git clone https://github.com/drush-ops/drush.git /usr/local/src/drush
git checkout master #or whatever version you want.
ln -s /usr/local/src/drush/drush /usr/bin/drush
But when I input "composer install",then press Enter button, I get some errors:
[root@localhost drush]# composer ins
I am studying multi-site hosting solution with Aegir. In particular, the method used to update the version of Drupal multiple website in one step.
In interface to migrate sites from a platform to another, i noticed this: "You can perform a batch migration of websites from this source platform to a different target platform using this form , if you wish to order Do That securely , Clone always one of them in its current platform , Then test Migrate cloned copy of the first and check if the cloned copy works fine , Before You Will try that with your live sites."
My question is
I have recently installed Aegir (6.x-2.1) on a Debian 6.0.10 (squeeze) following the instructions found here http://community.aegirproject.org/node/400.
I have followed the instructions found here: https://mig5.net/content/developing-aegir-extending-aegir-and-communicat... and here: https://groups.drupal.org/node/97039, to pass data from signup form to platform's installation profile, but with no luck.
in more details I created a drush script hosting_school.drush.inc in my hosting_school module and inside the script i have implemented hook pre_host
The Aegir community has always seen among the best Drupal experts in the community so let me be lazy and ask you people: what techniques would you use to keep a community website like this one free of spam?
We are currently using the Honeypot and Mollom modules, but as you may have seen recently here (~7000 spam nodes created after christmas), this is not always enough. After reporting pages and pages of spam to Mollom, we (me and Helmo) have worked on a neat little view to massively (using the Batch API and VBO) remove spammy content from the website.
Hi, i have Aegir runnig, but when i want upgrade my server Ubuntu 10.04 i can't :
apt-get upgrade -> return:
You should run "apt-get -f install", to fix them. The following packages have unmet dependencies: aegir2: Requires: aegir2-provision (>= 2.0) but is not installed aegir2-hostmaster: Requires: drush (>= 5.5) but is not installed Wymaga: aegir2-provision (>= 2.0) but is not installed
apt-get -f install -> is not much helpful.
We are using the Drupal Feeds Module (https://www.drupal.org/project/feeds) on many sites in Aegir and it is working wonderfully on most sites. Once we add an additional alias (besides the www. one) the automated process stops running. From what we can tell this isn't an issue with the module it is something with what all is changed once an alias is added. We can manually import everything, but as we keep adding aliases our list of sites to manually import is growing rapidly.
Any help would be greatly appreciated.
I (and bgm, among others) have committed to supporting a dedicated StackExchange Q&A site for CiviCRM, and you should too: http://area51.stackexchange.com/proposals/77367/civicrm?referrer=T6p-Ire...
Dedicated sites like community.aegirproject.org are great for providing a central place for the community to discuss and share. However, they take a non-trivial amount of work to maintain, moderate, currate, etc. Moving to StackExchange relieves many of those responsibilities, allowing the core team to focus more on fixing bugs and coding new features.