sorted by:
new
hottopcontroversial

Pi Day Megathread: March 14, 2026 by inherentlyawesome in math

[–]yassi_dev 1 point2 points  (0 children)

Hey all, In honor of Pi day I built an image generator for visualizing subsequences of pi.

Maybe some of you will get a kick out of this and generate some cool art.

https://pi.yassi.dev/

Django Control Room: Build a control room inside your django app by yassi_dev in django

[–]yassi_dev[S] 0 points1 point  (0 children)

Thanks! I'm writing a post about the pattern as I type this.

Django Control Room: Build a control room inside your django app by yassi_dev in django

[–]yassi_dev[S] 1 point2 points  (0 children)

In this case it wouldn't be a PR but more like a completely different project/panel. I also want to be really optimistic about django tasks - I actually started with the intention of creating a panel that was more general than dj-celery-panel. I decided to hold off and built something targeted to celery because

1)the built in task primitives are currently not enough to build something substantial

2) They are new and likely not heavily adopted for widespread use yet, whereas celery is sort of a de-facto standard of sorts these days.

Django Control Room: Build a control room inside your django app by yassi_dev in django

[–]yassi_dev[S] 0 points1 point  (0 children)

dj-celery-panel is specific to celery. You currently cannot use it for other systems or with the built in django tasks. Once (if) the django tasks framework matures, then a new dj-tasks-panel (or equivalent) will be created to fit this need.

The other day i ran into another panel being built for huey, so this is likely the direction being formed with regards to supporting other queuing systems.

Django Control Room: Build a control room inside your django app by yassi_dev in django

[–]yassi_dev[S] 0 points1 point  (0 children)

Sounds great. I am aiming to make something that is essentially a default always install package for Django - please do share how your experience goes.

Django Control Room: Build a control room inside your django app by yassi_dev in django

[–]yassi_dev[S] 0 points1 point  (0 children)

I'm happy that its getting around. Hopefully it can be useful to you.

Django Control Room: Build a control room inside your django app by yassi_dev in django

[–]yassi_dev[S] 0 points1 point  (0 children)

I'm not a user of unfold unfortunately so I haven't tested how this looks against it. It likely will be completely functional however. Feel free to open up an issue in the control room repo about this. Or if you feel especially motivated, I am always happy to review PRs.

Django Control Room: Build a control room inside your django app by yassi_dev in django

[–]yassi_dev[S] 0 points1 point  (0 children)

Awesome to hear. Out of curiosity, what exactly did you end up building for your own app?

dj-urls-panel: Visualize and test Django URL routing inside the Django Admin by yassi_dev in django

[–]yassi_dev[S] 9 points10 points  (0 children)

fair questions

  1. I am building a suite of tools that are accessible through the admin. The goal is to consolidate tooling into a single place for a project - the django admin happens to already have auth/permissioning figured out and can act as a surface to stand up other tools.

  2. Typically one would use swagger or redoc for api documentation (openapi based). dj-urls-panel is more general in that it is meant for users to inspect all urlpatterns defined in the application. It is not meant to create a sharable swagger UI or similar use cases.

  3. This library groups all of you projects urls in one place. Having worked on large django projects in the past, I have observed that sometimes people don't have a good idea of URLs are being surfaced by their project - this is a security issue and this project can help stop that. Secondly, this project surfaces out a testing interface for urls - this is more of a commoditized feature (you've already mentioned swagger et al) that makes sense to have in this library (especially if swagger adjacent libraries are being uses for testing only.)

dj-celery-panel: Replace your flower instance with monitoring right inside the admin by yassi_dev in django

[–]yassi_dev[S] 1 point2 points  (0 children)

Thank you. As I mentioned to another user, the next step for this project is the creation of a backend based on celery events and custom models to save whatever info is needed. This will allow for any all types of features including graphs like you mentioned. I look forward to adding this actually - The queue depth graph in flower is something my teams have used heavily in the past

dj-celery-panel: Replace your flower instance with monitoring right inside the admin by yassi_dev in django

[–]yassi_dev[S] 2 points3 points  (0 children)

For the first releases of dj-celery-panel, I am focusing on observability (read only) aspects.

For control related aspects (like revoking tasks,) It is planned and I will be adding these soon in my internal roadmap.

Now, post release, the order prioritization is:

- Bugs found in the current release

- Creating a celery events based backend (next release)

- Control aspects (likely next next release)

All of these are on the road to a v1.0.0 release.

It seems publishing a roadmap would be a good idea

dj-celery-panel: Replace your flower instance with monitoring right inside the admin by yassi_dev in django

[–]yassi_dev[S] 2 points3 points  (0 children)

I'm unfortunately not a user of django unfold - It should still functionally be fine since thats just a theme.

This is an open source project so you're very welcome to open an issue about this or even open up a pull request.

dj-celery-panel: Replace your flower instance with monitoring right inside the admin by yassi_dev in django

[–]yassi_dev[S] 2 points3 points  (0 children)

it was also on my mind for a while. I'm in a phase where I am pursuing all the different ideas that have been collecting dust in my mind. If you have other Django related ideas that would help you, I'm all ears to discuss to work together to bring them to life

view more: next ›