D
Debbie Sontag
Guest
Hello all!
Because there are so many questions being posted about creating two instances of Dadabik to view/manage one database, I've put together a quick, step-by-step tutorial for you to follow.
1..........
The usual schtick -- you have to have a database WITH tables already created to use Dadabik.
2..........
Install your first instance of Dadabik using the default Dadabik table prefixes contained in the CONFIG.PHP file (last two variables in the file).
http://your.domain.com/dadabik/install.php
If you want things to look the same in both installations like headers, footers, logos, etc., you can make those changes now so that you only have to make them once. OR... You can worry about prettying it up later.
3..........
Copy your ENTIRE Dadabik folder into a new folder you wish to use for the second instance:
http://your.domain.com/dadabik/ <-- all contents copied to:
http://your.domain.com/dadabik/admin-dir-name/
4..........
Open CONFIG.PHP from the /dadabik/admin-dir-name/includes/ folder and change the table prefix and table list name in this file to something like:
dadabik_admin_
and
dadabik_admin_table_list
It does not matter what your prefixes are -- just so long as they are DIFFERENT from the first install prefixes.
5..........
Now, install your second instance of Dadabik:
http://your.domain.com/dadabik/admin-dir-name/install.php
6..........
This will create additional tables with your admin prefix for all your original Dadabik tables also. You should remove them by going to the admin interface for the second instance you just installed and uninstall those tables.
For this example, we'll assume you used the following:
1st install: "dadabik_" table prefix with "dadabik_table_list" table list name
2nd install: "dadabik_admin_" table prefix with "dadabik_admin_table_list" table list name
In the admin for the 2nd install (/dadabik/admin-dir-name/admin.php), "uninstall" each table you see beginning with "dadabik_admin_dadabik_".
7..........
Now you can manage both instances independent from each other through:
http://your.domain.com/dadabik/admin.php
and
http://your.domain.com/databik/admin-dir-name/admin.php
Beyond this, you can add pasword protection to your admin area through .htaccess (do a search in the forums for this or goog it for tons of info) or other methods.
In my case, I've always made the admin directory something that users would not be able to easily guess to make things easier on the DB admins. I just provide the admins for the DB the URL and advise them not to pass that info out unless they want others mucking with their data and it's worked very well.
It's really a personal preference how you want to manage the security end of things.
Hope this helps everyone!
Debbie
Because there are so many questions being posted about creating two instances of Dadabik to view/manage one database, I've put together a quick, step-by-step tutorial for you to follow.
1..........
The usual schtick -- you have to have a database WITH tables already created to use Dadabik.
2..........
Install your first instance of Dadabik using the default Dadabik table prefixes contained in the CONFIG.PHP file (last two variables in the file).
http://your.domain.com/dadabik/install.php
If you want things to look the same in both installations like headers, footers, logos, etc., you can make those changes now so that you only have to make them once. OR... You can worry about prettying it up later.
3..........
Copy your ENTIRE Dadabik folder into a new folder you wish to use for the second instance:
http://your.domain.com/dadabik/ <-- all contents copied to:
http://your.domain.com/dadabik/admin-dir-name/
4..........
Open CONFIG.PHP from the /dadabik/admin-dir-name/includes/ folder and change the table prefix and table list name in this file to something like:
dadabik_admin_
and
dadabik_admin_table_list
It does not matter what your prefixes are -- just so long as they are DIFFERENT from the first install prefixes.
5..........
Now, install your second instance of Dadabik:
http://your.domain.com/dadabik/admin-dir-name/install.php
6..........
This will create additional tables with your admin prefix for all your original Dadabik tables also. You should remove them by going to the admin interface for the second instance you just installed and uninstall those tables.
For this example, we'll assume you used the following:
1st install: "dadabik_" table prefix with "dadabik_table_list" table list name
2nd install: "dadabik_admin_" table prefix with "dadabik_admin_table_list" table list name
In the admin for the 2nd install (/dadabik/admin-dir-name/admin.php), "uninstall" each table you see beginning with "dadabik_admin_dadabik_".
7..........
Now you can manage both instances independent from each other through:
http://your.domain.com/dadabik/admin.php
and
http://your.domain.com/databik/admin-dir-name/admin.php
Beyond this, you can add pasword protection to your admin area through .htaccess (do a search in the forums for this or goog it for tons of info) or other methods.
In my case, I've always made the admin directory something that users would not be able to easily guess to make things easier on the DB admins. I just provide the admins for the DB the URL and advise them not to pass that info out unless they want others mucking with their data and it's worked very well.
It's really a personal preference how you want to manage the security end of things.
Hope this helps everyone!
Debbie