DevDash is a terminal dashboard for developers who want the most up-to-date data they need, per project, at one place.

• All the metrics you specifically need, at one place.
• Pull data from Github, Google Analytics or Google Search Console. More services to come!
• Unlimited amount of different dashboards with different configurations.
• Widgets' data refreshed automatically.
• A huge amount of flexibility compared to other terminal dashboards:
  • Choose the widgets you want.
  • Place your widgets where you want.
  • Choose the color, the data and a lot of other things for each widget.
• It's in the terminal so it's cool!

• Installation
• Getting Started
• Authorization and permissions
• Configuration examples
• Structure of the config file
• Widget types
• Configuration reference
• General references
• Acknowledgement
• Contribute
• Licence

You can simply grab the latest released binary file and put it wherever you want.

Here's a simple way to download and put DevDash in /usr/local/bin, which should be part of your path.

cd /usr/local/bin && sudo curl -LO https://github.com/Phantas0s/devdash/releases/download/0.1.0/devdash && sudo chmod 755 devdash && cd -

You need go installed to compile DevDash.

Then, simply run go get -u github.com/Phantas0s/devdash/cmd/devdash/

For now, you can access four APIs (services) via DevDash:

• Google Analytics (ga)
• Google Search Console (gsc)
• A monitoring service (mon)
• Github (github)

To see DevDash in action and get familiar with the config file, you can easily configure the monitoring service:

Here the config to create this (very simple) dashboard:

---
general:
  refresh: 600
  keys:
    quit: "C-c"

projects:
  - name: Quickstart
    services:
      monitor:
        address: "https://www.web-techno.net"
    widgets:
      - row:
          - col:
              size: "M"
              elements:
                - name: mon.box_availability
                  options:
                    border_color: green

You can:

• Copy past the config in a new file (monitoring.yml, for example)
• Run DevDash: devdash -config monitoring.yml

Congratulation! You just created your first dashboard. DevDash will simply send a request every 600 seconds to https://www.web-techno.net and display the response's status code.

Some services need credentials and permissions for DevDash to pull the data into your shiny terminal. Following the detailed step by step tutorial to create these permissions:

1. Go to your Github account in your favorite browser
2. Click on your avatar (top right corner)
3. Click on "Settings"
4. Click on "Developer settings"
5. Click on "Personal access tokens"
6. You don't need to select any scope for DevDash, except if you want to read data from your private repositories.
7. Generate a new token you will add in your DevDash configuration.

Obviously, you need to have a Google Analytics account or Google Search account to access these two services.

1. Go to [https://console.developers.google.com/apis/api/webmasters.googleapis.com/credentials](Google APIs Credentials).
2. Select Service account key.
3. Create a new service account.
4. Select the role Project -> Viewer for a read access only.
5. Add a name.
6. Click on the button create.
7. Save the Service account ID somewhere. We will need it later.
8. Download the JSON file. Its path need to be specified in the config of your DevDash dashboard.

1. Go to your Google Analytics account.
2. Click on Admin in the menu (last element of the menu)
3. Select the application you want to use with DevDash in the property column (just below the column name property).
4. Click on the + button and add a user.
5. Click on user management of the same column.
6. Enter the email address you saved before (the Service account ID of step 7, above).
7. Click on View settings on the View column and copy the View ID into your DevDash configuration file.

1. Go to your Google Search Console account
2. Click the property you want to access with DevDash.
3. Click on Settings in the menu on the left.
4. Click on Users and permissions and add a user with the Service Account ID as email address (see step 7 of Downloading the authorization JSON file above).

You can click on each screenshot to see the config of these dashboards.

Since a diagram is better than a wall of text, here we go:

There are three category of widgets:

• box - a single value in a box
• bar - a bar diagram with multiple values overtime (dates on the x-axis)
• table - data in a table

    services:
      monitor:
        address: "https://www.my-website.net"

None.

    services:
      github:
        token: myToken
        owner: myName
        repository: myCoolRepo

The repository is not mandatory. However, you will need to precise the repository for each widget fetching data for a specific one.

    services:
      google_analytics:
        keyfile: goanalytics-abc123.json
        view_id: 456789123

    services:
      google_search_console:
        keyfile: goanalytics-abc123.json

The list of colors you can use in DevDash configuration.

Their display will depend of the colors you've configured for your terminal.

DevDash is based on a 12 columns grid.

You can indicate the width of a widget in number of column (1 to 12), or using the equivalent t-shirt size as described below:

The start_date and end_date options accept dates following this format: 2016-01-02.

You can use as well aliases relative to the present day.

The same alias can be a different date depending if it's used for the start_date or the end_date option.

You can replace every x in the names by numerical values.

Thanks to MariaLetta for the awesome and beautiful Gopher pack she made! I used it for my logo on top.

DevDash was inspired from other open source projects:

• wtf
• tdash

First of all, thanks a lot if you want to contribute to DevDash!

I think the "talk, then code" practice is pretty good to avoid misunderstandings and hours of work for nothing.

Therefore:

"Every new feature or bug fix should be discussed with the maintainer(s) of the project before work commences. It’s fine to experiment privately, but do not send a change without discussing it first."

Apache Licence 2.0