These are chat archives for getredash/redash

13th
Dec 2017
RoyWiggins
@RoyWiggins
Dec 13 2017 00:24
incidentally it's not rendering tables properly either, even though it has test cases for tables so you'd think it would https://github.com/evilstreak/markdown-js/blob/master/test/features/tables/simple_leading.text
Arik Fraimovich
@arikfr
Dec 13 2017 09:34
@jerluc there are various things in the system that "belong" to a user. Having everyone use the same user will create a mess.

@RoyWiggins re. HTML: yes, it's no longer supported. What were you using it for?

As for tables - can you share a screenshot of how it looks like?

📣 We recently started a significant effort on improving Redash's user experience and look & feel. The lead on this effort is @kocsmy and you can track the progress (and join the discussion) using this GitHub board: https://github.com/getredash/redash/projects/2.
RoyWiggins
@RoyWiggins
Dec 13 2017 15:09
We were using it to embed a meta-dashboard with buttons as links to other dashboards. That can live as its own page
but it was nice to have it inside Redash proper for consistency's sake
as for tables- it's just not parsing the table syntax at all and interpreting it as plain text instead of spitting out an HTML table.
RoyWiggins
@RoyWiggins
Dec 13 2017 15:15
(the meta-dashboard also had a couple of search boxes which forwarded you to a search-dashboard, dropdown menus to pick common sets of dashboard parameters, that sort of thing)
sunil kumar
@vytla102_twitter
Dec 13 2017 17:13
Any help on my last question ..? @arikfr
Arik Fraimovich
@arikfr
Dec 13 2017 19:47
@vytla102_twitter which one?
sunil kumar
@vytla102_twitter
Dec 13 2017 19:48
I have an weird issue. I have two redash servers in AWS, second redash server uses and connects to the first redash server DB URL within some changes in the env variable and I am using same security group for both the redash servers and I have modified my SG that it allows all the traffic ingress within the security group only, But after sometime Second redash server was unable to connect to the master and redash was down. So I have to open the postgresql port explicitly with the second server ip as a inbound rule and eveyrthing works well. I wonder I am already allowing all traffic within the security group and why it doesnt work until unless I create a new inbound rule opening the posgresql port with the second server IP ..? Any idea ..? @arikfr
Arik Fraimovich
@arikfr
Dec 13 2017 19:49
This is weird indeed. Maybe something to do with private vs. public IP address and the IP address your postgres binds with? Anyway, this doesn't seem specific to Redash so you might have more luck in an AWS forum...