MGI Installation Procedures

Jump to MGI 3 Macintosh OS X and Apache Installation Instructions

Jump to Macintosh OS X Permissions

Jump to MGI 3 Linux and Apache Installation Instructions

Jump to Linux Permissions

Jump to Suffix/Extension Mapping Instructions

Jump to Transferring MGI 2 Sites to MGI 3

Jump to Reinstalling or Upgrading MGI


MGI 3 Macintosh OS X and Apache Installation Instructions

  1. Upload the installer file to your server.
  2. Double-click the installer file.
  3. Follow the installer instructions. During the installation process, you can click the "Customize..." button where you will have the option of installing MGI without the Advanced Module and PHP.

    The MGI installer will automatically restart the web server when installation is complete. However, if the web server was stopped, MGI will not start the web server. To start the web server, enable web sharing via:
    System Preferences > Sharing > Web Sharing
    The MGI installer places the following files and folders on your server:
    /etc/apache2/other/mgi3.conf
    /etc/mgi
  4. Open your main Apache configuration file. The location of configuration file for the default Apple installation of Apache is:
    /etc/apache2/httpd.conf
    Check for the following Include directive:
    Include /etc/apache2/other/*.conf
    If the Include directive is not present, add it as shown to your Apache configuration file and save. Then restart the web server by turning web sharing off and on via the System Preferences:
    System Preferences > Sharing > Web Sharing
  5. Access the MGI server admin page in a web browser either directly on the server via:
    http://localhost/serveradmin.mgi
    the server IP address, for example:
    http://111.222.333.444/serveradmin.mgi
    or via any domain already configured in Apache, for example:
    http://www.domain.com/serveradmin.mgi
  6. Enter the default username and password when prompted:
    Username: admin
    Password: MGI
  7. Click the "Security" button and change the administrator username and password, then click "Save". You will immediately need to enter the new username and password to continue.
  8. Click the "Server Settings" button and enter your Serial Number and Authorization code in the fields. Then click "Save". If you are running a demo copy of MGI, you may skip this step.

Return to Installation Menu


Mac OS X Permissions

The most common issue you might experience with MGI on Macintosh OS X is permissions. If permissions are not set correctly, MGI may not be able to create files on the server.

By default, Apache runs with the permissions of the "www" user. Any files that will be creqated by MGI need to be owned by the "www" user or the apache configuration can be changed to run under a different user (not recommended).

If you are having problems creating files or folders via MGI, open Terminal and use the following command replacing the file path with the path to the folder containing your website(s):

sudo chown -R www /Path/To/Document/Root
The /Library/WebServer/Documents path is the default document root. You may change the command to reflect the location of your MGI files if you have a different configuration.

Return to Installation Menu


MGI 3 Linux and Apache Installation Instructions

  1. Upload the installer file to your server.
  2. Log in as "root" and use the following command to install the MGI RPM package (this command can also be used to upgrade MGI or reinstall MGI):
    rpm -Uvh InstallerFileName.rpm
    The MGI installer places the following files and folders on your server:
    /etc/httpd/conf.d/mgi3.conf
    /etc/mgi
  3. Restart the web server with following commands:
    service httpd stop
    service httpd start
  4. Open your main Apache configuration file. The location of configuration file for the default Linux installation of Apache is:
    /etc/httpd/httpd.conf
    Check for the following Include directive:
    Include conf.d/*.conf
    If the Include directive is not present, add it as shown to your Apache configuration file and save. Then restart the web server with following commands:
    service httpd stop
    service httpd start
  5. Access the MGI server admin page in a web browser either directly on the server via:
    http://localhost/serveradmin.mgi
    the server IP address, for example:
    http://111.222.333.444/serveradmin.mgi
    or via any domain already configured in Apache, for example:
    http://www.domain.com/serveradmin.mgi
  6. Enter the default username and password when prompted:
    Username: admin
    Password: MGI
  7. Click the "Security" button and change the administrator username and password, then click "Save". You will immediately need to enter the new username and password to continue.
  8. Click the "Server Settings" button and enter your Serial Number and Authorization code in the fields. Then click "Save". If you are running a demo copy of MGI, you may skip this step.

Return to Installation Menu


Linux Permissions

The most common issue you might experience with MGI on Linux is permissions. If permissions are not set correctly, MGI may not be able to create files on the server.

By default, Apache runs with the permissions of the "apache" user. Any files that will be creqated by MGI need to be owned by the "apache" user or the apache configuration can be changed to run under a different user (not recommended).

If you are having problems creating files or folders via MGI, make sure you are logged in as root and use the following command replacing the file path with the path to the folder containing your website(s):

chown -R apache /Path/To/Document/Root

Return to Installation Menu


Suffix/Extension Mapping Instructions

By default, pages with a ".mgi" and ".mgimodule" suffix will be processed by MGI. If you wish to process other files with MGI for all sites on the server (rather than on a site-by-site basis) use the following Apache configuration for each suffix. For example, to have MGI process ".htm" and ".html" pages, use these configurations:

AddHandler mgi-script .htm
AddHandler mgi-script .html

You may choose to place the configurations directly in your main Apache config file or save them in a separate file that is included in the main Apache config file.

For example, you might create a file named "suffix.conf" and place that file in a folder that is included in the main Apache config file. Any .conf file in the following folders are often included in the main Apache config file.

Macintosh OS X:
/etc/apache2/other
(check the main Apache config file for the include line - Include /etc/apache2/other/*.conf)

Linux:
/etc/httpd/conf.d
(check the main Apache config file for the include line - Include conf.d/*.conf)

Load your new configurations by restarting the web server

Macintosh OS X:
System Preferences > Sharing > Web Sharing

Linux:
On a command line, use the "service httpd stop" then "service httpd start" commands

You may also use suffix mapping on a site-by-site basis. Simply add the AddHandler configuration to the VirtualHost container. For example,

<VirtualHost *:80>
ServerName domain.com
ServerAlias www.domain.com www2.domain.com
DocumentRoot "/Users/Server/Sites/folder"
DirectoryIndex index.mgi index.mgi2 index.html index.htm
AddHandler mgi-script .htm
AddHandler mgi-script .html
</VirtualHost>

Return to Installation Menu


Transferring MGI 2 Sites To MGI 3

For those of you with existing MGI2 sites, you can easily transfer them to MGI3. The following procedure will give you the smoothest transition with the least downtime for the site.

  1. Turn off FTP access for the site on the MGI 2 server.
  2. Create a new sub-domain for the site in DNS (e.g., mgi3.domain.com) and point the sub-domain to the MGI 3 server.
  3. Configure the site on the MGI 3 server. Using the MGI Server Admin, create the domain preferences and include the domain AND new sub-domain in the virtual host list so that databases created using the sub-domain will be available once you move the main site to the MGI 3 server.
  4. Export all of the MGI 2 site's databases and transfer the site files and databases to the MGI 3 server.
  5. Use the sub-domain to create/import the databases and test the site on the MGI 3 server.
  6. If the site is working, change the domain's DNS to point to the MGI 3 server.
  7. Turn on FTP access for the site on the MGI 3 server.
  8. Create a redirect in virtual hosting on the MGI 2 server that redirects any incoming requests to the new sub-domain during the DNS propagation.
  9. When the DNS is fully propagated, remove the site from the MGI 2 server (we suggest you keep a backup!).

Return to Installation Menu


Reinstalling or Upgrading MGI

During the course of MGI development, PagePlanet Software releases updates to MGI which contain bug fixes and new features. You may also need to reinstall MGI on an existing server. Resintalling MGI will NOT overwrite your existing MGI data including preferences and databases. However, you should always backup your /etc/mgi/MGI-Files folder prior to reinstalling.

You can download installers from the PagePlanet Software web site or via the Version Tracker feature of the MGI Server Admin.

To upgrade MGI using an installer:

  1. Download the installer to your server.
  2. Run the installer according to the installation instructions above.
  3. Restart the web server (the MGI 3 Macintosh OS X installer will automatically restart the web server upon completion of the install).

Use these instructions to install an individual module.

  1. Download the module from the PagePlanet Software web site or via Version Tracker.
  2. Transfer the module to the server.
  3. Stop the web server.
  4. Replace the module in the etc/mgi/MGI-Files/Modules directory.
  5. Start the web server to load the new module.

or

  1. Under Module Management, unload the module you are replacing.
  2. Copy the new module into the etc/mgi/MGI-Files/Modules folder.
  3. Under Module Management in the MGI Server Admin, reload the module. The new module will be active on your server as soon as it is reloaded.

Return to Installation Menu


[System Requirements] [Installation] [Domain Configuration] [Server Admin] [Domain Admin] [Licensing]


[MGI Guides Main Menu] [Admin Guide Main Menu]