Support Center

ViMP Support

FAQ Installation and First steps

Installing the Webserver, Webhosting and ViMP on RedHat 6.x / CentOS 6.x

Editions: Community, Professional, Enterprise, Enterprise Ultimate, Corporate
Versions: all

This article explains how to install the complete server software (Apache, MariaDB, php5, php-cli, postfix etc.) for ViMP and how to configure the webhosting.

We need the well known EPEL (Extra Packages for Enterprise Linux) repository to install php-mcrypt that is not part of the RHEL or CentOS base repositories.

For RHEL  please note:

For CentOS just execute:

yum install epel-release

We install Apache and PHP:

yum update
yum install httpd php php-gd php-mysql php-mbstring php-process php-xmlrpc php-xml libxslt php-mcrypt

We install postfix as MTA (Mail Transport Agent). Other MTAs like sendmail can be used, too, but please take care that it is configured to send e-mails by PHP scripts.

yum install postfix

Apache Konfiguration:

We install ViMP into the "default"-hosting. Its configuration was created automatically with the apache installation. We need some configuration changes and use "vi" as editor. Feel free to use any other editor of your choice:

vi /etc/httpd/conf/httpd.conf

First we change the DocumentRoot like this:

DocumentRoot "/var/www/html/web"

And we change the corresponding block. Please don't forget to adapt the path within the Directoy tag:

# Further relax access to the default document root:
<Directory "/var/www/html/web">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important.  Please see
    # for more information.
    Options FollowSymLinks

    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    AllowOverride All


We create the new configured DocumentRoot and set owner and group:

# mkdir /var/www/html/web
# chown -R apache:apache /var/www/html/web

We reload the configuration later. First we have to...

Configure Firewall

We open Port 80 (HTTP) and 443 (HTTPS) of the firewall iptables:

# iptables -I INPUT -p tcp --dport 80 -j ACCEPT
# iptables -I INPUT -p tcp --dport 3306 -j ACCEPT
# service iptables save
# firewall-cmd --reload

PHP configuration

There's just one php.ini file that configures PHP for Apache and the CLI (cli=command line interface).

joe /etc/php.ini

Modify the following lines:

upload_max_filesize = 2047M
post_max_size = 2047M
memory_limit = 2047M

Save and restart Apache.

service httpd restart

Create database and database user:

If not already done we set a password for the mysql user "root":

# mysql
mysql> UPDATE mysql.user SET Password=PASSWORD('mypassword') WHERE user='root'; mysql> flush privileges; mysql> exit;

Now log in again with the new password and create the ViMP database and db-user:

# mysql -p
# [enter mysql-root password]
mysql> create database DATABASENAME default character set utf8 collate utf8_unicode_ci;
mysql> grant all privileges on DATABASENAME.* to 'DATABASEUSER'@'localhost' identified by 'PASSWORD';
mysql> flush privileges;
mysql> exit;

Uploading and Installing the ViMP package

IMPORTANT: To run ViMP Community, ViMP Professional and ViMP Corporate editions you need to install the free SourceGuardian extension. Find the tutorial here: Installing the SourceGuardian PHP extension Redhat 6 / CentOS 6

Upload and installation of the ViMP installer is described here.

Basic usage

Now the installation is finished. Enter the URL of your portal in your web browser.

During installation three users with the corresponding user roles are created:

  • "admin" (Password: "admin") as administrator
  • "moderator" (Password: "moderator") as moderator
  • "user" (Password: "user") as standard user

Change all passwords as soon as possible after installation. If you don't need those standard users you can delete each of them in the administration backend.

Attention: Never delete the admin user as long as you didn't create another administrator - you would lock yourself out of the portal!

Last update on 2017/02/21 by SUPPORT.

Go back