Architecture / Installation

Architecture / Installation

Do all Tiki installations need to go in the 'public html' folder?

posts: 220 Ukraine


Should all Tiki installations be in the 'public html' folder? Since Tiki is a unique beast' in that everything is all packaged up together nicely, does this standard rule that web hosting companies recommend apply?

I did this with my first Tiki installation a long time ago, but didn't create a separate folder under 'public html' to put it in, so it's a mess! Than when it came time for my second Tiki instance (and 3rd, 4th, etc.), I created a folder outside of public html (since I though it would be an even bigger mess just dropping it in the 'public html' alongside the first installation) and put it there. All the instances (both inside and outside of 'public html') seem to work ok. (or could this be why I'm having issues with Composer?)

So, should I apply: 'if it ain't broke, don't fix it'?

Or do I need to move all the instances to new folders inside 'public html'? Will this break things?


posts: 8516 Israel

First, if your Tiki is published then it needs to be in a folder accessible through Apache2. (that’s why it is often public_html or htdoc or html... the default settings)

To answer a little widely and IMO, it depends of "external" factors (for what your Tiki is used and your IT Admin skills)

If this is intranet or your Tiki(s), meaning you of very few people use them, you can create inside public_html as many as Tiki(s) (subfolders) as you want and all should work fine (create corresponding files_gallery folders, etc).

To land on one of them, add the path to your domain. IE: https://www.mydomain.com/tiki21, https://www.mydomain.com/tiki22 etc.

If you know your way through server administration and how to set vhosts, then you redirect domain to different path than the default and set them part of the www-data group.

BUT I had to say that many things (libraries, software, packages, etc) work by default using Apache2 defaults and it can be a nightmare to adjust options and have them permanent (not reseted on server reboot).

And, if this is a public website you want it to be directly accessible with minimum of directories and navigation (https://www.mydomain.com) or eventually https://tiki21.domain.com