Website component of the JourneyMonitor service.
Switch branches/tags
travisci-build-master-136 travisci-build-master-135 travisci-build-master-134 travisci-build-master-133 travisci-build-master-132 travisci-build-master-131 travisci-build-master-130 travisci-build-master-129 travisci-build-master-128 travisci-build-master-127 travisci-build-master-126 travisci-build-master-125 travisci-build-master-124 travisci-build-master-123 travisci-build-master-122 travisci-build-master-121 travisci-build-master-120 travisci-build-master-119 travisci-build-master-118 travisci-build-master-117 travisci-build-master-115 travisci-build-master-114 travisci-build-master-113 travisci-build-master-112 travisci-build-master-111 travisci-build-master-110 travisci-build-master-109 travisci-build-master-108 travisci-build-master-107 travisci-build-master-106 travisci-build-master-105 travisci-build-master-104 travisci-build-master-103 travisci-build-master-102 travisci-build-master-101 travisci-build-master-100 travisci-build-master-99 travisci-build-master-98 travisci-build-master-97 travisci-build-master-96 travisci-build-master-95 travisci-build-master-94 travisci-build-master-93 travisci-build-master-92 travisci-build-master-91 travisci-build-master-90 travisci-build-master-89 travisci-build-master-88 travisci-build-master-87 travisci-build-master-86 travisci-build-master-85 travisci-build-master-84 travisci-build-master-83 travisci-build-master-80 travisci-build-master-79 travisci-build-master-78 travisci-build-master-77 travisci-build-master-76 travisci-build-master-74 travisci-build-master-73 travisci-build-master-72 travisci-build-master-71 travisci-build-master-70 travisci-build-master-69 travisci-build-master-68 travisci-build-master-67 travisci-build-master-66 travisci-build-master-65 travisci-build-master-64 travisci-build-master-63 travisci-build-master-62 travisci-build-master-61 travisci-build-master-60 travisci-build-master-59 travisci-build-master-58 travisci-build-master-51 travisci-build-master-50 travisci-build-master-48 travisci-build-master-47 travisci-build-master-45 travisci-build-master-44 travisci-build-master-43 travisci-build-master-42 travisci-build-master-41 travisci-build-master-40 travisci-build-master-39 travisci-build-master-38 travisci-build-master-37 travisci-build-master-36 travisci-build-master-35 travisci-build-master-34 travisci-build-master-33 travisci-build-master-32 travisci-build-master-31 travisci-build-master-30 travisci-build-master-29 travisci-build-master-27 travisci-build-master-25 travisci-build-master-22 travisci-build-master-20
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


About this repository

Applications that powers the JourneyMonitor website at

It contains two technical stacks, one based on PHP (e.g. the Symfony2 app), one based on JVM technology.

Build Status


About the JourneyMonitor project

Please see for more information.

Setting up a development environment

Using Docker (recommended)

Set up a development environment as described in this document.

Afterwards, follow these steps:

  • From infra/docker, run docker-compose exec journeymonitor-control bash
  • cd /opt/journeymonitor/control

Enjoy. Consider running most commands via sudo -u www-data, because www-data is the owner of all files in /opt/journeymonitor/control and the owner of the nginx and php-fpm processes.


  • cd /opt/journeymonitor/control/php
  • sudo -u www-data make test

Mac OS X

We do not officially support installing and running this application on Mac OS X environments (outside of Docker), but the following might be helpful if you want to give it a try.

Assumes that you have Make, PHP 5.5, Git, Bower, and Composer installed.

git clone
cd control/php
make dependencies
make migrations
make assets
make dev-server-run

You can now access the application at http://localhost:8000. Run the tests via make tests. Please note that you need to increase the memory_limit in php.ini to 256M to make the test run work.


We do not officially support installing and running this application on Windows environments, but the following might be helpful if you want to give it a try. The described steps have been tested on Windows 8.1 Pro x64 WMC.

  • First install git:
  • git clone
  • cd control
  • Download PHP from (x64 Threadsafe) and unzip to C:\Program Files\php
  • Add php to your PATH Variable (Windows+Pause --> Advanced --> Environment Variables --> PATH (Edit / New) --> Add 'C:\Program Files\php;' without quotes)
  • Copy C:\Program Files\php\php.ini-development to C:\Program Files\php\php.ini
  • Start an editor of your choice in elevated (admin) mode and make sure the following extensions are activated (remove ; in front):
  • extension_dir = "ext"
  • extension=php_curl.dll
  • extension=php_mbstring.dll
  • extension=php_openssl.dll
  • extension=php_pdo_sqlite.dll
  • extension=php_sqlite3.dll
  • Also add date.timezone = Europe/Berlin to the file
  • Open a cmd console and try to run php - if you see no output at all thats's good!
  • Next you need to install Composer from
  • Change into the cloned directory, subfolder php, and run composer install - choose C:\Temp\journeymonitor-control as the database file path
  • Login or create a github user and stay logged in in your browser
  • While running Composer it will fail saying you need to create an auth token - it will generate a link for you redirecting you in your already logged in github account
  • After generating the auth token rerun composer install to get the backend vendor files
  • Install Node.js from
  • Make sure to let the installer add PATH variables
  • If Node.js was installed successfully try running npm in your console - if the command was not found try rebooting
  • Head back to the checked out folder and run npm install -g bower
  • Then run bower install to get the frontend vendor files
  • Run php app/console doctrine:migrations:migrate
  • Run php app/console assets:install
  • Run php app/console server:run

Other info

At php/app/Resources/journeymonitor-control-dev.sqlite3.dist.gz you'll find an sqlite3 database file that contains the user '' with password 'demo123'. The user has some testcases and testresult data. Simply unzip to /var/tmp/journeymonitor-control-dev.sqlite3 if you want to use it.

Web Frontend Styleguide

See for color scheme.