typesafedjango
| docker-django-react-example | typesafedjango | |
|---|---|---|
| 1 | 1 | |
| 6 | 6 | |
| - | - | |
| 2.2 | 5.7 | |
| 3 months ago | 3 months ago | |
| Python | Python | |
| - | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-django-react-example
-
Modern JavaScript for Django Developers
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.
typesafedjango
What are some alternatives?
esbuild - An extremely fast bundler for the web
django-bridge - Build fast, user-friendly applications with Django and React
django-rest-framework - Web APIs for Django. 🎸
django-unicorn - The magical reactive component framework for Django ✨