django-extensions
django-sql-dashboard
django-extensions | django-sql-dashboard | |
---|---|---|
12 | 8 | |
6,422 | 431 | |
0.3% | - | |
4.5 | 4.4 | |
7 days ago | about 2 months ago | |
Python | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
django-extensions
-
Ask HN: Anyone use a code to mindmap/flowchart tool?
django_extensions/utils/dia2django.py: https://github.com/django-extensions/django-extensions/blob/...
django_extensions/management/modelviz.py:
-
Color Django shell by development environment
I often perform operational tasks such as modifying data or debugging failures using the Django shell. In fact, anything I can't do through the admin or through management commands I use the shell for. The package django-extensions provides a shell on steroids that I much prefer over the built in shell. It allows you to run a custom REPL such as IPython or Ptpython and has autocomplete, command history, automatic model class imports and a myriad of other dev tools. shell_plus is for a Django programmer what a scalpel is for a surgeon.
-
How do I list all my endpoints across the whole project
It currently has a bug with the latest django update I think; so if it it isn't fixed by the time you try it, remember to check it out later, because django-extensions is genuinely useful.
-
Is it normal to forget a lot of commands despite having used them multiple times in the past?
alias m='exit_if_not_in_python_virtual_env && ./manage.py' alias mcs='exit_if_not_in_python_virtual_env && ./manage.py collectstatic' alias mcsu='exit_if_not_in_python_virtual_env && ./manage.py createsuperuser' alias mm='exit_if_not_in_python_virtual_env && ./manage.py migrate' alias mmm='exit_if_not_in_python_virtual_env && ./manage.py makemigrations' alias mrs='exit_if_not_in_python_virtual_env && ./manage.py runserver' alias ms='exit_if_not_in_python_virtual_env && ./manage.py shell' alias msa='exit_if_not_in_python_virtual_env && ./manage.py startapp' alias mt='exit_if_not_in_python_virtual_env && ./manage.py test' alias mts='exit_if_not_in_python_virtual_env && ./manage.py testserver' # [django-extension](https://github.com/django-extensions/django-extensions): alias msu="exit_if_not_in_python_virtual_env && ./manage.py show_urls" alias mvt="exit_if_not_in_python_virtual_env && ./manage.py validate_templates" alias msp="exit_if_not_in_python_virtual_env && ./manage.py shell_plus" alias mrsp="exit_if_not_in_python_virtual_env && ./manage.py runserver_plus"
-
Is there a way to enable sql tracing in Django?
I use https://github.com/django-extensions/django-extensions
-
How to get urls path from django views list ?
If you just want a list of all the available urls & paths in your app, take a look at the django-extensions package. It has a django management command show_urls, which will list them all out nicely.
-
django and the issue of doing too much under the hood
https://github.com/django-extensions/django-extensions has a command, show_urls which outputs the URLs rendered for a project along with the name of their view handler
-
Django for Startup Founders: A better software architecture for SaaS startups
# 1 million lines of logic and who knows how many queries
I've actually seen this pattern in every Django project :(
Regarding urls, instead of enforcing a flat file, I'd highly recommend always using django_extensions[0]. You'll get `shell_plus` that auto imports model and `show_urls` that you can grep for endpoint and gives you the handler.
[0] https://github.com/django-extensions/django-extensions
-
Failing the CI build if django migrations are out of date
A common mistake in django is to make a model change but forget to run makemigrations to generate a migration for the model change. Sometimes it is not entirely obvious when this need to happen. For example, let's say I'm using the django-extensions library and I define a model like:
-
Data Analysis with Django
Django Extensions has a shell_plus with notebook mode.
django-sql-dashboard
-
Datasette is my data hammer
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.
- How do you log all API calls in your application?
- Saving Filtered Querysets for Future Access
-
Do I need to create seperate app for a dashboard?
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.
-
Why is uncoupled documentation bad?
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
-
Dataflow, a self-hosted Observable Notebook Editor
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.
-
Show HN: Django SQL Dashboard
It's hand-written CSS - there's not much of it: https://github.com/simonw/django-sql-dashboard/tree/01bb7e60...
-
Data Analysis with Django
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
What are some alternatives?
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
Redash - Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
re-frame - A ClojureScript framework for building user interfaces, leveraging React
scripts-to-rule-them-all - Set of boilerplate scripts describing the normalized script pattern that GitHub uses in its projects.
django-crispy-forms - The best way to have DRY Django forms. The app provides a tag and filter that lets you quickly render forms in a div format while providing an enormous amount of capability to configure and control the rendered HTML.
Docusaurus - Easy to maintain open source documentation websites.
django-seed - :seedling: Seed your Django database with fake data
django-sql-explorer - Easily share data across your company via SQL queries. From Grove Collab.
Django - The Web framework for perfectionists with deadlines.
dash - Data Apps & Dashboards for Python. No JavaScript Required.
django-b2 - Django backblaze b2 storage using b2sdk. Maybe useful for easier access to b2 outside of Django too. Plus: script to upload a (backup) file and tool to backup the postgres database.
papermill - 📚 Parameterize, execute, and analyze notebooks