Django architecture

leo_nexus_nl

Hi,

I read the books: Django for Beginners, Build a Website with Django and Mastering Django and went through the turtorial on the Django Project website.

I am struggling with the arhcitecture of the web application. I need a custom admin site for the superuser and staff users in which I manage the models, I need a backend in which non-staff/non-superuser users manage their content, and I need a frontend.

The models will be the same for all three, the views and templates will be different.

I thought of a structure like this:

venv/
backend/
    backend/
    manage.py
    myapp1/
    myapp2/
frontend/
    frontend/
    manage.py
    myapp1/
    myapp2/
myadmin/
    myadmin/
    manage.py
    myapp1/
        models.py
    myapp2/
        models.py

So, basically three projects with separate apps for the different components. Each project
will be referenced by a sub.domain

Any comment on this idea will be very much appreciated.

Kind regards,

Annet

aliviapope1

Splitting your Django project into separate directories like backend, frontend, and myadmin makes sense, especially if you’re aiming to keep things organized for different user roles and content types.

Inugakoo

In my view, using subdomains for each (admin, user backend, frontend) also sounds like a good way to keep things separate.

One thing to watch out for is the models. Since they all need to share the same database, you’ll want to make sure each project points to a single set of models so you’re not duplicating stuff or dealing with syncing headaches.

If you’re aiming to scale this or want to think about the bigger structure, checking out something like the TOGAF EA Foundation and Practitioner Course (https://www.advisedskills.com/enterprise-architecture/togaf-ea-foundation-and-practitioner-level-1-and-2) could give you some ideas on managing bigger architecture setups. Well, it helped me a lot when thinking through more complex setups that need to grow over time.