docker-django-react-example VS django-rest-framework

So I actually recently dealt with this, sharing this as hopefully it helps you.

https://github.com/ospira/docker-django-react-example

In essence, you need two instances of VSCode running connected to two separate Docker container instances. As I understand it, it's one remote container per VSCode window. Thus, I found this to be best, even though it isn't strictly speaking necessary, but it ends up feeling that way because as you said the language server integration (intellisense and extensions) will not work properly if not connected to the right container.

If you load this up in vs code it should prompt you properly given the presence of the files in `.devcontainter` dir. Having two windows in VSCode is kind of annoying at first, but I found it was actually fine, especially on macOS where tabbing to the other VSCode window (as opposed to ungrouped alt+tab on windows) was painless, and also kept me more organized not having backend and frontend code right next to each other.

Explore the Django REST Framework Documentation for advanced topics.

I've seen some companies using React with Django REST Framework [1], to keep the benefits of Django (I'm not a Django dev so I will have to guess, the ORM and project structure?) while having a strong separation between front and back (separate projects, teams, deploys, etc).

[1] https://www.django-rest-framework.org

Django REST Framework is a powerful and flexible toolkit for building Web APIs using Django, the popular high-level Python web framework. Zuplo proudly sponsors the DRF project to continue improving the Django API development ecosystem.

I think people tend to consider Django either for building old-school, industrial-strength monolith apps or for APIs and using something like React for the front-end. I’m here to tell you that plain old Django is a great option even for your personal websites! In my opinion, if you need a database, you should use Django1.

This post will extend Django REST Framework's ViewSet and SimpleRouter to provide a Rails-like request handler class + resource routing in server-render Django applications. It also features form-level method spoofing for PUT, PATCH and DELETE requests via custom middleware.

Django Rest Framework

When developing a SaaS application, you might choose to create a REST API and use a frontend framework like React.js or Vue.js. In this case you'd have two choices, one go with Django rest framework or go with Django ninja

- Django Rest Framework has no async support? https://github.com/encode/django-rest-framework/issues/7260

A URL shortener is a service that transforms long and complex URLs into short, easily memorable ones. This tutorial guides you through creating a URL shortener using Django REST framework and Postgres, deploying it on Koyeb.

Now, I'm converting this app into a Vue-based SPA (still powered by Django). I'm using the Django REST Framework to build the API that the SPA will interact with. (I'll be using token-based auth, via django-rest-knox. ETA: I'll actually be using djangorestframework-simplejwt.)