Links pulls it's config information from the links.def and links.cfg files.
Assuming you have the same category structure.
This is the line in each called file that tells links what paths to use:
Code:
require "admin/links.cfg";
If you want to run different configurations, you'll have to do some careful planning, but you can change the names of the files in the default ../links directory so rather than calling jump.cgi you call a_jump.cgi b_jump.cgi etc. Each group of files a_* b_* and a corresponding admin.cgi in the ../links/admin directory will use a different configuration file -- a_links.cfg a_links.def and a_category.def (unless the categories are the same.
Now, I haven't tested this, so there are probably minor things you'll have to work out, but that's the general idea.
The problem is that if you need different templates for the different databases, you are adding a layer of complexity that offers virtually no benefit over installing links several times.
There's a more elegant way if you seriously only want to run one set of scripts and several template directories that would use another passed variable to the script, and each script would use that variable in creating the configuration file to load --
Sort of like ../links/jump.cgi?ID=109&DB=a_
In the scripts, you'd pre-pend the DB filed to the links.cfg ($input_DB . 'links.cfg') test to make sure the file exists, and then load that config file.
You'd need only one set of scripts, but you'd want to keep the template files in different subdirectories so you could keep the same names in all the scripts.
Clear as mud???
This mission, should you choose....
