qfepweb

Development of the web interface to QligFEP.

Install for development

$ python -m venv qfepweb
$ cd qfepweb
$ source bin/activate
$ python -m pip install --upgrade pip
$ git clone [email protected]:GPCR-ModSim/qfepweb.git

At bin there is a file called activate. Create a new file called postactivate with the following contents:

export PYTHONPATH=$VIRTUAL_ENV/qfepweb
export DJANGO_SETTINGS_MODULE=qfepweb.settings

Load it with source bin/postactivate

$ cd qfepweb
$ pip install -r requirements_devel.txt

For the production environment install only this:

$ pip install -r requirements.txt

Create a file called .env besides the qfebweb/settings.py file and add the following lines. Never commit this file

DEBUG=on  # or off, for production
SECRET_KEY=somegoodrandomstring_atleast50length
# e.g. )Ql?ddAC3jMTybSHe^(vk@Sd=nTF#q&S5m:f$:U8O27^cr5S

If everything went smoothly, we could check Django testing page with:

$ django-admin runserver

First migration

You should have seen a warning like:

You have 18 unapplied migration(s)

The current database is the default db.sqlite3 (ignored by .gitignore). The pending migrations are the Django default tables. Apply it with:

$ python manage.py migrate

Continuous deployment

There's a dirty script to quickly apply everything needed at the server to sync with the code:

$ ./deploy.sh

This should work with any repo, except for the last command that restarts the systemctl unit which only works at the server. Other boxes might and should fail with:

Failed to restart qfepweb.service: Unit qfepweb.service not found.

General Notes

If you want to install using python3.6 and CentOS there's a big possibility of a version crash between sqlite3 < version 3.6.20 and Django 3.2. This means that it's recommended to make install from source at least for python 3.7.4 and then sqlite3 > version 3.6.20