We implemented three instances of Plogger against three separate databases in order to allow separate volunteers to update discrete sections of our Web site. Our host only gives us ten databases total. I am now wondering if separate instances and separate databases were both necessary. So here are the questions:
Can a single instance have different passwords set up for different sections of a Web site?
Can multiple instances use a single database?
Each year we might add up to 30 galleries of 25 photos each. Our host has a maximum database size limit of 650MB. Is this a problem?
In general, how much database space does Plogger use? Is it calculated per gallery or per image or some other metric?
Thanks for your help and your superb gallery software.
A single install (which consists of database tables and source files) can only have one password and one user, we do not have any sort of user system setup for this.
Multiple instances can use a single database, but you have to modify a few variables in the code. There is a variable called $TABLE_PREFIX that occurs several times in the code (we have since reduced that occurance to one), but in Beta 2.1 you have to replace the value of $TABLE_PREFIX = "plogger_" in all files where it occurs. You just need to changed "plogger_" to something else before installing and Plogger will work with these tables "yourprefix_pictures", "yourprefix_albums", etc. I think there is more information on how to do this here on the forum, try searching for "TABLE_PREFIX".
The database size is something you shouldn't really worry about. Everything is normalized and the data rows themselves take up very little space in comparison to the actual image files. You can usually view how much space your using in the database through your ISP control panel, but I sincerely doubt you would be able to top 650MB.
One thing Mike didn't make explicit is that Plogger doesn't store the images in the database, but in the filesystem; this should significantly contribute to you not exceeding your DB limit. Plogger uses the database to store metadata pertaining to each image, but not the image itself.