Dashboard for your Deployment pipeline https://dashboardhub.io/
Switch branches/tags
v0.8.0 v0.8.0-alpha v0.7.0-prototype build-release-0.2.1-prototype-398 build-release-0.2.1-prototype-397 build-release-0.2.1-prototype-389 build-release-0.2-pre-alpha-400 build-release-0.2-pre-alpha-390 build-release-0.2-pre-alpha-387 build-quick-test-285 build-quick-test-284 build-quick-test-283 build-quick-test-282 build-quick-test-281 build-quick-test-280 build-quick-test-279 build-quick-test-278 build-quick-test-277 build-prototype/yslow-beacon-data-410 build-prototype/yslow-beacon-data-395 build-prototype/yslow-beacon-data-394 build-prototype/yslow-beacon-data-384 build-prototype/yslow-beacon-data-382 build-prototype/yslow-beacon-data-374 build-prototype/yslow-beacon-data-373 build-prototype/yslow-beacon-data-366 build-prototype/yslow-beacon-data-364 build-prototype/yslow-beacon-data-363 build-prototype/yslow-beacon-data-362 build-prototype/yslow-beacon-data-361 build-prototype/yslow-beacon-data-360 build-prototype/yslow-beacon-data-342 build-prototype/yslow-beacon-data-326 build-prototype/yslow-beacon-data-324 build-prototype/yslow-beacon-data-312 build-prototype/yslow-beacon-data-310 build-prototype/yslow-beacon-data-309 build-prototype/yslow-beacon-data-308 build-prototype/yslow-beacon-data-307 build-prototype/yslow-beacon-data-306 build-prototype/yslow-beacon-data-305 build-prototype/yslow-beacon-data-301 build-prototype/yslow-beacon-data-300 build-prototype-v0.3-2016-04-19-560 build-prototype-v0.3-2016-04-05-557 build-prototype-v0.3-2016-04-03-555 build-prototype-v0.3-2016-04-03-554 build-prototype-v0.3-2016-04-03-552 build-prototype-v0.3-2016-04-02-550 build-prototype-v0.3-2016-03-31-546 build-prototype-v0.3-2016-03-29-543 build-prototype-v0.3-2016-03-28-542 build-prototype-v0.3-2016-03-28-540 build-prototype-v0.3-2016-03-25-519 build-prototype-v0.3-2016-02-22-517 build-prototype-v0.3-2016-02-21-514 build-prototype-v0.3-2016-02-21-513 build-prototype-v0.3-2016-02-21-512 build-prototype-v0.3-2016-02-19-511 build-prototype-v0.3-2016-02-11-509 build-prototype-v0.3-2016-02-11-507 build-prototype-v0.3-2016-02-09-505 build-prototype-v0.3-2016-02-09-504 build-prototype-v0.3-2016-02-08-502 build-prototype-v0.3-2016-02-08-500 build-prototype-v0.3-2016-02-08-497 build-prototype-v0.3-2016-02-07-496 build-prototype-v0.3-2016-02-07-494 build-prototype-v0.3-2016-02-07-493 build-prototype-v0.3-2016-02-06-491 build-prototype-v0.3-2016-02-06-489 build-prototype-v0.3-2016-02-05-485 build-prototype-v0.3-2016-02-05-483 build-prototype-v0.3-2016-02-05-482 build-prototype-v0.3-2016-02-04-480 build-prototype-v0.3-2016-02-03-478 build-prototype-v0.3-2016-02-03-475 build-prototype-v0.3-2016-02-02-473 build-prototype-v0.3-2016-02-02-471 build-prototype-v0.3-2016-02-02-466 build-prototype-v0.3-2016-01-31-463 build-prototype-v0.3-2016-01-30-461 build-prototype-v0.3-2016-01-30-458 build-hotfix/81-mock-user-error-192 build-hotfix/81-mock-user-error-190 build-hotfix/81-mock-user-error-189 build-hotfix/71-builtin-webserver-128 build-hotfix/71-builtin-webserver-126 build-hotfix/71-builtin-webserver-124 build-hotfix/48-oauth-redirect-46 build-hotfix/48-dev-parameters-file-53 build-fix/composer-download-travis-411 build-feature/207-update-profile-2016-02-05-484 build-feature/207-update-profile-2016-02-04-479 build-feature/207-update-profile-2016-02-03-476 build-feature/194-create-release-2016-01-30-457 build-feature/185-audit-user-login-2016-02-05-481 build-feature/185-audit-user-login-2016-02-03-477 build-feature/185-audit-user-login-2016-02-03-474 build-feature/185-audit-user-login-2016-02-02-472
Nothing to show
Clone or download
eddiejaoude Merge pull request #1067 from DashboardHub/epic-1051
feat(core): removal of covalent with material, general ui cleanup
Latest commit da247e5 Nov 2, 2018


