django-ninja VS microblog

Django Ninja [1], it forever changed how I write Django project, in a way so elegant and productive.

[1]: https://django-ninja.dev/

Django Ninja is a RESTful wrapper for Django, while UtilMeta Python Framework uses a more concise declarative ORM Schema for Django and other future-supporting ORMs like sqlachemy and Peewee to build RESTful APIs more efficiently, and supports not only Django but all Python mainstream frameworks like Django, Flask, Starlette, FastAPI, Sanic, Tornado, etc.

I can't recommend [django-ninja](https://github.com/vitalik/django-ninja) enough. It's an easy to use, extremely fast, typed API for django. I've found it to be better in almost all aspects when compared to djangorestframework.

It's gaining popularity but is still widely unknown.

> The only place I really see Django at large companies is as an api using DRF or something.

This is not a bad thing. Using Django as an API backend is amazingly fast in terms of development time, especially with modern frameworks such as django-ninja [1].

Just use the built-in ORM to create models, write your endpoints, and use the built-in admin interface to play with the database if you don't have endpoints for everything.

There is also a less known feature of Django called admindocs [2], which automatically generates a human readable, hyperlinked documentation for your models and relations between them.

[1] https://django-ninja.rest-framework.com/

[2] https://docs.djangoproject.com/en/4.2/ref/contrib/admin/admi...

Personally, I also prefer django-ninja to DRF.

Actually that's not fully true. If you mix async and sync codes in django-ninja there will be some errors. Where's the proof ? django-ninja doesn't support async auth

Subscribe to this issue :D

Also recommend Django-Ninja. It basically reimplements fastapi's type and decorator-based API construction, but embedded directly in django so you have access to django's ORM and middleware library.

In this blog, we're going to address the "on any website" part of a Search Solution. Or at least - propose a starting point for it. There are many great tutorials out there for a deep dive on Flask - one of the best from my colleague Miguel.

- https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial...

If you'd like to deploy a web app, Flask is your best friend. It's very user friendly and there's a lot of great tutorials online. The only thing you'd need other than Python knowledge is some basic understanding of HTML/CSS and Jinja notation for variables, both of which are pretty intuitive to learn. Good luck!

I can't speak highly enough of Miguel Grinberg's work with Python/Flask (https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial...) and the community he's created around it, for both beginners and advanced folks.

Racing through his mega tutorial was a great refresher for me on the fundamentals, and it's easy to plug in computer vision & related libraries/extensions/packages.

Use miguel grinberg’s tutorial https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-i-hello-world

I got a recommendation (from a few places) to use Miguel Grinberg's microblog series to help me get up to speed on some flask things. I'm on ch 15 with blueprints, and am running into pylint cyclic import errors, both on my app and in the actual project (https://github.com/miguelgrinberg/microblog/tree/v0.15?search=1)

In the project root directory create a folder called static with one subfolder called js and another called css. The js folder will contain all of the needed local JavaScript files while the css folder will contain all the CSS stylesheets. In the js folder create a file called index.js and in the css folder one called style.css. Just leave them empty for now. If you want to find out more about web development with Flask I suggest you try out this tutorial. Your current project structure should like this:

https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-i-hello-world is not perfect, but a great start.