Alexis Yushin

The (working) setup I have right now: ``` settings ├── __init__.py ├── base.py ├── local.py ├── production.py ├── sections │   ├── __init__.py │   ├── accounts.py │   ├── admin.py │   ├──...

> gotcha thanks for adding this!! I agree this is so much more manageable, but I like the current way our `production.py` makes sure there are no defaults in `production.py`....

No need for separate database and prod_database again: sections/base.py: ``` import environ from pathlib import Path env = environ.Env( DJANGO_LOG_LEVEL=(str, 'INFO'), DOMAIN=(str, 'turnaround.aero'), ) ROOT_DIR = Path(__file__).resolve(strict=True).parent.parent.parent.parent APPS_DIR = ROOT_DIR...

~~The only issue I'm still wondering about is how to make sure I also import `if DEBUG: ...` kind of settings, cause `from X import *` seem to ignore those~~...

A lot of interesting insights! https://gitlab.com/glitchtip/glitchtip-helm-chart/-/issues/5#note_451868819

Great, I'll make a start this week and we take it from there.

we already running a number of django projects internally with helm, i think i can make our charts open source. the work would be to tailor them to the actual...

Hi, I am sorry I just realised that I published our internal helm charts in December but never posted the link. https://github.com/apexlabs-ai/django-helm-charts

So, I guess there a number of things we should made configurable (some are already in the helm chart): - postgres deployment / external database - redis deployment / external...

Those are hard problems! :-) For some reason component-resource_type sounds more logical, I guess you are more interested to see the files grouped by component vs by the resource type....