arikfr

(Redash author)

Having a single executable is definitely the best, and I wish we had one for Readsh... trying to compensate on this with the Docker and cloud (AWS / GCE) images for easy setup.

(Redash author)

Step by step instructions could be great, but there is that much time in the day, so figured that anyone who wants to customize the deployment, will know how do it on his own (or use the bootstrap script for reference).

I'll be happy to answer questions on how to set it up in your environment, you're welcome to the forum[1], Gitter[2] or Slack[3].

[1] https://discuss.redash.io [2] https://gitter.im/getredash/redash [3] https://slack.redash.io

> queue parallel queries to the same data source

That's definitely possible. You might need to tune the number of workers you have to run queries (and maybe adjust your database settings, if it has limits on concurrency).

If you need help with this, you're welcome to the forum[1], Gitter[2] or Slack[3].

[1] https://discuss.redash.io [2] https://gitter.im/getredash/redash [3] https://slack.redash.io

The "::filter" convention is filters. We also have parameters (for some time now, although only in v0.11 added UI for them). With parameters you can do:

SELECT country_code AS "cc::filter", COUNT(1) as num_users FROM mytable WHERE lifetime_spend > {{minimum_lifetime_spend}} GROUP BY country_code

And minimum_lifetime_spend will render as an input box. Currently we only support input boxes (of different types - number/string/date), but there is a plan to add support for dropdowns there as well.

Allowing self serving without knowing SQL is the goal, but I believe it will take time to do it right. We focus on delivering a great product for people who know SQL, and allow them to give more interactive result sets to other users using things like parameters.

So not sure if our goal is less ambitious, but we just take a different path. And that's good I guess, it would've been not interesting if everyone built the same thing, the same way :-)

(Redash author)

You will need to allow access from our servers to your database. It's obviously a security concern, but we take great measures to ensure the safety of your data.

If that's not an option, you can always run Redash self hosted.

Thank you for proving it's not only for "tech people", and that "normals" can pass the SQL barrier too :) (and learn a useful skill on the way)

(Redash author here)

I was really hoping to address this in the upcoming v1.0.0 release, but eventually didn't want to delay it as it was in the oven for too long anyway. It will probably be addressed in the release after.

Beside the ability to delete a user have you experienced other rough edges in the recent releases? We strive to improve the stability and reduce the rough edges with every release, so really want to hear about your experience.

Thanks <3. Always enjoy seeing what Eli does with Redash & Zapier. Really looking forward for when the Zapier integration becomes official and goes into their directory.

Hi! I'm the author of Redash :) Nice to see Redash at the top of HN.

I'll be happy to answer any questions about Redash, open source and about my journey to make Redash a self sustainable project.

For any questions that don't fit on HN, feel free to reach me at arik at redash.io.

Re. filtering: do you mean something like parameters? Because that's supported.

1. The easiest thing is to give commentary from the sidelines. Ignore them.

2. Making the product, simple or complex is the easy part. The hard part is making a business out of it.

I'm in a similar situation to yours (creating a company, bootstrapped, solo founder). It's a hard ride and people who can truly support you mentally is important.

I've been running Docker in production for half this time and got pretty much to the same conclusion. ECS has its issues, but is still much more manageable than anything else (on AWS). And if started today, would've definitely used Convox (iirc, at the time you didn't support private subnets).

I never liked Cloudwatch Logs and recently switched it for an ELK stack (hosted by logit.io).

Thanks for mentioning Redash! (I'm the author) It's actually not that new -- I've been working on it for 3 years now :-)

Thanks!

I would love to understand what you're missing in Redash. If it's too much for a comment here, feel free to email me (arik at redash.io).

I guess that's the kind of polish VC money buys :-) I went the bootstrap/community route. But I hope that in about two months we will have funds to hire a UI/UX designer to improve the user experience and general look and feel.

I hope you don't mind the self plug: I think Metabase has support for raw SQL, but if you find it hard to translate to Metabase "questions", it sure will be easy to translate into queries in Redash... In Redash you create visualizations from regular SQL queries (although we do support adding parameters and such).

https://redash.io https://github.com/getredash/redash

Disclaimer: I'm the author/founder of Redash.

There aren't many SaaS services I can think of that can be truly hands-off to the extent that you can backpack with a free mind. Also scaling a SaaS business takes time and significant effort.

All of the above is from personal experience.

If I were looking for passive income from software I would've looked at desktop software.

Super! Thanks.

"if you avoid" - you mean if I just include specific icons from the Pro version?

I just wonder how licensing for the pro version works in regards to open source projects? If I buy the license, can I use it for my open source project?

Also the option to commission your own icon is really exciting! :-)

I wonder if they could sell their domain name to cover some of their debt... 4 letter .com domains are hard to come by.

How do you imagine Cuomo's anti-BDS law could affect him?

Have you considered using Re:dash[1] before writing your own tool?

[1] https://github.com/getredash/redash

Are you using Re:dash[1]? Seems like a good fit if you're doing lots of SQL and working with many different databases.

[1] http://redash.io/

If anyone wants to play with this dataset, and easily share his queries or visualize the data, you're welcome to use re:dash's demo instance [1]. I've also created an example query [2].

[1] http://demo.redash.io [2] http://demo.redash.io/queries/667/source#table

As I'm interested in this myself, what companies are you studying?

But if I have 15, then it's $13.3 per node. And at my work place we have >100, which means >$36 per node.

That's a lot.

re:dash author here if anyone has any questions.

Our company (EverythingMe) had a very similar journey to the one Samson describes (Splunk, MySQL, logs, ... -> Redshift). At the time Persicope wasn't there (or we didn't find it), so we built re:dash instead.

Yes, Redash sends the query as is to the database. It currently supports PostgreSQL (& Redshift), MySQL, BigQuery, MongoDB, Graphite and Python scripts. Also someone currently working on ElasticSearch support.

The MonogDB & Graphite support is crude, but exists.

I'm the project maintainer, feel free to ask if you have any questions.

(I'm re:dash project maintainer/creator)

Embedding is something that we want to add, although currently not a priority for us internally. You can follow #320 [1] for updates and details on when it will be implemented.

Also, if you just want to try re:dash out there is a Vagrant box [2] and GCE/AWS images [3].

You can always ping me for help or details, either through the mailing list, GitHub Issues, Gitter or just by email (arik at arikfr dot com).

[1] https://github.com/EverythingMe/redash/issues/320 [2] https://vagrantcloud.com/redash/boxes/demo [3] https://github.com/EverythingMe/redash/wiki/Setting-up-re:da...