Deletions are marked like this. | Additions are marked like this. |
Line 13: | Line 13: |
All of the examples below assumes that the primary and secondary instances are '''centos1.tibi1959.hu-dev1''' and '''centos1.tibi1959.hu-dev2''', and the primary and secondary main directories and databases are '''linthal114dev1''' respectively '''linthal114dev2''''. |
|
Line 17: | Line 19: |
Checkout to primary system first as usual (assumed CVS user: ''ntibor'', main development directory: ''/var/www/html/dev'', apache user: ''apache'', site: ''linthal'', instance: ''centos1.tibi1959.hu-dev1''): {{{ cd linthal114dev1/app/etc ./checkout.pl -v -r 114 -u tibor -d /var/www/html/dev -w apache linthal centos1.tibi1959.hu-dev1 }}} Assumed that the secondary system is on the same machine, use the option '-l dev1', which creates links for '''app''', '''lib''' and '''cfg/.../site''' directories to the primary system instead of checkout them, to allow that you will be not confused with the question:'what was changed where?'. Omit the option ''-l'' If you install the secondary system on a separate computer. {{{ cd linthal114dev2/app/etc ./checkout.pl -v -l dev1 -r 114 -u tibor -d /var/www/html/dev -w apache linthal centos1.tibi1959.hu-dev2 }}} |
Setting Up a Dual DrawMGT System
Contents
Introduction
A dual DrawMGT system contains an internal (secure, primary) and and external (shared, secondary) systems. The systems are basically independent from each other, but synchronized.
Setting Up a Dual Development System
The internal and external systems can be in the same computer on a development system. In that case the secondary system's app, lib and cfg/.../site directories can be linked to the primary system's directories.
All of the examples below assumes that the primary and secondary instances are centos1.tibi1959.hu-dev1 and centos1.tibi1959.hu-dev2, and the primary and secondary main directories and databases are linthal114dev1 respectively linthal114dev2'.
Create the instance settings for the two systems first, e.g. centos1.tibi1959.hu-dev1 and centos1.tibi1959.hu-dev2.
Checking Out The Development System
Checkout to primary system first as usual (assumed CVS user: ntibor, main development directory: /var/www/html/dev, apache user: apache, site: linthal, instance: centos1.tibi1959.hu-dev1):
cd linthal114dev1/app/etc ./checkout.pl -v -r 114 -u tibor -d /var/www/html/dev -w apache linthal centos1.tibi1959.hu-dev1
Assumed that the secondary system is on the same machine, use the option '-l dev1', which creates links for app, lib and cfg/.../site directories to the primary system instead of checkout them, to allow that you will be not confused with the question:'what was changed where?'. Omit the option -l If you install the secondary system on a separate computer.
cd linthal114dev2/app/etc ./checkout.pl -v -l dev1 -r 114 -u tibor -d /var/www/html/dev -w apache linthal centos1.tibi1959.hu-dev2