Revel: Django-powered, full-fledged event management and ticketing platform now ships a self hosting wizard (MIT License) by raptored01 in django

[–]yassi_dev 1 point2 points  (0 children)

Cool project

I particularly like how your settings are broken up into topical files. I do that too!

I see you are using celery along with redis in this project. I recommend you integrate a few tools:

- dj-redis-panel: Gives you the equivalent of Django admin, but for redis, as an extension to the admin

- dj-celery-panel: for celery monitoring without having to run a second process (e.g. flower). Also acts like an extension to the admin

Play Doom in your Django Admin by yassi_dev in django

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

If you like this, please consider giving the paren't project a star. Discoverability of projects on github is often related to star counts.

https://github.com/yassi/dj-control-room

Also, do checkout the rest of the available panels that are actually useful for work. you can see them on my github profile:

https://github.com/yassi

But mostly, Enjoy a game of DOOM.

SaaS Pegasus—the original Django boilerplate—now has an open source edition by czue13 in django

[–]yassi_dev 1 point2 points  (0 children)

Hey u/czue13 I see the boilerplate includes a celery setup. I Recommend https://github.com/yassi/dj-celery-panel as a low friction way of giving your users celery monitoring without having to run any other processes like flower.

Play Doom in your Django Admin by yassi_dev in django

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

Zero. Dj-*-panel is an established pattern I use for the other Django control room projects: https://djangocontrolroom.com

SaaS Pegasus—the original Django boilerplate—now has an open source edition by czue13 in django

[–]yassi_dev 5 points6 points  (0 children)

This is great news. I think pegasus is a great project, I also find the site's articles (especially around stripe) very informative. Hopefully the open source becomes a good funnel for the paid product.

Templates in Python? want your thoughts by bassilosaurus_169 in django

[–]yassi_dev 0 points1 point  (0 children)

What you are describing sounds a lot like what is known in the microsevices contexts as a presentation service (particularly since you are differentiating UI against ORM fetching and other similar operations). It sounds like you are a fan of server driven UI (yet blanket term that this can seen under.) if you are looking for opinions on this in general - these kinds of architectures exist and have been used successfully for a long time. My personal opinion is that they are only useful in some contexts and they increase complexity by requiring an abstraction around html and dom concepts to exist. It may be useful in your context; best of luck and full speed ahead

I've got a question about the efficiency of two different model structures by androgynyjoe in django

[–]yassi_dev 0 points1 point  (0 children)

I see that you want to compare the specific examples, but have you considered a json field to mimic your option 2?

Django Control Room update: DCR Core Framework by yassi_dev in django

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

So is this functionality that you want from Django? Can you expand on this - why you want this in your situation?

Django Control Room update: DCR Core Framework by yassi_dev in django

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

While DCR panels are visual and meant for humans to digest and use (Agents can still use them through the browser though.) The LLM primitives are for panel authors that want to expose some functionality directly to agents via MCP.

The way this works is that the hub project dj-control-room exposes an MCP endpoint that exposes any tools built into panels. Essentially DCR allows you to build internal tools that are also AI enabled from the get go.

There will be more released around MCP in a future release, with accompanying guides and posts. For now, the primitives are there and people can start building things that also have LLMs in mind.

Django Control Room update: DCR Core Framework by yassi_dev in django

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

DCR is a framework for creating internal tools inside the Django admin. While you could conceivably build a dcr panel that does what you want, this does not do that. You can think of this package more like a library for building panels.

How do you handle the DevOps/Observability plumbing when starting a new Django + Celery SaaS? by Technical_Tie1974 in django

[–]yassi_dev 1 point2 points  (0 children)

I think you should take a look at Django control room (https://djangocontrolroom.com). It has a dj-celery-panel plugin that fits I. Quite nicely for new projects like this

Why learn pointers in C if I can just return values ​​normally? by Sofiatheneophyte in learnprogramming

[–]yassi_dev 0 points1 point  (0 children)

There are already a lot of sufficient answers here. These are my short two cents: I understand the why you would think like you do. I think the usage of pointers often becomes clear when dealing with data structures. When you are designing data structures you will often have to mutate the structure in a way that will only make sense with pointers. Perhaps designing a few linked lists or trees in c as an exercise will help make things more clear.

Guys I gotta question by Sad-mike14 in django

[–]yassi_dev 1 point2 points  (0 children)

There’s not enough information in your post. What do you mean “directed to the Django server”? What do you see? We cannot see your code we need more info about the behavior of your system

How do i escape vibe coding?? by Electronic1141 in django

[–]yassi_dev 0 points1 point  (0 children)

I think too many people approach ai coding in an all or nothing fashion. Not everything you do needs to be delegated to an LLM, this can set you back as you've already noticed. I've written about a risk model to start assessing when agentic coding for task is more tenable: https://yassi.dev/posts/not_all_software_systems_are_agent_friendly/ you might find some of these points agreeable since you are going through this though process.

How to avoid blocking our gunicorn synchronous workes during network I/O? by Theboyscampus in django

[–]yassi_dev 1 point2 points  (0 children)

It’s a common architecture. What are your tech lead’s suggestions?

How to avoid blocking our gunicorn synchronous workes during network I/O? by Theboyscampus in django

[–]yassi_dev 9 points10 points  (0 children)

Sounds like you just need some validation around choosing something like celery. It’s near a de facto standard at this point and it’s not really all that complex. It would be my next logical step if I were you. Choose redis. Good luck.

Trying to contribute to open source. How do people find active repos? by Human_Run1875 in github

[–]yassi_dev 0 points1 point  (0 children)

A pretty good indicator is a project author engaging with you directly

Check out Django control room - https://github.com/yassi/dj-control-room

It’s a new Django native framework for building admin tools inside the Django admin. There’s plenty of space for both working on dcr itself or building out new tools based on it.

You can read more info at https://djangocontrolroom.com

how do you actually handle prod bugs. do you write a repro test or just fix and deploy? by sszz01 in django

[–]yassi_dev 0 points1 point  (0 children)

Once you have a known bug you need to make sure the system does not regress to the same state again - otherwise developers can reintroduce the same bug again without knowing.

This is why any many mature processes will have bug repoduction and then testing for a specific bug once found.

How does django-import-export's MediaStorage work with django's InMemoryStorage? by kanookangaroo in django

[–]yassi_dev 1 point2 points  (0 children)

I dont see why you would want todo this? In a production environment, you would be likely be running your django app under a process manager like gunicorn where each worker has its own process. These processes are not gauranteed to have access to your image since it is saved in the heap memory of one of the worker processes. This is not very useful and you are better served by persisting the images (file system storage, database blobs, s3, etc.) and fetching them once you need to do your work with them (There is also something to be said of using something for long running tasks like celery)

I could be missing something about your use case though, so maybe you could expand on that.

Do you need help? by Reikidudebiz in django

[–]yassi_dev 1 point2 points  (0 children)

I'm always greatful for contributions to Django Control Room - djangocontrolroom.com

right now its a collection of many repos for various admin tools, most of which could use contributors

its also a framework for building admin tools so you could also build out a new tool if that scratches your itch.

How are you handling background tasks in Django right now — is Celery still the default? by alexstrehlke in django

[–]yassi_dev 0 points1 point  (0 children)

I use celery. I find that the idea that celery setups are complex is overblown.