-
Notifications
You must be signed in to change notification settings - Fork 1
Project structure
jnand edited this page Oct 28, 2015
·
1 revision
SCM based on Git-flow
Branch membership is determined by a series of branch specific .gitignore files based on the configuration here.
- content
- all source data needed to "initialize" a
drush site-install
. At build time,drush make
will download this branch from a private server
- config/
- stage specific settings for capistrano, drush, and supporting services, along with templates.
- exports
- serialized config dumps from the database
- htdocs
- automatically created during local builds, or when a remote build is downloaded locally; is also ignored by git
- lib
- plugins and extension to dev tooling
- libraries
- contrib module dependencies
- modules/content
- content branch specific modules and data
- modules/custom
- custom modules not yet broken-out into their own projects, so are bundled with the profile here
- modules/dev
- developer tooling
- modules/features
- site specific configuration
- modules/migrations
- import/export migrations from older sites, also intra-release migrations between major versions
- modules/updates
- experimental meta-code for programmatically altering features
- patches
- build specific patches to core and/or contrib
- theme
- bundled themes