valitydev/redash
14
0
Fork 0
mirror of https://github.com/valitydev/redash.git synced 2024-11-07 01:25:16 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
2,983 Commits 7 Branches 0 Tags 20 MiB
Python 41.3%
JavaScript 33.2%
TypeScript 17.5%
Less 6.6%
HTML 1.1%
Other 0.1%
c1c2db4a73
Go to file
Kumar Vora c1c2db4a73 use user.org instead of passing org as a separate argument
2016-05-20 14:28:08 -05:00
.github Update ISSUE_TEMPLATE.md 2016-05-05 22:30:10 +03:00
bin Ama: Consolidate vagrant_provision script, move files to more intuitive locations, include command from #1021. 2016-05-09 17:13:33 -05:00
docs Ama/Kumar: Configure authorization for SAML 2016-05-17 14:01:18 -05:00
migrations Migration to make sure the default group has correct type 2016-03-27 10:29:26 +03:00
rd_ui Don't render visualizations in the background 2016-05-08 10:34:30 +03:00
redash use user.org instead of passing org as a separate argument 2016-05-20 14:28:08 -05:00
setup Ama: Install just pymongo and not everything in requirements_all_ds.txt 2016-05-09 17:15:07 -05:00
tests use user.org instead of passing org as a separate argument 2016-05-20 14:28:08 -05:00
.coveragerc Exclude settings.py from coverage report. 2014-02-06 20:55:14 +02:00
.dockerignore Fix .dockerignore file: 2015-11-23 11:38:15 +02:00
.env.example Remove references to deprecated config 2016-03-12 18:22:53 +02:00
.gitignore Change suffix of docker-compose file to .yml as suggested by docker-compose 2015-11-23 11:38:15 +02:00
.landscape.yaml landscape.io configuration file 2014-10-19 13:41:29 +03:00
circle.yml Ama: Install just pymongo and not everything in requirements_all_ds.txt 2016-05-09 17:15:07 -05:00
docker-compose-example.yml redash static assets path should be pointed at dist, not app 2016-03-10 11:36:42 -08:00
Dockerfile Dockerfile: set the path to static assets 2016-03-12 18:37:20 +02:00
LICENSE BSD 2-Clause 2016-02-10 11:32:00 +02:00
Makefile Run make deps only if rd_ui/app exists 2016-01-07 14:56:28 +02:00
manage.py manage.py support group operations. 2016-04-10 22:08:36 +09:00
Procfile.dev Vagrant file to use the redash/dev box 2014-12-30 07:45:30 +02:00
README.md Add Slack to list of contact methods 2016-04-17 09:24:21 +03:00
requirements_all_ds.txt code style, name method 2016-03-23 11:44:57 +02:00
requirements_dev.txt Move datasource requirements from bootstrap to own requirements file 2015-07-27 11:46:53 -07:00
requirements_oracle_ds.txt Better number handling 2015-10-21 10:05:38 -04:00
requirements.txt Merge pull request #934 from alexanderlz/master 2016-03-29 22:00:32 +03:00
Vagrantfile Ama: Consolidate vagrant_provision script, move files to more intuitive locations, include command from #1021. 2016-05-09 17:13:33 -05:00

README.md

More details about the future of re:dash : http://bit.ly/journey-first-step

Join the chat at https://gitter.im/getredash/redash Documentation

re:dash is our take on freeing the data within our company in a way that will better fit our culture and usage patterns.

Prior to re:dash, we tried to use traditional BI suites and discovered a set of bloated, technically challenged and slow tools/flows. What we were looking for was a more hacker'ish way to look at data, so we built one.

re:dash was built to allow fast and easy access to billions of records, that we process and collect using Amazon Redshift ("petabyte scale data warehouse" that "speaks" PostgreSQL). Today re:dash has support for querying multiple databases, including: Redshift, Google BigQuery, PostgreSQL, MySQL, Graphite, Presto, Google Spreadsheets, Cloudera Impala, Hive and custom scripts.

re:dash consists of two parts:

  1. Query Editor: think of JS Fiddle for SQL queries. It's your way to share data in the organization in an open way, by sharing both the dataset and the query that generated it. This way everyone can peer review not only the resulting dataset but also the process that generated it. Also it's possible to fork it and generate new datasets and reach new insights.
  2. Dashboards/Visualizations: once you have a dataset, you can create different visualizations out of it, and then combine several visualizations into a single dashboard. Currently it supports charts, pivot table and cohorts.

re:dash is a work in progress and has its rough edges and way to go to fulfill its full potential. The Query Editor part is quite solid, but the visualizations need more work to enrich them and to make them more user friendly.

Demo

You can try out the demo instance: http://demo.redash.io/ (login with any Google account).

Getting Started

Getting Help

Reporting Bugs and Contributing Code

  • Want to report a bug or request a feature? Please open an issue.
  • Want to help us build re:dash? Fork the project, edit in a dev environment, and make a pull request. We need all the help we can get!

License

See LICENSE file.