CivicActions Recommended Directory Structure For Drupal Hosting

At the Seattle Drupal User Group meeting tonight I gave a short presentation on the directory structure that we like to use at CivicActions. Some people asked if I would post my slide deck explaining the directory structure, so here it is. I may come back and flesh out this post explaining the structure more, but wanted to get the slide deck up for those who were listening on U-Stream or following on twitter, or actually in the room. As I joked at the end: I make no warranties expressed or implied, no joke.
AttachmentSize
Slide Deck Explaining CivicActions Directory Structure111.37 KB

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Wrapping my brain around nested symlinks

I've used symlinks on a one-to-one basis, but readily get lost when there are multiple levels, nestings, and retrograde links. I look forward to groping your directory structures in detail. Thanks Gregory. =)

two clarifications and one less symlink

Thanks for posting this, Gregory. A couple notes: The "nobackup/" directory is recognized by the CivicActions backup scripts to denote directories that have no custom code and can be skipped by the backups. You can skip this directory if you want. To get DEV, QA and LIVE sites to work, we have three doc roots per site: example, example-qa and example-dev. If you do something imilar, you might want to skip the link from 6 -> 6.11 and have e.g.,
public_html/example -> ../drupal/6.11
public_html/example-qa -> ../drupal/6.11
public_html/example-dev -> ../drupal/6.12
This makes it easier to upgrade e.g., your DEV site to 6.12 and test it before upgrading the LIVE site (as shown above). For building a multi-site setup in your Linux sandbox, see: the Drubuntu HOWTO.