Wiki Folder Location
Is it possible to install the wiki script in an inner folder. To illustrate this, the main folders of my websites, for the major categories are placed after the /public_html/:
///public_html/...
(equivalent to the ///www/... in other webhosting services)
right now, the tikiwiki that I installed and am experimenting with was placed in the root folder
///public_html/wiki/
However, I may end up installing quite a number of "wikis" so that there will be dedicated databases for each of the major categories in my website.
My question is: Can I do this?
.../public_html/cms_wiki/category_name/...
where the content of "category_name" actually corresponds to a complete files in a download "tiki_wiki"software. To elaborate further, let us say, a complete version tikiwiki1.9.1 was uploaded to the main folder "cms-wiki", then after the download, that complete "tikiwiki1.9.1" folder was renamed "ecosystems" because all the contents of the tikiwiki database will be related with "ecosystems".
Similarly, another complete version of tikiwiki1.9.1, will be renamed "arts" for a tikiwiki database devoted exclusively for the "arts", etc., etc., etc.
The reason for this is that each of the major categories in my website would eventually contain gazillions of files (text, photos, directory links, etc.) and to lump them all the categories in one single "tikiwiki" database would create a very bulky database — a bandwidth hogger that will not be liked by my current webhosting service. As it is, they already moved my website to another server, because there are times when the traffic "gets a blip" — affecting the performance of other sites.
The question I have are:
(1) Will this work if the tikiwiki script is not placed in the root folder?
(2) How will the speed of info retrieval be affected by this choice?*
(3) Is there a mechanism to integrate eventually the various information found in the different databases, e.g., during a search using the search function provided in the "tikiwiki"?
My other concern about this "solution" to solving database bulkiness is that the complete tikiwiki CMS script is several MB, so that installing 10-100 of such will occupy so much space. I believe a program, "gallery" in its more advanced form is able to manage a number of databases — in fact, connect to remote databases, to access "upload" images temporarily — all from a single program.
I am new to tikiwiki — so I am not sure if any such feature is under development.
Thanks.
cgc0202
___
N.B.* I am testing some sections of the tikiwiki website for example, and there are sections that they more time to load.