This repository has been archived by the owner on Oct 31, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Developers Guide
Helen Burns edited this page Apr 29, 2019
·
6 revisions
🚧 Under development 🚧
- clone repo
-
conda env create -f fortis.yml
2b.conda activate fortis
- Initialise postgres data base if not done already
initdb -D ~/postgresdata/
3b. if you already have a different postgress folder modify.env
accordingly source .env
createdb FORTIS
- edit layout.html (comment out script with comment
<!-- FORCE https script -->
) not for local servers python manage.py db upgrade
- CEMAC staff - Decrypt credentials.json. Others - follow Google API instructions to generate credentials file
python manage.py runserver
- make your edits and test
- Update requirements.txt etc
conda env export | grep -v "^prefix: " > fortis.yml
- edit layout.html (uncomment out script with comment
<!-- FORCE https script -->
) gives https capability on heroku - Follow generating users guide
- Prerequiste - have heroku account and in install CLI
heroku login
heroku create --remote staging --app fortis-training
git config heroku.remote staging
-
git push heroku <branch name>
I ofter
NB app was set up as pipenv installed packages - requires effort to switch this Options update dependencies on live app:
- Switch to conda on heroku - possible but perhaps why risk breaking something that works
- make a pip install-able requiremnts.txt and create a pip env and lock from that
- i.e remove
=py[a-z,0-9]{2,}_[0-0]{1,}
- replace = with ==
- replace "== with "<= in generated pipfile
- run
pipenv install --skip-lock
to install packages
- i.e remove
- small changes simply edit Pipfile manually