Jentla Wiki
Jentla Wiki > Jentla 1.5 "How To" Guides > How To Replicate a Site

How To Replicate a Site

Page last modified 12:31, 4 May 2011 by mihaela.pavel
    Redirected from "How To" Guides/How To Replicate a Site

    This section provides information on how to replicate an existing site.

    Copying websites is very easy in Jentla. There is no limit to how many times a site can be copied and held under the management of the one Jentla Manager, however to assist in creating large numbers of sites quickly, a Batch Replication process is included in Jentla. Distributed Site Replication is the foundation of the primary benefits of Jentla. It makes it hugely scalable and much easier to manage large numbers of sites.

    To replicate an existing site:

    1. Logon to Jentla Administrator (accessed via http://yourdomain.jentla.com/manager/administrator)
    2. Go to Jentla>Sites. The sites list will be displayed
    3. Mark the checkbox corresponding to the site to be replicated
    4. Choose Copy from the menu . This will replicate a selected site to a new Joomla site with it’s own database and filesystem. The Jentla extensions are automatically installed and the newly created site will be under the control of the Jentla Manager.
    5. The site configuration screen displays and now you have to configure the settings for the new site, as described in Site Configuration section below.
    6. Click Copy to perform the replication.

    Site Configuration

    When copying a site you have a set of mandatory settings to be configured, and also a set of additional ones.

    You can choose to configure nothing but the settings that are mandatory (and the Copy Database Content remains checked by default ). In his case the manager will try to resolve the URL of the new site to an IP. If the operation is successfull then the respective IP would be considered as the server where everything related to the new site will be performed (code copy, database installation, Apache configuration, and so on). If the URL is not resolved you'll get an error message.

    You are also able to configure manually some additional settings, as described below.

    Mandatory Settings

    • Site Name - The name of the new site. It must be unique
    • Alias -The alias for the new site
    • Site URL - Enter the new site URL. If the existing URL is http://mydomain.com/ Site/ the most limited change required is to change Site to another name. If copying the site to a new domain, add the new domain name here
    • New Site Directory Path - The server directory where the site files are located.
    • New Database Name - The database name for the new site. Each site has a separate database.
    • New Database User - The user name for the new site’s database
    • New Database Password -The password for the new site’s database.

    Optional/Additional Settings

    • Site Already Exists - If the code copying, database creation, database content import from the database of the source node (to be copied) and Apache configuration for the new virtual host were manually performed and you want only to register the new site together with its articles to the Jentla Manager, then you mark the Site Already Exists checkbox
    • Overwrite Site Directory Path - mark this if the destination directory already exists and you want to overwrite its content
    • cPanel - cPanel is a Unix based web hosting control panel that provides a graphical interface and automation tools designed to simplify the process of hosting a web site. Those settings make sense if either the source or the new site is on a server using cPanel.
      • Source Username - Username for the source cPanel access
      • Source Passord - Password for the source cPanel access
      • Source SSH Port - Source SSH port for host access
      • Destination Username - Username for the destination cPanel access
      • Destination Password - Password for the destination cPanel access
      • Destination SSH Port - Destination SSH port for host access
      • SSH Time Restricted
    • Server  - This section is only to be completed if copying the site to a new server. The default entry of localhost for the first four fields do not need to be changed if the new site is to be on the same server as the Jentla Manager
      • Source Hostname: The name of the server for the original site. Source Database Hostname
      • New Hostname: The server name for the server which is hosting the new site.
      • New Database Hostname: The name of the server where the new site’s database resides.
      • Database SuperUser Name: The name of the database user on the new site’s server with rights to create and define new databases.
      • Database SuperUser Password: The password for the database user on the new site’s server with rights to create and define new databases.
      • Replication-user: The name of the UNIX user with rights to log into the remote server via SSH.         
    • DNS - If the copy is to be to another server from the Jentla Manager, these fields must be completed. They define connections to the DNS system on the server where the new site is to be installed:
      • Name server Host: The name of the DNS server
      • Name server Fully Qualified Domain Name: The Fully Qualified Domain Name of the DNS server
      • Mail server Host: The name of the email server
      • Mail server Fully Qualified Domain Name: The Fully Qualified Domain Name of the DNS server
      • Named config file Directory Path: The actual DNS configuration file. Generally it is /etc/named.conf
      • Named config dir Directory Path: Directory where new zone files will be created. The directory is created by the installer into: /var/named/chroot/var/named/jentla. This path above is created by using the following variables:
        • --named-root-dir – the dir where bind is chrooted (/var/named/chroot). When reading the config, the script searches for the directory where zone files are being searched (/var/named)
        • --named-dir – the name of the directory to be used inside the previously found directory (jentla). So /var/named/chroot/var/named/jentla is derived from /var/named/chroot + /var/named + / + jentla
      • Named checkzone Directory Path - The directory where the checkconf utility is found. checkzone is the DNS tool for performing integrity checks on the DNS zone contents.
      • Named checkconf Directory Path - The directory where the checkconf utility is found. checkconf is the DNS configuration file syntax checking tool.
      • Named rndc Directory Path - The directory where the rndc is found. Rndc is a utility which allows command line administration of the named daemon.
    • Apache - If the copy is to be to another server from the Jentla Manager, these fields must be completed. They define connections to the Apache system on the server where the new site is to be installed.
      • Apache Config Directory Path - The directory for the Apache configuration file, httpd.conf. Defaults to /usr/local/jentla/etc/apache.
      • Apache Log Directory Path - The directory where Apache logs files are stored. Defaults to 'usr/local/jentla/logs.
      • Apache Root Directory Path - The base directory served by Apache, for example, /var/www/html
      • Apachectl Directory Path - The directory where apachectlc is installed. apachectl is a front end to the Apache Server. Defaults to /usr/sbin/httpd, if not provided.
      • Httpd Directory Path - The directory where Apache is installed.
    • Owner/Publisher Setup       
    • Copy Database Content - This is marked by default. Deselect only if you need to create a “bare-bones” Joomla site.
    • Sections/Categories - The Sections and Categories already defined on the current site are selected by default. It is possible to change the list of Sections and Categories to be created on the new site using the multi-option selector boxes.
    • Advanced - The advanced options define some higher level functions:
      • Source Directory Path - The directory on the server from which the site is to be copied. In some circumstances, a differing Joomla filesystem may be required to be copied together with the existing Joomla database.
      • Global Users - If Global Users is selected, users created on the new site will be able to log into other sites which also have this setting selected. So if desired, the same user can log into multiple websites without going though the process of creating a new user in each site.
      • Publish Article - This defines whether the articles are published in the advanced Jentla format or if they are published in standard Joomla format. Jentla provides a publishing workflow which can only be used for a site if the Jentla format is selected.
      • Google Analytics - To assist in collecting website statistics, when a site’s Google Analytics tag is added here, it is placed correctly on each page of the website. The signup for Google Analytics is here: http://www.google.com/analytics/
      • Temporary Directory path - The temporary directory for the Jentla installation script. It defaults to /usr/local/jentla/tmp In some circumstances, a different temporary directory may be defined. By default, this setting is left empty.
      • Google Map Key - This is for the site Google Maps API Key if Google mapping is in use on the site. The signup for the key is done here: http://code.google.com/apis/maps/signup.html
    • Site Specific Values
    Powered by MindTouch Core