https://djangocontrolroom.com/panels/dj-doom-panel
I built dj-doom-panel, a Django Control Room plugin that lets you play DOOM directly inside the Django admin.Its mostly a fun project, but it also shows that you can use the DCR framework for more than tooling.Enjoy.Official Site:https://djangocontrolroom.com/panels/dj-doom-panelSource:https://github.com/yassi/dj-doom-panel
I've published several panels under this banner already (tools for redis, caches, celery, etc.); I am currently working on a base library layer for tools to inherit from and to make it easier to create new tools.
Essentially, the point of all of this is to make it so that you don't need so many external services; Instead, DCR provides self hosted alternatives. This in turn makes it a lot easier to build and productionalize something using Django.
Reception has been decent so far and I estimate several thousand current adopters (Its hard to estimate based on download numbers alone.) For May I will finalize a common design language, further formalize the plugin system and how it works, and likely release a new panel.
The flames of hell: https://pi.yassi.dev/generator?start=747179&len=4096&mode=wa...
Looney Tunes Rings: https://pi.yassi.dev/generator?start=972784&len=16384&mode=r...
Dreamcast Logo: https://pi.yassi.dev/generator?start=809214&len=65536&mode=s...
Happy π Day!I built a small experiment that generates images from slices of the digits of π.Choose a starting digit, sequence size, renderer and make some art.
I am hoping this work makes it easier for people to start extending the admin in a normalized way.
I think there is a strong case for officially expanding the django admin to other use cases. I suppose this is a topic for another time
I think its good advice to avoid the admin for customer facing use cases. But for internal facing tools It seems pretty wasteful to not use the built in admin - it has all the bells as whistles to build upon (auth, permissions, etc.)
In my view. Building things with AI creates the need for common patterns and guardrails (i.e. frameworks) Then as these new apps become productionalized - tooling that fits your framework starts to become more important.
In that sense, AI increases the need for good patterns around observability. This project aims to make this a little easier to do for Django right from inside the framework as opposed to an external service.
I think even if AI handles more of the CRUD side, you still need to understand what’s happening in the system once it’s running - this is where this project fits in.
To your point about framework use because of AI: As more applications are being built because of lowering barriers, I think it makes sense for full stack monolithic frameworks to be used more frequently.
README and site were definitely optimized for speed over perfection. The panels themselves got a bit more attention.
Curious what you’d want to see improved on the docs/site side.
What I'm aiming for here is slightly different - keeping everything inside Django so there are no extra services to run or configure or proxy. As long as you surface the admin somewhere, then that is the place to find your tooling (including celery monitoring)
There will always be room for both approaches. A lightweight proxy/redirect could be something to explore in the future.
I think that explains some of the value for this project a bit better
https://github.com/yassi/dj-control-room
Over the past year I’ve been building a set of operational panels for Django:- Redis inspection - cache visibility - Celery task introspection - URL discovery and testingAll of these tools have been built inside the Django admin.Instead of jumping between tools like Flower, redis-cli, Swagger, or external services, I wanted something that sits where I’m already working.I’ve grouped these under...
https://github.com/yassi/dj-celery-panel
I built an open-source tool that surfaces Celery inspection data directly inside Django admin.The motivation was avoiding a separate Flower process and keeping operational context where Django teams already work. It uses swappable backends that support django-celery-results or even the celery inspect API directly for live communication with workersFeedback is welcome, especially from teams...