135ffd693a
A user can disable it if he has tons of series. Now that we explicitly enable it, it's also visible for a single series. |
||
|---|---|---|
| bin | ||
| docs | ||
| migrations | ||
| rd_ui | ||
| redash | ||
| setup | ||
| tests | ||
| .coveragerc | ||
| .dockerignore | ||
| .env.example | ||
| .gitignore | ||
| .landscape.yaml | ||
| circle.yml | ||
| docker-compose-example.yml | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| manage.py | ||
| Procfile | ||
| Procfile.dev | ||
| Procfile.heroku | ||
| README.md | ||
| requirements_all_ds.txt | ||
| requirements_dev.txt | ||
| requirements_oracle_ds.txt | ||
| requirements.txt | ||
| Vagrantfile | ||
Some of you read the news about EverythingMe closing down. While more detailed announcement will come later (once more details are clear), I just wanted to reassure you that you shouldn't worry -- this won't affect the future of re:dash. I will keep maintaining re:dash, and might even be able to work more on it.
If you still have concerns, you're welcome to reach out to me directly -- arik@arikfr.com.
Arik.
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:
- 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.
- 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
- Setting up re:dash instance (includes links to ready made AWS/GCE images).
- Documentation.
Getting help
- Google Group (mailing list): the best place to get updates about new releases or ask general questions.
- Find us on gitter (chat).
- Contact Arik, the maintainer directly: arik@redash.io.
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 and make a pull request. We need all the help we can get!
License
See LICENSE file.