Gallery rocks, 'nuff said.
I only became aware of Gallery at LCA '04, when Rasmus mentioned it in his PHP tutorial. I immediately chucked it on my webserver and threw out the dodgey thumbnailing-on-the-fly PHP code I'd written, and I've never looked back.
A little while before I reinstalled daedalus in the June holidays, my friend Alison, who is over in the UK at the moment, asked me for recommendations on online photo gallery websites. I told her she could use my Gallery after I'd reinstalled daedalus, but what I wanted to do was rather than have all her photos lumped in with mine, was to have a separate instance of Gallery with individual albums for all my friends, similar to what I'd seen done elsewhere.
Now I'd looked into running multiple instances a few times (I really didn't want to copy the static Gallery code to a second directory, because that would remove the benefits of security updates and whatnot, and was generally not the elegant solution I desired), but the FAQ didn't mention it, and Googling for such a generic term wasn't turning up much either.
So tonight I finally sat down and looked at the code, and it was remarkably
simple. The way I wanted to do it was define an environment variable on a
per virtual host basis, which specified where to look for the config.php
file. I added an
SetEnv directive to the vhost for the new
Gallery instance, and only had to patch one file to add some additional
logic. If I can get the Gallery upstream to accept the patch,
it'll all be good. At the moment, a new Gallery package would clobber
everything, which is exactly what I'm trying to avoid.
It's still not ideal though, as when you first rock up to the new instance, it creates a default user database, with no users, and I've got no idea how to add new users. I ended up copying the user database from my other instance to bootstrap things.