decouple mono-repo #303

New issue

Closed

opened 2025-04-07 21:39:49 +02:00 by kiara · 1 comment

kiara commented

2025-04-07 21:39:49 +02:00

Owner

while our django application is structured as a monolith, our repo currently has different things, many of which may not need to be in a mono-repo structure:

website (defunct) - can be archived
matrix (debian) - can be split off (archived?)
django application - #145 aside, architectural changes could loosen coupling for this with the above, allowing to split this out
deployment module - as per above, could potentially be split out after decoupling from django, but remains sort of coupled with application service templates, so maybe keep those together
application service templates
infrastructure - after detangling bits shared with deployment module, this could maybe be split out, tho CI would then need to update deps (#65)
- demo environment
- hard-coded application service test vms - hard-coded details that should probably be part of deployment state

while our django application is structured as a monolith, our repo currently has different things, many of which may not need to be in a mono-repo structure: - website (defunct) - can be archived - matrix (debian) - can be split off (archived?) - django application - #145 aside, architectural changes could loosen coupling for this with the above, allowing to split this out - deployment module - as per above, could potentially be split out after decoupling from django, but remains sort of coupled with application service templates, so maybe keep those together - application service templates - infrastructure - after detangling bits shared with deployment module, this could maybe be split out, tho CI would then need to update deps (#65) - demo environment - hard-coded application service test vms - hard-coded details that should probably be part of deployment state

Rows
Columns