Installation of the Baltic Content Framework is fairly simple. Here's how to do it.

Important Note

The Baltic Content Framework is designed to provide content and content management for other domains, and as such, requires a dedicated domain (or sub-domain) of its own on which to run. The domain on which you install the Baltic Content Framework is not the domain that users visit; they visit another domain (or domains) that receive content from Baltic. In order to leverage the power of the Baltic Content Framework, it is helpful to have control over certain settings for your web server, such as a domain's document root.

Getting Started

First, extract the Baltic files to a directory on your server that will host the Baltic domain. The extracted layout looks like this:

• app
• cache
• core
• domain
• entry
• init
• plugin
• public

The document root of your web site must point to the public directory, not above it. The public directory is the only directory that is inside the web space; everything else is outside. Therefore, the document root for your web site configuration will look something like this:

/home//www/balticframework/public

Next, rename CoreDatabaseConfig.php.txt to CoreDatabaseConfig.php. This file is located in the core/database directory and is required to connect to the database. CoreDatabaseConfig.php contains one static function like so:

public static function getDatabaseConfig(): OpenObject
{
return new OpenObject(array
(
'prefix'   => 'mysql',
'host'     => 'localhost',
'database' => 'my_database',
'persist'  => true,
'user'     => 'username',
'password' => 'xxxxxxxxxxxxxxxxxxxx'
));
}

Edit the host, database, user, and password according to your database installation. Do not change prefix or persist. Currently, only MySQL is supported.

Before continuing with the installation, note that the database must exist and be empty. The installer application creates the various tables and other database elements, but it does not create the database itself.

Install

Now run the installer application. To do so, point your browser to:

http://mydomain.com/install

The installer application checks the database connection and whether the database is empty, as required. It creates a default administrative user with a random email (used for login) and a random password. When the installation completes, login to the admin app (aka kong). From there, you can set the auto-generated credentials to those of your choosing.

You can also use the kong application to disable the installer application. This isn't absolutely necessary because once the database has been populated with its tables and other database elements, the installer application won't attempt the installation again, but it's a good idea. When the installer application is disabled, an attempt to run it will fail with a 404 error.

To disable the installer from the kong application, use System / Tools / Disable installer.