Skip to content
Dashboard for your Deployment pipeline https://dashboardhub.io/
Branch: v0.11.0-alpha
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
api fix(releases): #591 duration is 0 for when in starting state Jun 12, 2018
data
web defect(environment-details): #1068 fixed environment details spacing Nov 22, 2018
.floo Realtime collaboration with Floobits Sep 2, 2017
.flooignore Realtime collaboration with Floobits Sep 2, 2017
.gitignore Removed all current UI and started porting over without Covalent, thi… Oct 11, 2018
.travis.yml feat(ci): #965 bumped version to v0.10-alpha Jun 1, 2018
CODE_OF_CONDUCT.md Code of Conduct added Aug 11, 2017
LICENSE License added Jul 22, 2017
Makefile
README.md

README.md

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

PipelineDashboard

Display your deployed versions and monitor it.

Current active project board and epic branch issue-firebase

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

Website

Features

Application Platform

Releases


REQUIREMENTS

  • 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

ROADMAP

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

QUICK START

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:

    1. API AUTH0_CLIENT_ID_TEST=XXX AUTH0_CLIENT_SECRET_TEST=YYY NODE_ENV=development make api

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/

RUNNING AUTOMATED TESTS

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)
    1. Run AUTH0_CLIENT_ID_TEST=XXX AUTH0_CLIENT_SECRET_TEST=YYY NODE_ENV=development make test

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

SUB PROJECTS

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

COLLABORATION

Use Floobits to do realtime coding collaboration.


FAQs

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/
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.