Single installation of gallery on a webserver but different

Clear :smile:

While it's possible, it's better to let each user have his/her own personal gallery code. Here's why:

-If you centralise it, you need to make a directory full of symlinks to the original files, because the "config.php" and ".htaccess" files need to be unique to each user, but still need to be in the same directory as the other files. This is messy, but it *will* work. Then, if you ever update the code, there might be missing symlinks if new files appear. Not fun.

-If someone wants to edit the html_wrap or css files, or say, edit the PHP, then the issue of overwriting the files comes up. Again, easier if you have your own copy.

-The Gallery code takes up a few hundred kilobytes... comparable to a couple of photos. It's certainly not going to save much hard drive space.

I would recommend (certainly from a client's point of view) that rather than use a centralised codebase, you instead let each user have his own code, but you officially make your service "Gallery Friendly"... that is, you have working centralised NetPBM, ImageMagick, Jhead, Unzip and ZipInfo binaries, and provide convenient links to the Gallery code, or support/instructions for installing it. (You could even have the "gallery" and "albums" directories created automatically when a new client signs up and selects an "install gallery for me" option). This gives the client a little more flexibility.

But I'm sure someone can argue the opposite case :roll:
(My 2¢)
-Beckett (beck@beckettmw.com)

Hey I just saw on muggles website, he is offering a hack for just this.

worth a look

<!-- BBCode Start --><A HREF="http://www.muggles.gocompupro.net/index.php" TARGET="_blank">http://www.muggles.gocompupro.net/index.php</A><!-- BBCode End -->