generated from opensafely-core/repo-template
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #231 from opensafely-core/adr-django
add adr for django
- Loading branch information
Showing
1 changed file
with
32 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# 5. Uee django framework for python backend | ||
|
||
Date: 2023-08-11 | ||
|
||
## Status | ||
|
||
Accepted | ||
|
||
## Context | ||
|
||
We need to provide a python http server to deliver the UI and handle the files. | ||
|
||
## Decision | ||
|
||
We will use the Django framework for two reasons | ||
|
||
- the team is very familiar with it | ||
- there's a high likelihood of needing a db for this project in future, and | ||
django has good support for migrations. | ||
|
||
## Consequences | ||
|
||
|
||
### Pros | ||
|
||
- familiarity | ||
- strong db support | ||
|
||
### Cons | ||
|
||
- larger dependency than needed for the initial scope | ||
- currenly uses in-memory db, which logs some spurious migration errors on startup |