Here is some documentation:
Overview: http://prezi.com/nqm6g-grqniq/cornell-university-library-drupal-setups/
Scripts & README.txt: https://svn.library.cornell.edu/cul-drupal/drupal_6/scripts
Migrate module: http://drupal.org/project/backup_migrate
Drush: http://drupal.org/project/drush
Drush Make: http://drupal.org/project/drush_make
What is below here is obsolete. We're on a different server now with a different organization and workflow.
This describes the organization of the Drupal sites DLIT has on our test server.
...
- ask Enrico Silterra to do the tasks for setting up a new site
- set up subdomain (eg. mysite.test1.library.cornell.edu)
- set up directory structure on libdev (eg. /webvision-dev/apache2/drupals/mysite)
- create mysql database and user for Drupal
- install drupal core files and doctor sites/default/settings.php to include user/password/db for this site
- create subversion directory for the site under Drupal-Sites
- get CUWebAuth set up if necessary
- go to the site and run the Drupal install (eg. http://mysite.test1.library.cornell.edu/install.php)
- you may need to update the Drupal core if it's out of date
- check out Drupa-Sites/mysite.library.cornell.edu from SVN
- add whatever modules you need to site.manifest
- webvision.manifest should only have modules/cul_common (other webvision modules are out of date)
- check in your changes to Drupa-Sites/mysite.library.cornell.edu
- do the 'Update a site on the test server' procedure
- add a line to /webvision-dev/apache2/drupals/crons/testcrons
- (eg. /opt/common/bin/wget -0 - -q http://mysite.test1.library.cornell.edu/cron.php >/dev/null 2>&1 )
...