DarkHelm.org/plex-playlist-old
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Adding more ADRs and libraries

Browse Source 
Signed-off-by: Cliff Hill <xlorep@darkhelm.org>
This commit is contained in:
Xlorep DarkHelm
2023-11-14 17:10:39 -05:00
parent bd49e0e747
commit 2da8757db7
5 changed files with 370 additions and 118 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/adrs/002-configuration-file-format.md
View File

@@ -13,7 +13,7 @@ SQL DB Table
## Rationale
Because the system already is using an SQL Database, it makes sense to use a SQL table to store these values in a simple way that then can be retrieved and updated using the same basic SQL components other parts of the application use.
Because the system already is using an SQL Database, it makes sense to use a SQL table to store these values in a simple way that then can be retrieved and updated using the same basic SQL components other parts of the application use. Actual application configuration would be through environment variales to comply with the 12-factor app.
## Status

2
docs/adrs/008-models.md → docs/adrs/008-db-models.md
View File

@@ -4,7 +4,7 @@ Database models can be constructed in a few different ways in SQLAlchemy.
## Decision
Models will be defined as dataclasses.
DB Models will be defined as dataclasses.
## Rationale

19
docs/adrs/009-db-migrations.md Normal file
View File

@@ -0,0 +1,19 @@
# ADR 009: Database Migrations
Database migrations will be important as the system evolves and changes, in order to protect the database and allow for everything to flow nicely.
## Decision
Alembic will be used for the database migrations.
## Rationale
Alembic is the defacto standard for SQLAlchemy migrations.
## Status
Accepted
## Consequences
Maintaining the SQL migrations will be key in order to ensure that the database is safely updated with changes as the code advances. It will be imperitive to keep the migrations up as the system is developed.