3 ms·
> it just requires ignoring almost every common or recommended Django pattern Indeed I'm already ignoring a lot of them. No forms or templates of any kind, nor
by scrollaway 6y ago
> it just requires ignoring almost every common or recommended Django pattern
Indeed I'm already ignoring a lot of them. No forms or templates of any kind, nor any of the stuff that is built for that (messages framework etc); only using DRF; stick to Postgres-only (I don't make much use of the db abstractions), etc.
The ORM is … nice, and has its limitations. I really just want to start using FastAPI by default but I'm concerned I'm setting myself up for a lot of busywork by skipping on such high-value niceties as the Django admin or DRF viewsets.
- ttymck 6y agoI think DRF Viewsets may be easy to replicate with the help of class based views from fastapi-utils[0] But I agree that Admin is still the missing killer feature from the fastapi ecosystem. But it looks like there is an emerging ORM/Admin combo heavily based on Django[1]. I've also considered (if you prefer SQLAlchemy) the possibility of instantiating a Flask/Flask-Admin wsgi app and mounting it on a running fastapi server, but haven't been able to confirm if that works yet. (EDIT: I just confirmed it does indeed work, and is rather painless.) [0] https://fastapi-utils.davidmontague.xyz/ https://fastapi-utils.davidmontague.xyz/ [1] https://github.com/long2ice/fastapi-admin https://github.com/long2ice/fastapi-admin