Installation

For the sake of clarity we will perform this installation in a preconfigured Vagrant box built with PuPHPet. More info in this chapter about the PuPHPet development environment. If you have a development environment, just adjust to match your specifics.

This chapter assumes you have started the box (vagrant up), ssh'ed into it (vagrant ssh) and have navigated to the /var/www folder (cd /var/www). If there is a folder there called myprojectname you should delete it by running: rm -Rf myprojectname

Downloading and configuring the base CMS

We will get started by downloading the Kunstmaan Bundles Standard Edition to get the CMS and all it's dependencies.

composer create-project kunstmaan/bundles-standard-edition myprojectname

composer create

It will then ask you some questions to configure Symfony and the CMS system. At this point just fill in the database_name like so:

composer parameters

Since our project is named myproject, the websitetitle, session_prefix, searchindexname and searchindexprefix are all ok. In a real project they probably aren't.

We will configure all other parameters later on.

First step now is to add all these files into version control. What version control system and what vcs hosting you use is up to you. This example assumes Git and GitHub.

Create a new repository (in most cases a private one). Don't add any files from the GitHub interface to start with.

composer create-project -s dev kunstmaan/bundles-standard-edition myprojectname

Then execute these commands in /var/www/myprojectname/ to initialise the git repository

git init
git add .
git commit -m "Clean install of the KunstmaanBundlesCMS"
git remote add origin https://github.com/USERNAME/MyProject.git
git push -u origin master

At this point refreshing the page for your repository on GitHub will show you your files.

Please note that the .gitignore file of the KunstmaanBundlesStandardEdition prevents committing your parameters.yml file into git. Depending on your needs, you could change this by removing that line from yout .gitignore file.

Generating a bundle

First, you should generate a bundle for your website specific code.

app/console kuma:generate:bundle

Each bundle is hosted under a namespace (like Acme/WebsiteBundle). The namespace should begin with a "vendor" name like your company name, your project name, or your client name, followed by one or more optional category sub-namespaces, and it should end with the bundle name itself (which must have Bundle as a suffix).

See this Symfony Best Practices document for more details on bundle naming conventions. At Kunstmaan we use ClientName/WebsiteBundle as a convention for a standard CMS project. In this example we use MyProject/WebsiteBundle.

For all other questions, the defaults should suffice.

Sometimes there are some issues with bash/zsh escaping in terminal input, so use / instead of \ for the namespace delimiter to avoid any problems.

app/console kuma:generate:bundle

Generating your website skeleton

Now that we have a bundle to store our code in, we are going to generate the skeleton for our website. You do this by running the following command. It will ask you for a MySQL database prefix, just leave it unless you have a specific reason to do so.

app/console kuma:generate:default-site

app/console kuma:generate:default-site

This generates:

This is the best starting point for a real website. If you add --demosite to the command above, this generator will generate more styling and fixtures so that the result ends up exactly like the demo site.

Initialising the database

When this is done, create the database schema and load all the generated fixtures to fill it.

app/console doctrine:database:create
app/console doctrine:schema:create
app/console doctrine:fixtures:load

app/console doctrine:schema:create

Generate Unit and Behat tests (optional)

If you want, you can generate a set of Unit and Behat test features that test that your site is working correctly. It will test logging in to the administration interface, it will create a page and tries to enter every pagepart. Most generators will generate extra features when you add features later on in development.

app/console kuma:generate:admin-tests

Just accept the default bundle namespace at the prompt.

app/console kuma:generate:admin-tests

Get all the front-end assets

Now that all your code is generated, let's make sure all front-end assets are available.

First make sure you have Bower, Gulp, UglifyCSS and UglifyJS installed globally.

UglifyCSS and UglifyJS are used via Assetic to minimize the javascript and css files in the administration interface, as per this recipe on in the Symfony Cookbook: How to Minify CSS/JS Files (Using UglifyJS and UglifyCSS)

Depending on your system you need sudo here.

npm install -g bower
npm install -g gulp
npm install -g uglify-js
npm install -g uglifycss
gem install bundler

Then execute the following commands:

bundle install
npm install
bower install
gulp build
app/console assets:install --symlink
app/console assetic:dump

At this point browsing to http://kunstmaan.cms/en/admin should greet you with the following screens.

Demo Site Admin

Note that the screenshots were made of a site using the --demosite option during generation