Documentation

Notes from conversations over the past few weeks in IRC, email and on the skype. These notes are intended to capture the mind-meld consensus on how to architect the guts of Aegir so that we can embrace multiple servers and multiple services for 0.4!

This is an outline for now; I will flesh out and add diagrams in a bit. Feel free to embrace and extend!

• Drush @aliases will allow us to identify servers along with bundles of services. E.g. @webserver might be an IP/domain plus --http-service=apache2 --db-service=null --file-service=local

This document might seems long because of many explanations but the basis of ssh remote loging, password or passwordless is really simple, as explained in the Principles paragraph below

Purpose of this document :

Give some explanation and be a reference to setup SSH login on a server, or "password-less" login between server.
Each time I need to do this I dig the net to find some good and clear explanation, and often end up having to untangle confusing ones or dangerously working but overcomplicated one. More importantly most of those are unclear about the WHY we do things and I tend to think that not understanding is the worst thing you can do in "security".

So we've been talking seemingly forever about possible queuing system instead of our crappy "PHP/Vixie Cron based" one, but we have yet to document pro/cons of possible alternatives. Here are the goods (or the beginning of em).

Aegir install on OSX Snow Leopard

Aegir install instructions are fantastic if you run Debian/Ubuntu Linux. Some of the steps for OS X are a quite different. These instructions assume you are installing on Snow Leopard Client; if you are running on Snow Leopard Server many of these steps will not apply to you.

This page, like all our documentation, is a Wiki - please feel free to add and edit.

The Aegir project is growing rapidly, and more and more people are installing and testing the code. Many users ask about how to help out and give something back to the project - so that's what this page is about.

Finding and Reporting Bugs

So you've found a bug? Although bugs obviously aren't good, in a complex project like this they're bound to exist - so it's brilliant you found it. Now we'd really like your assistance to help us fix it.

Here's how:

This page is just intended to be for the development team to make notes about needed documentation for the project. It's a scratchpad for notes, thoughts etc.

Existing Documentation to revise (perhaps because the code has changed):

Features Yet to be documented:

Troubleshooter tips to write up:

FAQs to write up: