community.aegirproject.org
Automatic install on Debian
Debian packages have been uploaded to http://debian.koumbit.net/, currently in the "unstable" distribution during the test period. We eventually want to upload those packages to the official archives, but this will take some adaptation and time to sponsor the packages in.
These are the installation instructions that are recommended on Debian. Aegir dependencies (Apache, MySQL, PHP...) are also automatically installed. If you are managing the installation from a remote Windows computer, well-known open source tools for this task are for example PuTTY (a SSH client for command line), and WinSCP (a SFTP client with easy text file editing).
If you wish to install Debian packages over an existing manual install, it's possible. See the Debian upgrade procedures.
Debian packages are uploaded to http://debian.aegirproject.org/ shortly after a release. We eventually want to upload those packages to the official archives, but this will take some adaptation and time to sponsor the packages in.
1. Special notice
Due to a resource issue, we cannot update the packages in the Debian reposititory until early October, which means that the last version available in them is Aegir 1.3. This means that it doesn't contain the security fix in Aegir 1.4. If you follow the install instructions here, you must then follow the special Debian instructions in the Aegir 1.4 Release notes
2. Adding the Koumbit repositories
Add the following line to /etc/apt/sources.list.d/koumbit-stable.list:
deb http://debian.aegirproject.org stable main
To install other versions, see the developer instructions for the debian package.
3. Adding the archive key to your keyring
This archive self-signs packages uploaded to it (and packages uploaded are verified against a whitelist of trusted uploaders) using OpenPGP (GnuPG, to be more precise).
The key of the archive is in the key.asc file. You should add the key using something like this:
wget title="http://debian.aegirproject.org/key.asc
apt-key">http://debian.aegirproject.org/key.asc
apt-key add key.asc
apt-get update
4. Adding backports for or manually installing Drush
You should also configure backports repositories for Drush. Version 4.4 of Drush is now in Debian unstable, wheezy, squeeze-backports and Ubuntu Natty.
So if you are running Debian wheezy or later, or Ubuntu Natty 11.04 or later, you don't need to do anything here. The Drush package you need is available from your distribution's repositories.
If you are running Debian Squeeze 6.0, add the following line to /etc/apt/sources.list :
deb http://backports.debian.org/debian-backports squeeze-backports main
You might also have to add a proper Pin-Priority before this works. Create a file called drush containing the following and drop it into /etc/apt/preferences.d:
Package: drush
Pin: release a=squeeze-backports
Pin-Priority: 1001
Then run:
apt-get update && apt-get install drush
If you are running Debian lenny 5.0 or Ubuntu Maverick 10.10 or Karmic Koala or earlier, we recommend downloading and installing the Drush package manually. The version of Drush in the Ubuntu Universe repository for these versions of Ubuntu is outdated. If you are using Ubuntu Lucid LTS 10.04, you can install the Drush package manually or instead use Brian Mercer's PPA (Personal Package Archive) using the following command:
sudo add-apt-repository ppa:brianmercer/drush
5. DNS configuration
Aegir requires a properly configured "FQDN" (Fully Qualified Domain Name) be assigned to the machine. In practice, this means that the hostname returned by the hostname -f
and uname -n
shell commands should resolve to the IP address for this server, and vice versa, with the resolveip
command (included with the mysql-server package).
6. Manual sudo configuration
If you are running sudo versions previous to 1.7.2p1-1
(in Debian squeeze and Ubuntu Lucid), you will need to manually modify your /etc/sudoers file to add the following line:
aegir ALL=NOPASSWD: /usr/sbin/apache2ctl
The line above assumes that you have created a user aegir as specified in the installation instructions.
7. Installing Aegir
To install aegir, frontend and backend, use the following command:
apt-get install aegir
If apt-get reports that the aegir packages have unmet dependencies, then make sure that you have installed Drush (as explained above). On a debian system, you can force the install of Drush from the squeeze-backports repository:
apt-get -t squeeze-backports install drush
Then install aegir using the apt-get command above.
This will prompt you for the required information (MySQL password, Postfix configuration...) and go ahead with the install.
During the Postfix configuration, the following options appear: "No configuration, Internet site, Internet with smarthost, Satellite system, Local only". That first text screen only allows to use the tab key to select "OK", and then the enter key to display a second screen where you can select one of the choices. The default is "Internet site", useful in most cases to enable the server to send email messages, for example to the admin.
At the end of the installation, you will receive an email message or, if the user "aegir" has been assigned with a local email account during the installation, the file /var/mail/aegir will contain the message. It will include a one-time login to your new Aegir control panel, that is a URL to copy into your browser so that you can set the password for the "admin" user.
8. Custom distributions
If you have your own makefile, you can go ahead with the above process, but change the makefile to the one you want:
echo debconf aegir/makefile string /var/aegir/makefiles/aegir/aegir-koumbit.make | debconf-set-selections
apt-get install aegir
This allows you to specify the makefile path for your custom distribution of Aegir. To maintain these customizations, you'll need to ensure you do the same when upgrading.
An example aegir-koumbit.make file could look like:
core = 6.x
api = 2
includes[aegir] = "/usr/share/drush/commands/provision/aegir.make"
projects[] = module_filter
Note that for this to work, you may need the patch from this issue, allowing drush_make to reference absolute system paths.
9. Troubleshooting the install
To make the install smoother, the install command is run without much debugging information, which can make diagnostics pretty hard. For this, there's a special environment variable you can set that will trigger debugging output. Install aegir with this:
env DEBUG=yes apt-get install aegir
You can build your own Debian packages from our repositories using those instructions.
Note: the DEBUG flag is deprecated. In 1.x releases, it is accepted, but in 2.x it won't. You should use DPKG_DEBUG instead, it is usable starting from 1.1-4.
- Login or register to post comments
- Print entire section
- Talk
Automatic Installation on Ubuntu 11.04+ (QuickStart)
Here are simplified instructions for installing Aegir on a server, quickly and easily.
The fastest way to install Aegir is on the latest Ubuntu Server LTS (Long Term Support). Currently 12.04.
Command Summary
Here is every command, ready to copy and paste.
sudo su
echo "deb http://debian.aegirproject.org stable main" | tee -a /etc/apt/sources.list.d/aegir-stable.list
wget -q http://debian.aegirproject.org/key.asc -O- | apt-key add -
apt-get update
apt-get install aegir
It is highly recommended to read through the Installation Instructions step by step to give yourself the feel for how this is done. In addition, if you are not already familiar in Linux system administration, please read up on the subject. Standard linux security protocols should be followed.
Installation Instructions
Enter all commands in code boxes
exactly as they are written.
ALL commands should be entered as root
user until these instructions are complete. After that, you should never have to use the root user.
Self-installation of Ubuntu has you create an additional user in the admin
group, which means they can sudo. If you are using a cloud hosting service, it likely just sent you root user credentials. Server security and user management is up to you. Don't give away access to root or the aegir user unless you know what you are doing. Follow standard web host best practices
For a summary of all needed commands, scroll to the bottom of the page.
Fire up a new server
- Use Ubuntu 11.04 Server Edition for the smoothest and most reliable installation experience.
- Make sure it has at least 1024MB, preferably 2048MB of memory. Depending on your host you will have to configure a hostname. It can be convenient to call this 'aegir'.
- If you want the smoothest installation, create a brand new server. There will be the least chance of conflicts if you start with a brand new Ubuntu 11.04 server. If you use Ubuntu Desktop, you should be able follow these instructions without any problems.
- Run all commands as root. If you are not root, enter
sudo su
Add the project repositories and archive key
Use this command to add the Aegir package "Software Source" repository to your system:
Use this command to add the archive key to your keyring:echo "deb http://debian.aegirproject.org stable main" | tee -a /etc/apt/sources.list.d/aegir-stable.list
Then, finally, update your apt repositories:wget -q http://debian.aegirproject.org/key.asc -O- | apt-key add -
apt-get update
Install configure Aegir and dependencies
Once you have added the repositories, you can now fire off the standard debian installation command. For Aegir 1.x, the command is:
For Aegir 2.x, the command is:apt-get install aegir
This fires off the installation script for AEgir, along all dependencies including Apache, MySQ and PHP. You will be asked a number of questions about your server.apt-get install aegir2
- You will be asked to create a MySQL root user password. Make this long and random and type it down somewhere safe, you won't need it very often, but you will need it later on in the installation process.
- In Postfix Configuration: Choose Internet Site, unless you have a reason otherwise. When asked for the System mail name, pick either the hostname (default) or the domain name you will be hosting this server on.
- In Configure aegir-hostmaster, you will be asked to choose a "URL of the hostmaster frontend". This should be either the hostname (default) or the domain name the server will be hosting, with "aegir" as a subdomain. For example, "aegir.example.com". You may want to change this to whatever you prefer, just don't forget it as it will be where you use the Aegir front-end.
- After entering your domain, Aegir Hostmaster installation will ask you for the MySQL root password you created earlier. You did write it down, didn't you?
NOTE: The current DEB package requires you to enter the MySQL root password twice. When this script is done, if everything went ok, after a lot of other interesting information, you should see this:Aegir is now installed. You can visit it at http://test/user/reset/1/1329504351/eda205d9a27abde400a27cf160dff69a
***... frontend bootstrap correctly, operation was a success!
Setting up aegir (1.6-1) ...
Setting up libhtml-template-perl (2.9-2) ...
Setting up mysql-server (5.1.54-1ubuntu4) ...
Setting up php5 (5.3.5-1ubuntu7.7) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
root@test:~#
At this point, everything is installed. Visit the link the script provided you to check out the frontend. Switch to the
aegir
user to check out the backend:su - aegir
Once you are the aegir user, check out the drush site aliases it gives you.
@hostmaster
is the alias for the new front-end you created. You will get new site aliases for every platform and site you create.drush site-aliases
Give yourself access to the server
As the "Administrators Manual" can tell you, you should only manage the Aegir server from the backend as the
aegir
user.However, by default, the
aegir
user cannot sudo (except to restart apache). The aegir user also does not have a password. Therefor, the only way to become aegir is tosudo su - aegir
from a user that can.So, to finish the server, you should give yourself a personal account that you can use to login to the server with a password in case all of your SSH keys get lost.
To add yourself as a user:
Then fill out the little wizard it gives you.adduser yourname
//@TODO: Add some helpful notes about SSH keys and remote aliases.
Install SSH on your server, generating your SSH keys and install them on your Ubuntu server. (Directions to generate your SSH keys are assuming your PC is Ubuntu as well, Windows users look below for SSH directions)
If using Windows, you must use Putty, PuttyGen, and PuttyPageant to generate and use your SSH keys.
- Tutorial #1: http://the.earth.li/~sgtatham/putty/0.53b/htmldoc/Chapter8.html
- Tutorial #2: http://www.howtoforge.com/ssh_key_based_logins_putty
You will want to also be a part of the aegir and www-data groups so you can write to some of their files:
addgroup yourname aegir
addgroup yourname www-dataStart Using!
Now that aegir is installed, head to the User Manual page to get your first platform and site up and running.
Credits
This document was originally based on http://community.aegirproject.org/installing/debian but has been trimmed down to list only the steps you need to use on an Ubuntu server to get Aegir up and running as quickly and easily as possible.
#1
On Squeeze, I tried to install aegir2, but have some dependency errors, firstly stating I need hostmaster2 and provision2, then stating I need drush5.5 or greater. I have installed drush5.8 using php-pear package, but apt-get mustn't know about this.
I thought that running 'apt-get install aegir2' would have picked up the correct hostmaster and provision (aegir-provision2 and aegir-hostmaster2), as I think it does for 'apt-get install aegir'.
root@aegir2:~# apt-get install aegir2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
aegir2 : Depends: aegir-provision2 (>= 2.0~alpha1) but it is not going to be installed
Depends: aegir-hostmaster2 (>= 2.0~alpha1) but it is not going to be installed
E: Broken packages
root@aegir2:~# apt-get install aegir-provision2 aegir-hostmaster2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
aegir-hostmaster2 : Depends: drush (>= 5.5) but 4.5-2~bpo60+1 is to be installed
aegir-provision2 : Depends: drush (>= 5.5) but 4.5-2~bpo60+1 is to be installed
E: Broken packages
Thanks in advance for any help with this.
#2
@mccrodp: I had a similar experiance, and opend this issue: http://drupal.org/node/1920152
#3
Would it be possible to add "profile" as an option, just like "makefile"?
#4
Sure. It would have to be added to the drush hostmaster-install and possibly hostmaster-migrate commands. Feel free to open an issue. Patches welcome ;)
#5
Thanks to jonpugh @ #32 and #33 for helping me get aegir 1.9 going with a fresh install of Debian Wheezy. The default wheezy version of drush is now too new (v5.x) for aegir 1.x. You need version 4.x, available in squeeze-backports. If you've already tried to install and run into "The drush command '@hostmaster status' could not be found." you must purge aegir and drush before attempting to reinstall with the correct drush version pinned.
#6
I had problem installing aegir2 on debian 7. Warning was
ERROR: Module ssl does not exist!
This can be solved with enabling mod_ssl on your apache2. For my case I needed to create /etc/apache2/mods-available/ssl.load with content
LoadModule ssl_module /usr/lib/apache2/modules/mod_ssl.so
After creating that file and restarting apache enable module sudo a2enmod ssl.