update;
This commit is contained in:
parent
6abe9ebc35
commit
ccd241b5df
12
README.md
12
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:
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user