Floobits Status Build Status DashboardHub Badge Gitter Conventional Commits Help Contribute to Open Source


Display your deployed versions and monitor it.

WANT TO GET INVOLVED? Don't know how? ...

All contributions are welcome, not only from code, but also blogs, content, documentation etc. Read more on our contributions guidelines.

Pair with our team remotely over Google Hangout!

Please get in touch via @DashboardHub and let us know, we are happy to chat and more than happy to pair on the technologies we use:

  • Angular (v5+)
  • Material design
  • Node
  • Serverless
  • AWS Lambda & DynamoDB



Application Platform



  • node (minimum v8)
  • npm (minimum v5)
  • java (minimum v8) - note: this is only to simulate aws services, you do not need to know any java
  • sed - note: available on linux by default, mac osx has a slightly different version that wont work, install linux version with brew brew install gnu-sed --with-default-names, more info in the FAQ section below.

Built with love using...

angular serverless nodejs aws


We have an aggressive plan for our ALPHA, so we can get feedback ASAP.

Milestone Link
Remove template https://github.com/DashboardHub/PipelineDashboard/milestone/23
Startup Grind event https://github.com/DashboardHub/PipelineDashboard/milestone/30

For more up to date information and more details please visit our milestone list


Using make to build and run the project(s):

Note: You need AW configured, although it will not be used, the AWS CLI requires it

    1. Install the npm dependencies for all projects, use make install.local

Open 2 terminals and run each of these commands in its own terminal:


NOTE: You will need a pem file for local development, and needs to be in the directory api call auth.pem (api/auth.pem)

    1. UI make ui

Then visit http://localhost:4200/


This is done using CumcumberJS, with the Given, When, Then format in English, in the api/tests/features directory.

Internet is needed when running the automated API tests, because a real jwt is used from Auth0 service.

    1. Start the API (step 2 from previous section)

Note: To run only specific feature files use the envar TEST_TAGS, for example TEST_TAGS=@Monitors

Additional useful commands

  • make api.clean resets the config files

Commit message standards

We use the Angular standards...

We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the Angular change log https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit

The format is <type>(<scope>): #<issue-no> <subject>, examples...

  • feat(environments): #123 delete environment
  • docs(commits): #456 example commit messages
  • chore(dependencies): #789 updated UI dependencies
key value notes
type build Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
type ci Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
type docs Documentation only changes
type feat A new feature
type fix A bug fix
type perf A code change that improves performance
type refactor A code change that neither fixes a bug nor adds a feature
type style Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
type test Adding missing tests or correcting existing tests
scope auth Authentication module
scope core Application wide, for example interceptors
scope environments Environment module changes (not sub modules)
scope help Help module
scope legal Legal module
scope monitors Monitors module
scope projects Projects module
scope releases Releases module
scope tokens Tokens module


  • API, read the API docs
  • Web UI, read the UI docs


Use Floobits to do realtime coding collaboration.


OS Question Answer
Mac OSx Error sed: 1: "./config.json": invalid command code . Use linux sed brew install gnu-sed --with-default-names
ALL Changes to the API config api/config.json are lost This file is generated, do not make changes to it. If you need to update any config make changes to api/config.json.tpl
ALL First time setup login failure Check you have the auth.pem file in the API directory
ALL Worked before but now login failure The API pem file was renamed from dashboardhub.pem to auth.pem

Social media

media link
Twitter https://twitter.com/dashboardhub
LinkedIn https://www.linkedin.com/showcase/dashboardhub/
Facebook https://www.facebook.com/dashboardhub/