From ccd241b5dfab445822a02d07a71251ab532cb33e Mon Sep 17 00:00:00 2001 From: Marco Zeisler Date: Tue, 4 May 2021 19:47:59 +0200 Subject: [PATCH] update; --- README.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 21ba491..5776611 100644 --- a/README.md +++ b/README.md @@ -4,12 +4,13 @@ * Angular for our single-page frontend * Django for our backend -* Database: TBD +* Database: sqlite3 We chose this specific stack because all of our team members have previously worked with this combination of Angular/Django and there is a lot of -documentation for it online. We have not yet settled on a technology for the -persistence layer. +documentation for it online. +We chose sqlite3 as persistence layer because it comes out of the box with django. Django +also provides a built-in ORM mapper. Our db schema is very simple, sqlite3 handles it well. ## Linting @@ -30,7 +31,10 @@ the `build` keys inside the `docker-compose.yml` file. The `docker-compose.yml` file builds the images by calling the `Dockerfiles` in the folders `frontend` and `backend`. The frontend is served via nginx on port -4200. The backend is served on port 8000. +4200. The backend is served via gunicorn on port 8000. + +The container's database folder is mounted to ./container_db of the host's docker-compose folder. Therefore, +the database is persisted at the client's filesystem. The docker images are available at: