django-sql-dashboard VS Redash

I have a sister project to Datasette called Django SQL Dashboard which works against PostgreSQL databases: https://django-sql-dashboard.datasette.io

It used Django for the authentication layer but can otherwise work against any PostgreSQL database.

I partly built it to help explore what Datasette could look like if it expanded to work with more databases than SQLite. That's still something I'm considering doing in the future, via a plugin hook, but it's not on my short-term roadmap.

Reusable apps do exist (I released one myself a few months ago, https://django-sql-dashboard.datasette.io) but in most projects apps are single-use only - at which point they become little more than a code organization tool.

I use documentation systems that publish the documentation from the repo to a website. Most of my projects use Sphinx and reStructuredText for this, but I recently tried MyST (Markdown for Sphinx) and I like that a lot.

Some examples:

- https://docs.datasette.io serves documentation from https://github.com/simonw/datasette - which has documentation unit tests here: https://github.com/simonw/datasette

- https://django-sql-dashboard.datasette.io/ serves from markdown in https://github.com/simonw/django-sql-dashboard - I don't have documentation unit tests for that yet

Weirdly my Django SQL Dashboard project fits the bill a bit here: you can build up a "dashboard" (which is a tiny bit notebook-like if you squint at it the right way) with multiple SQL queries on it, and save that either as a bookmark or as a "saved dashboard" with a URL.

https://django-sql-dashboard.datasette.io/

In my own work I've been using it for the kind of things that I would normally use a Jupyter notebook for - gathering together research on problems I'm trying to solve.

It's hand-written CSS - there's not much of it: https://github.com/simonw/django-sql-dashboard/tree/01bb7e60...

I've been building a tool for this over the past couple of months called Django SQL Dashboard - it currently only works with PostgreSQL and you need to create a read-only database connection, but it then provides an interface for executing any bookmarking SQL queries plus some basic visualizations: https://github.com/simonw/django-sql-dashboard

It seems like there may be an issue with Watchdog on Apple Silicon.

I am looking for service or tool similiar to Metabase or Redash that allows me to add data source - for example Postgres connection, and create raw SQL queries that can be shared or exposed through API. So instead of keeping raw SQL code somewhere, my other service would call this tool e.g. http://microservice/query=1?param1=xx&page=2 and get the results from the DB. These calls are internal only and part of ETL processes, but of course authentication would be required.

Yeah, a lot of the time I'd agree with you.

This container came about for the Redash project (https://github.com/getredash/redash), which has been stuck on PostgreSQL 9.5 (!) for years.

Moving to a new PostgreSQL container version is easy enough for new installations, but rolling that kind of change out to an existing userbase isn't so pretty.

For people familiar with the command line, PostgreSQL, and Docker then no worries.

But a large number of Redash deployments seem to have been done by people not skilled in those things. "We deployed it from the Digital Ocean droplet / AWS image / etc!"

For those situations, something that takes care of the database upgrade process automatically is the better approach. :)

I have tried Metabase, Redash beore (both self hosted open source versions), from my experience I find Metabase a bit easy to work with.

Regarding visualization tools, sqliteviz has proven to be the best I've found so far. Their web app runs locally but has some trackers, so I run it locally via a simple, static HTTP server. Falcon and Redash seem like overkill for my needs.

Redash seems to be dead or at least in hibernation. There hasn't been a release in over a year.

https://github.com/getredash/redash/issues/5891

redash