[development] Local repository best practices
drupal-devel at webchick.net
Tue Sep 9 20:15:17 UTC 2008
I've been doing some research for a client on best practices surrounding
repository management, and wanted to take this discussion to the
developer list and see if we could get some general consensus, and
document it as a best practice in the handbooks.
I found a bunch of discussion on this topic:
Most of these discussions are around Drupal *shops* who setup SVN to
manage the development of their clients' sites, or who host their
clients' Drupal sites and manage updates via SVN.
However, I'm curious what people generally use in terms of repository
structure/deployment strategy *after* development is complete, and they
hand the site over to the client so that they can be self-sustaining? It
doesn't really seem like they need a vendor branch with various versions
of Drupal and contributed modules. The repository is around just their
We typically do something like this:
This is where "crazy" development happens that will break other stuff.
This is where deployments go. Whenever we move a deployment to prod,
we tag it first so that we can see a historical record of things that
were put 'live'
The latest development code in preparation of deployment.
Should be kept stable at all times. Minor fixes can go in here, but
major ones (particularly porting tasks) get a dedicated branch.
Beneath each directory above is something like this:
- /www: Drupal files, modules, etc.
- /assets: Things like wireframes, TinyMCE .zip files, and anything else
that shouldn't be web acessible.
- /db: Database backup files
What are other people doing for this use case?
More information about the development