| Author | Post |
|---|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 603 |
|
Posted: Thu Jun 30th, 2005 05:00 pm |
|
Step-by-step instructions for creating one installation on an Apache server that can run child installations in other domains on the same server.
This configuration allows a child installation in one domain to use the code files in a parent installation on the same physical server. The child installation contains only the wrx.cgi and a set of data files that are unique to the domain that it is installed on.
Security
The concept requires a Perl script in a child domain to be able to read files in the parent installation in a different domain. On most Unix servers (Plesk in particular) it is a security violation for a script in one domain to read files in another domain. Look at the permissions on the domain's root folder. If it is 751 or 750 then a script outside of that domain is not allowed access to the domain. To make this kind of EditWrx multi-domain installation work you must change the permissions on the domain's root folder to 755. Doing so will allow a script from a different domain to read any file inside the domain.
If you have sensitive files in the domain that should not be readable by scripts in other domains you can do one of two things:
- Place the sensitive files in a folder inside of the domain and give that folder the same permissions as was originally set for the root folder.
- Create a fully qualified sub domain and place only the EditWrx installation in that sub domain. The sub domain will need to resolve for browser access and it must have it's own domain root folder (which will have the 755 permissions).
Parent Installation
Install EditWrx on the parent domain. Get that installation running properly. For 6.04+ installations no changes are necessary.
Child Installation
Create a child installation in another domain on the same server. On the child domain install only the files:
/editwrx/wrx.cgi
/editwrx/library/data/config.txt
/editwrx/library/data/users.txt
/editwrx/library/data/changelog.txt
/editwrx/library/data/sessions.txt
On wrx.cgi change $child=0; to $child=1; Then edit the URLs and PATH in the variables
$url_to_library = "url_to_library_in_parent_domain";
$url_to_ikons = "url_to_ikons_in_parent_domain";
$path_to_library = "path_to_library_in_parent_domain";
to reflect the locations of those folders in the parent domain. Use absolute URLs and PATH.
Open /editwrx/library/data/users.txt and replace everything with only admin=start When the child domain user first logs in they need to login as "admin" and use "start" as the password. They will then be required to enter a different password for "admin".
Open /editwrx/library/data/config.txt amd remove any values for
$disallow
$url_to_common
$DOMAIN_LICENSE
You will need to generate a DOMAIN_LICENSE for the child installation using your Developer KEY.
Automatic Updates
Version 6.04+ automatically knows if the installation is a child installation. If it is a child installation all capability and options for doing automatic updates are voided. If it is the parent installation, automatic updates are available in Site Parameters and User Setups in the Admin Control Panel.
Last edited on Mon Jul 4th, 2005 07:32 pm by Keith |
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 603 |
|
Posted: Sat Jul 2nd, 2005 12:44 am |
|
The wrx.cgi before 6.04.050628 & 6.04.050629 had the wrong variables for $path_to_data
Either change
$path_to_data = "$path_to_library/data";
to
$path_to_data = "$path_to_domain/$editwrx_folder_name/library/data";
or download the 6.04.050701 wrx.cgi zip
http://editwrx.com/download/zip/wrxcgi.zip
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 603 |
|
Posted: Thu Feb 23rd, 2006 08:16 pm |
|
Please see the 6.11.060223 version changes in the Important labeled topic of the same name
http://www.editwrx.com/forums/forum2/132.html
Last edited on Sun Feb 26th, 2006 09:10 pm by Keith |
Mark
Member
|
Posted: Sun Feb 26th, 2006 09:00 pm |
|
Please see the 6.11.060223 version changes in the Important labeled topic of the same name above
Sorry Keith - can you explain please - where are they?
Thanks
Mark
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 603 |
|
Posted: Sun Feb 26th, 2006 09:12 pm |
|
Sorry, when I first wrote that I had not yet posted the new entry and didn't have a url for it yet. Here it is.
http://www.editwrx.com/forums/forum2/132.html
|
Mark
Member
|
Posted: Sun Feb 26th, 2006 09:25 pm |
|
LOL - okay, I know I'm having a bad day....
but there's nothing in that topic about vsn 6.11.x - is there anything new in 6.11 regarding parent/child set-up?
Thanks
Mark :)
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 603 |
|
Posted: Sun Feb 26th, 2006 11:42 pm |
|
LOL! No Mark. I'm the one having the bad day! The version number over there is supposed to be 6.11+ not 6.10
The main difference is that a child installation can use the license from the parent installation. This lets you precode the parent license in config.txt files for child installations so child installation creation can be automated.
|
Mark
Member
|
Posted: Mon Feb 27th, 2006 01:09 am |
|
Thanks Keith - here's hoping tomorrow is a better day for both of us!!
Regards
Mark :)
|
Current time is 05:07 pm | |
|
