Configuration file (conf.php)

Conf.php is main Vivvo configuration file containing basic and most important configurations for the system. It is located in root of your VIVVO installation, and it is highly recommended to keep it on maximum security level.

Default config file after initial installation should look like this:

<?php
	define('VIVVO_URL', "http://www.example.com");
	define('VIVVO_LICENSE_CODE', 'Developer-1234567890');
	define('VIVVO_DB_TYPE', 'mysql');
	define('VIVVO_DB_HOST', "localhost");
	define('VIVVO_DB_USER', "db_user");
	define('VIVVO_DB_PASSWORD', "db_password");
	define('VIVVO_DB_DATABASE', "db_database");
	define('VIVVO_DB_PREFIX','');
	define('VIVVO_DOMAIN', 'localhost');
	define('VIVVO_FS_ROOT', realpath(dirname(__FILE__)) . "/");
	define('VIVVO_FS_INSTALL_ROOT', VIVVO_FS_ROOT);
	define('VIVVO_FS_PLUGIN_ROOT', VIVVO_FS_ROOT);
	define('VIVVO_FS_LANG_ROOT', VIVVO_FS_ROOT);
	define('VIVVO_FS_TEMPLATE_ROOT', VIVVO_FS_ROOT);
	define('VIVVO_FS_ADMIN_ROOT', VIVVO_FS_ROOT);
	define('VIVVO_FS_ADMIN_DIR', 'admin/');
?>

These values may vary depending on your installation options

Default configuration values

Parameter name Description
VIVVO_URL Full HTTP path to Vivvo installation
VIVVO_LICENSE_CODE Your license key
VIVVO_DB_TYPE Database type (currently only MySQL supported)
VIVVO_DB_HOST Database server
VIVVO_DB_USER Database username
VIVVO_DB_PASSWORD Database password
VIVVO_DB_DATABASE Database name
VIVVO_DB_PREFIX Prefix for table names (optionally)
VIVVO_DOMAIN ???
VIVVO_FS_ROOT' ???
VIVVO_FS_INSTALL_ROOT ???
VIVVO_FS_PLUGIN_ROOT Root directory for plug-ins
VIVVO_FS_LANG_ROOT Root directory for lang files
VIVVO_FS_TEMPLATE_ROOT Root directory for templates
VIVVO_FS_ADMIN_ROOT ???

Additional (optional) configuration values

Vivvo Configuration allows you to change these values, or add new params to control your installation.

Renaming 'Admin' folder

You can change the path of Control Panel (administration) in Vivvo. Default path is /admin and it is defined in

define('VIVVO_FS_ADMIN_DIR', 'admin/');

In order to change this, you must change this parameter value and also physically change the name of the folder via FTP.

Serving Static Content

Vivvo allows usage of additional server to serve static content (images, JS, CSS) in order to improve overall speed and performance of the system. Any server can be used, like Nginx, Varnish, Lighttpd or similar. You need to define the port and address where the server is listening.

define('VIVVO_STATIC_URL', 'static.site.com:8080/');

It is highly recommended to use dedicated subdomain for static_URL.

Support for Memory-based caching (memcache)

Configuring requires a basic knowledge of JSON format. If you are not familiar with JSON, please harvest a basic understanding how parameters can be set in your conf.php file in order to set it right. You can start from here for JSON conventions.

To setup Vivvo Memcache requires two constants in conf.php:

Default configuration looks like this (assuming you have Memcache running):

...
define('VIVVO_SYSTEM_CACHE_DRIVER', 'Memcache');
define('VIVVO_SYSTEM_CACHE_DRIVER_PARAMS', '{
"Memcache":{
  "servers":[
    {"host":"127.0.0.1", "port":11211, "persistent":false}
    ],
  "compression":false,
  "namespace":"vivvo",
  "lifetime":0
  }
}');
...

Please refer to full Memcache instruction notes for detailed explanations and references.

CSS & JavaScript Caching

As of version 4.5 Vivvo CMS minifies and caches CSS and JavaScript files which are served trough compress.php. This helps lower server load and improves responsiveness of your page. By default file is cached for an hour.

While this is helpful on production servers you may want to disable it on your development server (where you frequently change CSS/JavaScript). To do so just add following line to your conf.php file:

define('VIVVO_COMPRESS_CACHE_LIFETIME', 0);

Also you may want to increase cache lifetime period to more than an hour (on production server), just change 0 to number of seconds you wish cache file should be valid for. For example, this is how you set cache lifetime to 10 days:

define('VIVVO_COMPRESS_CACHE_LIFETIME', 864000);  // 60 * 60 * 24 * 10 = 864000

Caching With Separate Server for Static Content

If you're using separate server for serving static content, you will need to purge the cache before changes to CSS take effect. For Varnish you will need to SUDO with root privileges and execute:

sudo varnishadm -S /etc/varnish/secret -T localhost:6082 purge.url themes/*

You may also reference official Varninsh wiki for more information and alternatives.

Using Custom URL for Invalid License

As of Vivvo 4.5 you can use custom landing page for invalid license notifications. This applies to Developer licenses only.

define('VIVVO_INVALID_LICENSE_URL', 'http://www.yoursite.com/invalid-license.html');
 
user_manual/installation/config.txt · Last modified: 2010/09/03 04:13 by boccio
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki