This repository has been archived by the owner on Mar 7, 2018. It is now read-only.
Home
Daniel Beauchamp edited this page Apr 18, 2016
·
35 revisions
Good question! There are tons of great options available, such as Geckoboard, Dashku, and Ducksboard. However, each have their own limitations.
At Shopify, we needed our dashboards to:
- Use our own authentication. Many online platforms give you private URLs to your dashboards. Those can be tricky to remember, and can accidentally fall in the wrong hands. With Dashing, you can add whatever auth you want. We use Google Auth.
- Be completely customizable. We didn't want to be limited by the widgets that are available on other platforms. We also wanted all of our code to be in version control, and editable in whatever IDE we want.
- Keep instances of the same widget in sync. Many online dashboards give unique ids for every widget instance you create. This means that if you want to update 3 identical widgets showing 'daily sales', you'll need to use the API to push the value to all 3 instances. With Dashing, identical widgets all have the same id, meaning less duplication, and complete synchrony across all dashboards.
Visit the homepage
Here's a list of awesome widgets you can include in your dashboards. Feel free to add your own!
- How To: Add authentication
- How To: Deploy to Heroku
- How To: Run Dashing on Puma
- How To: Send HTML data to your widgets
- How To: Run on a different port, or in production
- How To: Debug incoming widget data
- How To: Change the default dashboard
- How To: Run dashing on a sub path
- How To: Update font awesome fonts from version 3 to 4
- How To: Prevent a job from overlapping with itself
- How To: Share your widgets
- How To: Send Mysql data to your widgets
- How To: Cycle through Multiple Dashboards
- How To: Prepare data for a graph widget
- How To: Define a data model and store history data to database