04 schrieb Piyush Prasad:
Why not use a mono repo?
*From:* django-developers@googlegroups.com
on behalf of Alex Sonar
*Sent:* Sunday, April 2, 2023 10:21:33 PM
*To:* Django developers (Contributions to Django itself)
*Subject:* Re
Why not use a mono repo?
From: django-developers@googlegroups.com
on behalf of Alex Sonar
Sent: Sunday, April 2, 2023 10:21:33 PM
To: Django developers (Contributions to Django itself)
Subject: Re: The problem of versioning a large project.
It is about one
I'm not sure your issue is Django-specific, so it may be off-topic for this
group. However, your question is a bit vague to be appropriate for Stack
Overflow or other forums either.
"Versioning" could mean a few things. At first, I thought you meant
something like date-based or semantic version
It is about one project that includes many applications.
We would like to separate the repository specifically for front-end guest
groups.
With access to parts like: views_groups, templates, dummy_data,
forms_group, helpers_group, static_blob and media_blob as an example.
Now our application t
>Now we have organized versioning, where our project is divided into
separate GIT repositories which are created for each application.
why? what's the reasoning for this? django already has apps, so why do you
need to make multiple projects for single components?
On Friday, March 31, 2023 at 1
Like Aharon, I'm not entirely certain what you mean but this line:
> The task looks like bad practice, where we have to create a repository
within another one.
reminded me of git submodules, which I don't think are considered bad
practice. Is that what you mean?
On Thursday, March 30, 2023 at 5:
Could you give more information, please?
the project structure provided to your GIT repository
It is not entirely clear how you perform separation by application
среда, 29 марта 2023 г. в 23:17:41 UTC+3, Alex Sonar:
> The problem of versioning a large project.
>
> Hi guys, I really got stuck wit
