This document describes all neccessary steps in order to get an running Mapbender3 installation.
Mapbender3 needs the following components in order to run:
Optionally, in order to use a database other than the preconfigured SQLite one you will one a matching PHP extension supported by Doctrine http://www.doctrine-project.org/projects/dbal.html.
If you want to use the developer mode, for using the web installer or to create profiler data to be used to analyze errors you will still need the SQLite extension!
Installation packages are distributed as compressed packages and are available for download at the download http://mapbender3.org/download page.
After downloading, extract the package in a directory of your choice. Then make sure your Webserver points to the web directory inside the mapbender3 directory you just uncompressed. You will also need to make sure that the default directory index is app.php.
A Git-based installation - mainly for developers - is also possible.
Configuration right inside your browser is not yet available. Please use the command line method below for now.
Configuring your Mapbender3 installation is made up of the following steps:
All can be done using the console utility provided by Symfony2, the awesome framework Mapbender3 is build upon. There’s a mayor caveat though you should understand, before continuing:
The console utility will write files in the app/cache and app/logsdirectories. These operations are made using the user permissions ofwhatever user you’re logged in with. This is also true for the app/dbdirectory and the SQLite database within. When you open the applicationfrom within the browser, the server PHP process will try to access/writeall these files with other permissions. So make sure you give the PHPprocess write access to these files. See last step below.
Database connection parameters are stored together with some more configuration parameters in the file app/config/parameters.yml. This file is using YAML syntax, so be aware that you can not use tabs for indenting. Be careful about this.
Symfony2 can attempt to create your database, this works of course only if the configured database user is allowed to. Call the console utility like so:
app/console doctrine:database:create
Symfony2 will create the database schema for you, if you ask nicely:
app/console doctrine:schema:create
We also need to initialize the security system’s database tables seperately:
app/console init:acl
Each bundle has it’s own assets - CSS files, JavaScript files, images and more - but these need to be copied into the public web folder:
app/console assets:install web
As a developer, you might want to use the symlink switch on that command to symlink instead of copy. This will make editing assets inside the bundle directories way easier.
The standard roles need to be initialized in the database:
app/console fom:user:initroles
The first user - which has all privileges - must be created using the command:
app/console fom:user:resetroot
This will interactively ask all information needed and create the user in the database.
Now head over to your installation in your browser and enjoy.
Inserting from srs parameters into the database occurs using the command:
app/console doctrine:fixtures:load –append