reactiveservices VS cookiecutter-django

https://github.com/intelix/reactiveservices

And the screenshot is the early version of the real app built on it

Conceptually it's the same to what described in conductor, however you are in full control how the data is synced, how and to what you subscribe etc.

It was built, first of all, for the application in forex trading, so there are some "specific" features, such as optimised binary stream with delta-only updates, priority on the data streams, demand-based backpressure, subscription based on the visibility of the data, very low latency, cross-dc clusters and many more.

How it works is described (in rather over-simplified way) on the github page. There's a choice of scala or java on the back end, and react on the client side. Websocket only. Like I mentioned, the currently exposed source code is not maintained and based on the very version of react (there are still mixins in the example), and has some vulnerabilities.

The latest version of the framework is maintained in the private repo, and we have built a number of solutions on it over the years, and not only in the forex space. It is well suited for most Single-page apps.

Latest version uses latest react features, hooks based, and the server side has seen significant changes as well.

Why we decided to keep it private? We thought world already have enough web frameworks, and since, we thought, our framework and approach was such a niche, we just kept using it for our clients and our own projects. But since then we have been surprised how easily it could be applied to other fields, and yet there's still nothing like this is available. GraphQL with subscriptions probably is the closes, but not good enough.

Is there any interest in something like this in the community? If so, we can definitely make large parts of the framework, which is now 6yo, public.

cookiecutter https://github.com/pydanny/cookiecutter-django

"1" is definitely something I'd like the team to focus on. Cookie-cutter django aims at it (https://github.com/pydanny/cookiecutter-django) but IDK I think it goes a little too far, and we should have better out-of-the-box options. I think we have this situation because of the unwillingness to make backward incompatible changes.

Use Django Environ for secret keys etc, have a look at 12 factor https://12factor.net and https://github.com/pydanny/cookiecutter-django for a solid example of a best practise setup.

Have you seen https://github.com/pydanny/cookiecutter-django ?

I don't have production level examples but cookie cutter django covers setting up points 3,4,6 https://github.com/pydanny/cookiecutter-django for you. django-allauth for point 6

You really should take a look at cookiecutter it makes bootstrapping projects easier and more customizable. You can also peek at cookiecutter Django.