TYPO3 Neos - Smooth instalation and configuration

This post is about to present short but accurate instruction how to download TYPO3 Neos CMS, properly configure it and prepare for the very first run.

1. Server requirements

Not surprisingly, TYPO3 Neos requires www server to run properly as well as database server. Lots of Neos instalations run well with Apache and nginx. However though IIS and others works as well - they just haven't really been tested yet. One of the more important configuration of www server is to set mod_rewrite module enabled.

The oldest PHP version that Neos is able to work with is 5.3.2 It's been said that the newer PHP version, the better, faster and more stable Neos works. Moreover, it's advised that such PHP modules as mbstring, tokenizer i pdo_mysql set to enabled.

In summary, Neos' requirements are as bellow:

  • web server (Apache, nginx, IIS)
  • PHP >= 5.3.2
  • database server (MySQL, MariaDB, PostgreSQL)

Neos' sources can be downloaded two ways:

  1. as a package archive - https://neos.typo3.org/develop/download.html
  2. via composer - this way will be presented bellow

2. Getting sources

First step is to get composer manager if it isn't installed already. To get it just run below command in console (you might need root privileges):

#:/var/www/neos$ curl -sS https://getcomposer.org/installer | php

Following step is to move into directory where we want to keep Neos' sources. When we are there, we just need to fire another command to tell composer to download sources:

#: php composer.phar create-project typo3/neos-base-distribution {$our_custom_project_name}

When above command is run, we are able to see what is really going on. The newest and stable packages of TYPO3 Neos are being downloaded.

3. Installation and Configuration

The very first step in this case is to prepared our virtualhost file correctly. The most important thing is to set correct path to document root - the Web directory. An example is shown bellow:

Next, we ought to add our virtual server name as well as ip adres into /etc/hosts file in order to use it later.

Link as below allows us to start Neos setup process:


Initial password need to be read from example path as above and used in order to get into the next step of wizzard. This next step is about to fill database connection credentials and create new database for Neos if it hasn't existed yet.

Last but one step of wizzard is to fill administrator credentials who will be able to login into the backend.

Finally, the last step of wizzard is to choose which site of our instalation will be mark as a default one. Neos Demo Site was downloaded with default packages. If we want to have this one as default, we don't have to change nothing in this step. Default site is already chosen in "Select a site package" field. However, if we want to have our own, "dummy" site package, we may fill two fields bellow. Important thing is to remember that site name has to have it's own name pattern - just like it is shown in picture bellow.

After the last step, we sould see green confirmation that wizzard has successfully ended. We ought to be able to see two login buttons: into the backend and frontent as well.

Congratulations! You've just installed and configured TYPO3 Neos.

4. A few words of backend

Login into the backend is possible via address of your Noes instalation plus "/neos" e.g. www.my-neos.local/neos

After successful login one should see main cockpit content edition just like in picture below. Then we are able to:

  • see demo page with some content already, if you has chosen Demo Site Package in previous step
  • on left side, there is located tree structure of our website files. It allows you to switch between site pages and watch their content
  • in the middle, there is located main content window, where everyone can edit some existing content or insert the new one. This process should be smooth and easy for everybody who has worked with such applications as Word before
  • on right side, there is place for setting properties of middle window content elements such as background color change or setting url address

More examples of backend editing can be found in video below: