|laziness, impatience, and hubris|
A web application is a piece of software that runs through a web interface.
I do have multiple instances of my application on a server; each one runs for a specific customer on its own web server, using its own database and directory path.
If I were being awfully clever I could have one set of code and multiple sets of data .. but I don't have to be that clever. Yet.
Are you talking about a Class::DBI backend? I'm not even sure I know what that is. Can you explain?
After installing (which means I have read-only copies of all of the files), I check out individual files against a specific issue. That makes them writable.
When I'm done testing, I check everything in and ask the Release guy to make a version out of it. That gets passed to the QA person for a smoke test.
We've decided on three levels of builds, development builds (just for me), milestone builds (to mark the completion of a specific set of features and bug fixes) and releases (to mark a milestone that is sufficiently good to give to the customer).
If you have a designer that wants to edit templates, set them up with a userId on your source control system and show them how to check files out and then back in again. If you're on Linux and they're on Windows, perhaps have them ssh in to their home directory on a Linux system, use a command line interface to check files out, then ftp those files home for editting and testing. When they're done, ftp the same files back and check the files in.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds