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
- AWS Lambda & DynamoDB
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...
We have an aggressive plan for our ALPHA, so we can get feedback ASAP.
|Startup Grind event||https://github.com/DashboardHub/PipelineDashboard/milestone/30|
For more up to date information and more details please visit our milestone list
make to build and run the project(s):
Note: You need AW configured, although it will not be used, the AWS CLI requires it
- Install the
npmdependencies for all projects, use
- Install the
Open 2 terminals and run each of these commands in its own terminal:
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
RUNNING AUTOMATED TESTS
This is done using
CumcumberJS, with the
Then format in English, in the
Internet is needed when running the automated API tests, because a real
jwt is used from
- Start the API (step 2 from previous section)
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
Additional useful commands
make api.cleanresets 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
|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||core||Application wide, for example interceptors|
|scope||environments||Environment module changes (not sub modules)|
Use Floobits to do realtime coding collaboration.
||Use linux sed
|ALL||Changes to the API config
||This file is generated, do not make changes to it. If you need to update any config make changes to
|ALL||First time setup login failure||Check you have the
|ALL||Worked before but now login failure||The API