- Builds (Make files, profiles and other support files for building a fully functional Drupal file structure), are stored in /var/aegir/builds on suarit01linux. Builds create platforms in Aegir.
- Builds should be checked out from git repos so they are easily updated
- Platforms are fully functional Drupal file structures which become multisites for one or many web sites in Aegir.
- Platforms are stored in /var/aegir/platforms on suarit01linux.
- Builds in /var/aegir/builds/ should be named lowercase and separated by hyphens. The name should be short and descriptive (ex: /var/aegir/d7-sandbox/d7-sandbox.make).
- Platforms:
- Publish Path: /var/aegir/platforms/ (ex: /var/aegir/platforms/d7-sandbox-suarit02linux. The server name is required because a platform can only live on one remote Aegir server, so you may have several platforms which are identical and deployed on differente remotes.
- Name: Friendly name for the platform (ex: Drupal 7 Sandbox)
TODO: Probably need to add platform build numbers to naming which correspond to git tags for platform migrations/upgrades. Thoughts?
IRC comments on the subject:
mig5:
shrop: i use 'platformname_build_20110607' or sometimes I drop the build. And I use the /var/aegir/builds as written there (I might've coined that ? :) )
[08:34a] mig5:
sometimes i add a digit to the build date in case i build multiple times a day. eg 2011060701. in this respect i treat it like the serial number in a dns zone file
[08:35a] mig5:
a git tag sounds smarter :)
joestewart:
shrop: good stuff. We've been append mmdd without the year. And rarely have added -n for multiple per day. I have been referencing gitweb urls as it is easy to get separate branches and tags. But will think about the builds directory working copy. I noticed mig5 uses the .build file extension too.
joestewart:
shrop: Also I usually don't use a "friendly" platform but instead the same as the directory name. Props to Dane Powell for http://drupal.org/project/hosting_platform_pathauto as I now only enter this once.