Folders and subdomains

[KillBill]

Hello, I had my first installation of elxis only a short while ago. 
I was wondering... Is it better to install elxis in ROOT or in a folder (e.g /elxis)?
What is your suggestion? I have read somewhere that installing in a folder prevents you from playing videos. And now a tough question... Lets say that I want to have 2 sites, a test site and a production site ONLINE (e.g. http://test.mysite.com and http://mysite.com). Can elxis support multiple installations for different subdomains (multiple databases actually)? In other words can I have MORE THAN ONE configuration files? The same situation is when someone wants to have  http://mysite.com as he main site and for example http://shop.mysite.com, http://forum.mysite.com and so on for different purposes
Thanks in advance

[eliasan]

Hi,

The short answer is yes to all.

The decision on where to place your Elxis (root or folder) is primarly a decision based on other factors.
Basically design or strategy factors.

If the decision is up to me, I choose the "root" option.

It is true that if you place Elxis inside a subdirectory the videos that come with Elxis do not play right away. That can easily solved by editing the relevant autonomous pages and specifing the exact path to the .flv file.


"Can elxis support multiple installations for different subdomains"
Each Elxis installation will be separate from the others. Each Elxis will have its own configuration file.

[KillBill]

Thanks for the (fast) answer.
The first yes is clear, thank you.
About the second one, if I understood well, you are talking about 2 or more COPIES of elxis files (one for each subdomain) and 2 or more COMPLETELY different installations (running the install script more than once).
Something like this:
/ (root) ---> Corresponds to mysite.com and database elxis for example
/ configuration.php
/ globals.php
/ index.php
/ mainbody.php
..................
/ administrator (folder)
/ images (folder)
/ modules (folder)
..................
AND
/test ---> Corresponds to test.mysite.com and database test for example
/test/configuration.php
/test/globals.php
/test/index.php
/test/mainbody.php
..................
/test/administrator (folder)
/test/images (folder)
/test/modules (folder)
..................
In other words, having the same code twice, for each database and the databases have no connection (2 completely different sites)
Sharing the SAME CODE or SOME TABLES of the database (e.g users) is not supported, am I right?
Thanks in advance

[eliasan]

Sharing the SAME CODE or SOME TABLES of the database (e.g users) is not supported, am I right?

Yes you are right.
I do not see any need to be able to do something like that.
Maybe, apart from working as ASP (Application Service Provider).
But that is not among the goals of Elxis.

But maybe, I am not seeing the whole picture under your needs. So please enlighten us.

[KillBill]

Thanks once again!
How can I explain...
I am using Drupal CMS (www.drupal.org) for my site.
Drupal has some powerful characterisics, among which is "Multi-Site from single code base".
I liked elxis  so I installed it in a subfolder to play with 
Especially I liked it because it's developed by greeks 
Now the needs...
1) It makes sense to share Elxis code (might be over 20 MB!) for multiple installations. Only configuration.php needs to be different actually.
2) I don't know about ASP but this feature can be useful in many cases.
Lets say that someone's main site is mysite.com, with subdomains business1.mysite.com, business2.mysite.com and lets say personal.mysite.com: 3 databases, same system (elxis), same code.
If this extension is not among the goals of elxis, no problem.
I want to see elxis develop and be DIFFERENT (and much better) from mambo/joomla.
Continue your good work...
And thank you anyway.