Get a list of modules. What I did was use ls mysite/all/modules/ as a template and removed drush from that list.

./drush dl admin_menu advanced_help date drupalforfirebug drush_mm \
event flag og pathauto smartqueue_og token votingapi adminrole \
cck devel drush_sm fivestar nodequeue \
og_vocab rules timeline views wysiwyg

Drush nicely downloads all given drupal projects.


Project admin_menu (6.x-1.4) downloaded to /home/clemens/htdocs/drupaljam.build2be.com/www/sites/all/modules/. [success]
...

Get drush and test it.

mkdir drupaljam.build2be.com
cd drupaljam.build2be.com/
wget http://ftp.drupal.org/files/projects/drush-All-Versions-2.0.tar.gz
tar xzf drush-All-Versions-2.0.tar.gz 
rm drush-All-Versions-2.0.tar.gz 
./drush/drush

Get drupal without thinking.

clemens@clemens-laptop:~/htdocs/drupaljam.build2be.com$ ./drush/drush dl drupal
Project drupal (6.12) downloaded to /home/clemens/htdocs/drupaljam.build2be.com/.  
mv drupal-6.12 www

I want drush inside my sites/all/modules tree.


mkdir www/sites/all/modules

This book is about what step I took to prepare the (temporary) demo site and what my presentation is about.

This is now just a link container ... need to spend some time on this once.

http://www.ibm.com/developerworks/library/os-php-designptrns/?S_TACT=105...
http://www.ibm.com/developerworks/opensource/library/os-php-designpatterns/

Trying best practices I occasionally move the files directory from DRUPAL_ROOT/files/my-site.com to DRUPAL_ROOT/sites/my-sites/files

Doing this has some implications for the files table content. All file-path are pointing to the wrong location.

Quick solution for this is an mysql replace update query.

select replace(filepath, 'files/my-site/', 'sites/my-site/files/') from files;
# update files set filepath=replace(filepath, 'files/my-site/', 'sites/my-site/files/')"

Or through drush

So you finally have your own svn repository. But you need to use external code as well. And you want to keep track of changes in those external code. Then use svn:externals. This tells subversion there are external subversion repositories destined to blend into the current folder. I learned this from a script thanks to Wim Leers

First let's create an externals to a repository in the current directory.

svn propedit svn:externals .

If this fails configure an editor like this

export EDITOR=vi

Setting up an apache based subversion needs a little more work then doing it with a plain or svnserve setup.

My steps are described here and executed on two computers.

Create your repository

# the switch --fs-type fsfs is the default 
# but I was a little worried of getting the bdb file system
svnadmin create --fs-type fsfs demo

Make sure apache is capable of reading the repo and other cannot

# /var/lib/svn is owned by root so let www-data (apache) access the repos dir.
chmod o+rx /var/lib/svn
chmod -R o-rwx demo
chown -R www-data:www-data demo

These pages describe my interpretation of a subversion setup.