Dirk Alders 4a7549ec26 users library update | 1 month ago | |
---|---|---|
.vscode | 1 year ago | |
config_example | 1 month ago | |
data/media/theme | 4 years ago | |
fstools @ 9237f6f7f7 | 1 month ago | |
main | 1 month ago | |
mycreole @ 997594e371 | 2 months ago | |
patt @ 7ff8071be9 | 1 month ago | |
requirements | 1 month ago | |
stringtools @ e1f76d9631 | 3 years ago | |
themes @ b7673fa827 | 1 month ago | |
users @ a50e55daf1 | 1 month ago | |
.gitignore | 3 years ago | |
.gitmodules | 3 years ago | |
.project | 4 years ago | |
.pydevproject | 4 years ago | |
LICENSE | 4 years ago | |
README.md | 3 years ago | |
activate | 4 years ago | |
manage.py | 4 years ago | |
reposinit | 2 years ago | |
requirements.txt | 2 years ago |
Project and Teamorganisation Tool
cd ~/tmp
git clone https://git.mount-mockery.de/application/patt.git
cd patt
git submodule init
git submodule update
virtualenv -p /usr/bin/python3 venv
source activate
pip list -o --format freeze|cut -d '=' -f 1 | xargs pip install $1 --upgrade
pip install -r requirements.txt
cp config_example/config.py .
chmod 700 config.py
Edit config.py and add a SECRET_KEY. Generate the secret e.g by executing the following command:
python manage.py
At the End of the error message you’ll see a random secret:
KeyError: “You need to create a config.py file including at least a SECRET_KEY definition (e.g.: --> ‘HERE IS THE RANDOM SECRET ;-)’ <--).”
python manage.py migrate
python manage.py createsuperuser
Now there are two ways to finalise your configuration. The first way is for a test or development system. The other is for a production System.
Test or development System: Edit config.py and set the Variable DEBUG to True.
Production System: Edit config.py and set the Variable ALLOWED_HOSTS. Execute “python manage.py collectstatic” to create a folder including all static files. Then add PaTT to your server configuration. See also Django Documnetation for further information.
cd ~/tmp/patt
source activate
python manage.py runserver
source venv/bin/activate
python manage.py dumpdata --natural-foreign --natural-primary -e contenttypes -e sessions -e auth.Permission -e sessions -e patt --indent 2 > dump_base.json
python manage.py dumpdata --natural-foreign --natural-primary -e contenttypes -e sessions -e auth.Permission -e sessions patt --indent 2 > dump_patt.json
tar -cvzf dump_media.tgz data/media
source venv/bin/activate
If you are starting without a database, you need to create one
python manage.py migrate
Afterward add data step by step to the database.
python manage.py loaddata dump_base.json
python manage.py loaddata dump_patt.json
tar -xvzf dump_media.tgz