-
Notifications
You must be signed in to change notification settings - Fork 36
install detailed
This is the detailed installation guide for Melody. Simpler guides for those comfortable performing these types of installations are also available: Quick Install via FTP or Quick Install via SSH.
First, check Getting Ready to Install for needed tools and preparatory steps and verify System Requirements are met.
Installation requires three major steps. Here’s the basic process:
- Install New Version
- Configure New Version
- Initialize Database
This guide assumes that you have FTP, shell, or some other form of access to the server.
Throughout this guide two terms are commonly used:
-
$M_HOME
is used to refer to the application directory -
$M_STATIC
is used to refer to the static directory
-
Download the Latest Release from openmelody.org
Download desired version, or copy url if using SSH to install.
-
Move Release to the Server
Two paths to do this based up on what level of server access is available:
- Via FTP - download locally, un-compress, then upload parts via FTP
- Via SSH - upload via SSH, un-compress on the server, move directories
Via FTP
- After downloading release to your local machine, double-click the melody-v1.x.zip (or melody-v1.x.tar.gz) archive to un-compress.
- Upload (or move) the static directory (melody-v1.x/mt-static) via FTP to the web root of the website.
- Upload the application directory (melody-v1.x) without the static directory (MT-5.0-en/mt-static) via FTP to the cgi-bin directory.
- Rename the application directory from “melody-v1.x” to “m”.
Via SSH
-
Login to the server and cd to the cgi-bin directory.
-
Copy release to the server. * Command line using wget:
$ wget http://github.com/openmelody/melody/zipball/master
* Command line using curl -LO $ curl -LO http://github.com/openmelody/melody/zipball/master
Note: If you downloaded to your local computer first, copy it to the server. From your local computer:
$ scp melody-v1.x.zip user@domain.com:/www/var/cgi-bin/
-
Unzip the release archive:
$ unzip melody-v1.x.zip
or if using a tar.gz archive file:
$ tar xzvf melody-v1.x.tar.gz
-
Change the name of the directory from the versioned name (melody-v1.x) to
m
:$ mv melody-v1.x m
Tip: a symlink can be created to point
m
to the current application directory in the cgi-bin so that Melody can be accessed without the version number in the URL:.$ ln -s melody-v1.x m
Read more about Symlinking to the application directory.
-
Move the static directory (melody-v1.x/mt-static) to the web root:
$ mv melody-v1.x/mt-static /var/www/html/mt-static
-
Update Permissions
Read about changing file and directory permissions for the following directories:
- Application Scripts (all files ending in
.cgi
) must be readable and executable by all users and writable only by the owner (755). - Support directory located at
$M_HOME/mt-static/support
must be writable (typically 777 or 775). - Themes directory must be writable in order to export themes (typically 777 or 775).
Tip: the
mt-static/support
and themes directories can be 775 if the web server user is in the directories’ group or 755 if the web server user owns the directories. Read more about File Permissions. - Application Scripts (all files ending in
Configuring requires the creation of the config.cgi
file. Two ways to do this:
-
Use the Configuration Wizard. Access Melody; the URL will be similar to http://www.domain.com/cgi-bin/mt/index.cgi). Melody will redirect you to the Configuration Wizard if it can't locate the
config.cgi
configuration file. -
Manually create the
config.cgi
configuration file.Note: There are many other configuration directives which may be used to customize the install.
Note: Optionally, confirm proper installation that Melody is installed properly by accessing the check.cgi script. Should be a url similar to this:
http://domain.com/cgi-bin/melody-v1.x/check.cgi
The message “Melody System Check Successful” will appear at the bottom of the screen if the server has all the necessary libraries/modules for installing Melody.
If the system check fails to complete, then the missing Perl libraries/modules must be installed before continuing.
Once the config.cgi
configuration file is in the application directory:
-
Access Melody; the URL will be similar to http://www.domain.com/cgi-bin/mt/index.cgi). If proceeding from the Configuration Wizard, you will be redirected to this url.
-
Create the administrator account. Click “Continue”.
-
Create the first website. Click “Finish”.
Melody will then initialize the database with all the configuration options and settings specified.
-
Click “Sign into Melody”... you’ve installed Melody.
If there are any errors, double-check that the steps above have been completed.
- Plugin Documentation
Third-party plugins critical to the functionality of blogs/websites published by this installation of Melody should be installed before the new version is used to publish otherwise there may be errors.
Read about “Confirming Plugin Compatibility” in the Pre-Upgrade Check List at the top of this guide.
Start Blogging!
Once necessary third-party plugins have been installed, publish each blog and website to test for any errors.
Warning: because the check.cgi script displays server details which could be useful to a hacker, it is recommended that this script be removed or renamed. If renamed, use the CheckScript directive so that Melody knows where the script was moved.
Questions, comments, can't find something? Let us know at our community outpost on Get Satisfaction.
- Author: Six Apart Ltd.
- Edited by: Violet Bliss Dietz, Mike Thomsen