Hey everyone! I hope to have more time today and this weekend to evaluate pants in more depth, but I thought I would ask a bit of advice first. Our repo is currently a monolithic django app and I want to move it to a monorepo with as little disruption as possible. To top it off, our repo structure is a bit unusual, but not that unusual for a django API. I wanted to see how people would approach adopting pants and a monorepo structure. Here is what our current structure currently looks like:

repo
├── compose
├── config
    ├── asgi.py
    └── settings
├── docker-compose.yml
├── manage.py
├── poetry.lock
├── proxy
├── pyproject.toml
├── setup.cfg
├── startup.py
├── staticfiles
└── api
    ├── accounts
    ├── authentication
    ├── celery.py
    ├── common
    ├── conftest.py
    ├── users
    └── util

Each django app under the api directory has

tests

directory for tests

So you have multiple apps but (for now at least) a single service that brings them all into a single settings.py?

yep

That's pretty common

Yep, and that has been very helpful! However, our sittings is at the top level. I realize we can move them into the

api

directory to solve the problem, but I was kind of hoping to get this working before making structural changes

Ah, so your settings.py is at the root? Not under config/settings?

the

config

directory holds the settings.py, wsgi.py, etc.

To clarify terms, how are you distinguishing "single project repo" from "monorepo". So do you have multiple repos with structure like the one you show above?

No, we only have the one repo above, but we do have a couple of separate deployable services (proxy, api) that share the same settings and django apps. I want to have better separation and modularity around this before it gets out of hand.

Gotcha