From e944d191ab0faf90b01aaa29ed8bf595179b9587 Mon Sep 17 00:00:00 2001
From: Jacek Lebioda <jacek.lebioda.001@student.uni.lu>
Date: Wed, 1 Feb 2017 09:13:56 +0100
Subject: [PATCH] Updated readme information
---
readme.md | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/readme.md b/readme.md
index 01d8a786..617e9c35 100644
--- a/readme.md
+++ b/readme.md
@@ -14,7 +14,7 @@
- `virtualenv env` to create new virtualenv (contains clean python working environment)
- `. env/bin/activate` (to start using virtualenv)
- `pip install -r requirements.txt` to install project's dependencies
- - Create `local_settings.py` file in `/scheduling-system/smash/smash` directory (see template below), and change your connection data:
+ - Create `local_settings.py` file in `(./scheduling-system)/smash/smash` directory (see template below), and change your database connection data:
```
# SECURITY WARNING: keep the secret key used in production secret!
@@ -44,11 +44,12 @@ DATABASES = {
}
}
-STATIC_ROOT = '/tmp/static'
+STATIC_ROOT = '/tmp/static' # Warning! `/tmp` directory can be flushed in any moment; use a persistent one; e.g. ~/tmp/static
+MEDIA_ROOT = '/tmp/media' # Warning! `/tmp` directory can be flushed in any moment; use a persistent one, e.g. ~/tmp/media
```
+ - Create the database by applying migrations (`./scheduling-system/smash/manage.py migrate`)
+ - Create the first, administrative, user- (`./scheduling-system/smash/manage.py createsuperuser`)
## Development
- Remember, that before working you have to activate _virtualenv_, by: `devel@host ~/home/smash/scheduling-system $ . env/bin/activate`
- In order to run development server, run: `devel@host ~/home/smash/scheduling-system/smash $ ./manage.py runserver` and go to `127.0.0.1:8000` in browser
-
-
--
GitLab