Difference between revisions of "Aegir"
Jump to navigation
Jump to search
(moar, mvs) |
|||
| Line 4: | Line 4: | ||
Aegir uses Drupal multisite features to share one Drupal codebase install as a 'platform' between sites. Distributions are equal to platform+site, i.e., turnkey solutions. Content can be shared (migrated) between sites using an updated or different platform (with the same content modules, natch). A platform and site distribution is created from a .make and .info using Drush Make. The Profiler library is installed with the .make and uses a .info file to specify modules to be initialised, including site sections/etc. from the Features module plus configuration settings via the Strongarm module. Provision initialises a site on that platform and installs the platform+site in Aegir. Features and theme are stored using Git, --working-copy can be used to build a dev site then content can be migrated from live for testing. Dev platform is perfected, then rebuilt as live without --working-copy. | Aegir uses Drupal multisite features to share one Drupal codebase install as a 'platform' between sites. Distributions are equal to platform+site, i.e., turnkey solutions. Content can be shared (migrated) between sites using an updated or different platform (with the same content modules, natch). A platform and site distribution is created from a .make and .info using Drush Make. The Profiler library is installed with the .make and uses a .info file to specify modules to be initialised, including site sections/etc. from the Features module plus configuration settings via the Strongarm module. Provision initialises a site on that platform and installs the platform+site in Aegir. Features and theme are stored using Git, --working-copy can be used to build a dev site then content can be migrated from live for testing. Dev platform is perfected, then rebuilt as live without --working-copy. | ||
| − | === | + | === [http://drupal.org/project/barracuda Barracuda] box setup === |
| − | * [[ | + | * Debian |
| + | * Download, edit, run [http://drupal.org/project/barracuda Barracuda] [http://drupalcode.org/project/barracuda.git/blob/refs/heads/master:/BARRACUDA.sh.txt git] [http://drupalcode.org/project/barracuda.git/blob_plain/refs/heads/master:/BARRACUDA.sh.txt raw] stack install script | ||
| − | + | * Create users, add to /etc/sudoers | |
| − | * | + | * Change port in /etc/ssh/sshd_config, disable root login |
| − | * | + | * Open ports (ssh, 6667 for irc, 11370 for pgp keys) |
| + | * Give aegir shell access in /etc/passwd, password/keys | ||
| + | * Load Csf module in webmin; From local file > /etc/csf/csfwebmin.tgz > Install Module | ||
| − | === | + | === [http://drupal.org/project/octopus Octopus] === |
| + | Like Barracuda, but a satellite Aegir instance with pressflow and other distros. | ||
| + | |||
| + | === Aegir usage === | ||
| + | * http://www.computerminds.co.uk/articles/migrate-sites-one-aegir-another | ||
| + | |||
| + | === Dev/production workflow guides === | ||
* [http://greenbeedigital.com.au/content/drupal-deployments-workflows-version-control-drushmake-and-aegir Drupal deployments & workflows with version control, drush_make, and Aegir] (mig5, Oct 28 2009) | * [http://greenbeedigital.com.au/content/drupal-deployments-workflows-version-control-drushmake-and-aegir Drupal deployments & workflows with version control, drush_make, and Aegir] (mig5, Oct 28 2009) | ||
* [http://lists.aegirproject.org/pipermail/aegir/2011-January/000026.html Using drush hosting-import to auto-create your platform node (and other entities)] (mig5, Jan 11 2011) - Updated workflow on Aegir mailing list | * [http://lists.aegirproject.org/pipermail/aegir/2011-January/000026.html Using drush hosting-import to auto-create your platform node (and other entities)] (mig5, Jan 11 2011) - Updated workflow on Aegir mailing list | ||
* [http://www.archive.org/details/drupalconchi_day2_from_zero_to_distribution_using_features From Zero to Distribution using Features, Profiler, and Drush Make] (dimitri, March 9, 2011) | * [http://www.archive.org/details/drupalconchi_day2_from_zero_to_distribution_using_features From Zero to Distribution using Features, Profiler, and Drush Make] (dimitri, March 9, 2011) | ||
| − | + | == Drush == | |
* [http://drupal.org/project/drush Drush] - [http://drupal.org/project/issues/drush?categories=All issues] | * [http://drupal.org/project/drush Drush] - [http://drupal.org/project/issues/drush?categories=All issues] | ||
* [http://drush.ws/ Drush.ws] | * [http://drush.ws/ Drush.ws] | ||
Revision as of 02:47, 9 January 2012
Process overview
Aegir uses Drupal multisite features to share one Drupal codebase install as a 'platform' between sites. Distributions are equal to platform+site, i.e., turnkey solutions. Content can be shared (migrated) between sites using an updated or different platform (with the same content modules, natch). A platform and site distribution is created from a .make and .info using Drush Make. The Profiler library is installed with the .make and uses a .info file to specify modules to be initialised, including site sections/etc. from the Features module plus configuration settings via the Strongarm module. Provision initialises a site on that platform and installs the platform+site in Aegir. Features and theme are stored using Git, --working-copy can be used to build a dev site then content can be migrated from live for testing. Dev platform is perfected, then rebuilt as live without --working-copy.
Barracuda box setup
- Create users, add to /etc/sudoers
- Change port in /etc/ssh/sshd_config, disable root login
- Open ports (ssh, 6667 for irc, 11370 for pgp keys)
- Give aegir shell access in /etc/passwd, password/keys
- Load Csf module in webmin; From local file > /etc/csf/csfwebmin.tgz > Install Module
Octopus
Like Barracuda, but a satellite Aegir instance with pressflow and other distros.
Aegir usage
Dev/production workflow guides
- Drupal deployments & workflows with version control, drush_make, and Aegir (mig5, Oct 28 2009)
- Using drush hosting-import to auto-create your platform node (and other entities) (mig5, Jan 11 2011) - Updated workflow on Aegir mailing list
- From Zero to Distribution using Features, Profiler, and Drush Make (dimitri, March 9, 2011)
Drush
- Drush - issues
- Drush.ws
- example.aliases.drushrc.php Drush context alias example
Drush Make
- Drush Make readme
- Drush Make theory for happy profile development
- Using drush_make to optimize workflow - Basics of make/profile management from mig5's first article
Provision
Distros and provision
Example make files
Profiles
- Developing installation profiles
- Install Profile Packaging
- Packaging a profile on drupal.org (make file -> install profile)
Profiler library
Features and settings
See also: Features
- Strongarm gives site builders a way to override the default variable values that Drupal core and contributed modules ship with. [1]
- Global variables