Loading...
 
Architecture / Installation

Architecture / Installation


Same Tiki, different DB?

posts: 4
I'm using Tiki to create a learning environment for small groups. They need to be completely separate... but the base format, look, modules, templates etc. need to be the same. Is it possible to run two different databases off the same installation of Tikiwiki?
posts: 15

Just a quick question to disambiguate your query a bit. What would be the deciding factor upon accessing the site as to which of the two databases is to be utilized for the session?

If it is a manual decision to be made by the user upon accessing the site, you might consider utilizing two separate installations within the same site. Either sub1.domain.com and sub2.domain.com being selected from domain.com or going from domain.com to domain.com/site1 or domain.com/site2 could be used for this purpose, each with their own database.

HTH and good luck!

posts: 4

My ideas have moved on since posting this... I've learned that all the styling except the base theme is in the databases, not in the site files. So it makes sense to set up separate instances.

However migrating the right information to the new instance database is tricky. There are 224 db tables, some of which have user-specific information (which must be cleaned out) and some of which contain settings that determine the look and feel of the site (which must be kept). I would love to find a place where there is a listing of the 224 tables and their contents (or even some of them!) to help me move through the content quickly, without individually inspecting each one.

No need for a reply, unless you know where such a listing could be found, or unless you have a brilliant idea that solves my difficulty another way!

posts: 4
Oh and I forgot to say a big THANKS for reading my original post and taking the time to think and reply. smile
posts: 15

Very happy to help when I can! I have no idea where such a listing might be found if there is one, as I just discovered tiki for myself 2 days ago. razz

This idea might help: Set up one site to have all of the shared features (style, etc) the way you want them, then copy everything to a second installation by doing a db dump. At this point you can set each up with it's own individual data. Note that two separate databases would require two separate registrations per user if they are to have the same user base.

HTH! :-)

posts: 15
You might check out Intertiki for how to share a user base if that is what you want. As I understand it so far, it sets one of the sites as a master (server) and others as slave (client) for user registration/login purposes. In tikiwiki 6, they plan to have user registration possible from slaves, which makes me believe it is only possible from the master at the moment. This will make more sense once you read that page.
posts: 4
What I want is the opposite.... same tiki, two completely separate user bases. Intertiki is two tikis, same user base.

posts: 15

Hi again, Clippership! Once you mentioned keeping the user bases separate, I had to wonder if I really understood your need for two installations. question

Would it be better to use Groups within one install with different access via Permissions? You could then use Categories to keep two separate sets of data for the two groups within the single database.



Upcoming Events

1)  18 Apr 2024 14:00 GMT-0000
Tiki Roundtable Meeting
2)  16 May 2024 14:00 GMT-0000
Tiki Roundtable Meeting
3)  20 Jun 2024 14:00 GMT-0000
Tiki Roundtable Meeting
4)  18 Jul 2024 14:00 GMT-0000
Tiki Roundtable Meeting
5)  15 Aug 2024 14:00 GMT-0000
Tiki Roundtable Meeting
6)  19 Sep 2024 14:00 GMT-0000
Tiki Roundtable Meeting
7) 
Tiki birthday
8)  17 Oct 2024 14:00 GMT-0000
Tiki Roundtable Meeting
9)  21 Nov 2024 14:00 GMT-0000
Tiki Roundtable Meeting
10)  19 Dec 2024 14:00 GMT-0000
Tiki Roundtable Meeting