Workflow improvements on server, SVN repository structure

From the Agaric archives way back in April:

1. How to set up - or automatically create - "site@example.com" e-mails.

2. Automatically "svn update" on specific test-sites directories (or would this have to be for all of test-sites, and so we need a different directory structure?) upon checking in a change to a site theme.

Drupal does not find example.com folders that are inside subdirectories.

So Dan, what that means is we have to decide whether we want a possible
hassle in checking out symlinks (essentially creating them outside version
control), or if we want to remove our project structure in the repository
and store example.com, example.org, bush907.net, jandsproperties.com all in
one directory.

My preference would be to have these in their own directories, go back to
Stefan's projectname/example.org/trunk (or tags) layout, and checkout
symlinks individually.

However, if the answer to automating test-site/example.org svn updates
number two requires the flat directory structure without distinguishing
projects, that's what we'll do.

Of course, if it would be possible to make a script that magically does both...

--below:

Me and
Stefan

My preference would be to have these in their own directories, go back to

Stefan's projectname/example.org/trunk (or tags) layout, and checkout
symlinks individually.

With the flat directory hierarchy, i.e. drupal/example.com/trunk, we can
have the symlinks in the repo, too, and check out all sites or
individual ones without much scripting. In that case I would opt for one
sites directory to replace the projetc dirs. Then I wouldn't have to
script anything.

However, if the answer to automating test-site/example.org svn updates
number two requires the flat directory structure without distinguishing
projects, that's what we'll do.