PKPDApp is an open source web-based application to explore, analyse and model the pharmacokinetics and pharmacodynamics of chemical compounds. The app is currently under heavy development, however a preliminary version is being deployed with Heroku and can be found under https://pkpdapp.herokuapp.com/.
Use these instructions for deploying the application in a production environment. Instructions for developers can be found below.
First clone the repository:
$ git clone https://github.com/pkpdapp-team/pkpdapp.git
$ cd pkpdapp
.env.prod
fileThe configuration of the production application is stored in the .env.prod
file in the root directory. Edit this file and variables to correspond to your particular setup, in particular make sure HOST_NAME
, DATABASE_URL
is set correctly and that SECRET_KEY
is altered from the default. The variables are described below:
DEBUG
: set to 0 for production
HOST_NAME
: the host name of the application
SECRET_KEY
: a large random string used for cryptographic signing
DATABASE_URL
: URL of a postgres database (e.g. postgres://username:password@postgres:5432/postgres). Note that any special characters in the password must be url-encoded. E.g. postgres://user:p#ssword!@localhost/foobar
should be written as postgres://user:p%23ssword!@localhost/foobar
.
RABBITMQ_DEFAULT_USER
: username for rabbitmq server (optional)
RABBITMQ_DEFAULT_PASS
: password for rabbitmq server (optional)
The following variables are used for LDAP authentication (optional):
AUTH_LDAP_USE
: set to 1 to use LDAP authenticationAUTH_LDAP_SERVER_URI
: URI of LDAP server (e.g. ldap://ldap.forumsys.com:389)For direct binding:
AUTH_LDAP_DIRECT_BIND
: set to 1 to bind directly to LDAP server (see hereAUTH_LDAP_BIND_DN_TEMPLATE
: template for direct binding (e.g. uid=%(user)s,dc=example,dc=com
)For search/bind, connecting to the LDAP server either anonymously or with a fixed account and searching for the distinguished name of the authenticating user.
AUTH_LDAP_BIND_DN
: distinguished name of an authorized user (e.g. cn=read-only-admin,dc=example,dc=com
)AUTH_LDAP_BIND_PASSWORD
: password for the authorized userAUTH_LDAP_SEARCH_BASE
: where to perform the search (e.g. ou=mathematicians,dc=example,dc=com
)AUTH_LDAP_SEARCH_BASE{i}
: additional search bases (optional, i
can be one of [2, 3, 4, 5]
). e.g. AUTH_LDAP_SEARCH_BASE2=ou=scientists,dc=example,dc=com
AUTH_LDAP_SEARCH_FILTER
: search filter based on authenticated username (uid=%(user)s
)AUTH_LDAP_USER_GROUP
: (optional) authentication will only succeed if user is in this LDAP group (e.g. cn=user,ou=groups,dc=example,dc=com
). If not set, then any user in the search base will be authenticated.AUTH_LDAP_ADMIN_GROUP
: (optional) user must be in this LDAP group to be a superuser (e.g. cn=admin,ou=groups,dc=example,dc=com
). If not set, then no user will be a superuser.There are also a number of optional variables that can be set:
VITE_APP_ROCHE
: set to true to enable Roche brandingVITE_APP_HELP_URL
: url of help page shown on loginVITE_APP_GA_ID
: Google Analytics ID to enable analytics.The application uses SSL certificates for HTTPS. You will need to supply your
own SSL certificate and key. These should be placed in the .certs/
directory
in the root folder (this folder needs to be created) and named pkpdapp.crt
and
pkpdapp.key
respectively.
The application uses a PostgreSQL database. You should supply your own
database and set the DATABASE_URL
variable in the .env.prod
file appropriately.
To add tutorial videos to the application, you will need to create a csv file with the following columns (the first line of the csv file should be the column names):
Title
: title of the videoType
: tab in which the video will be displayed (either Tutorial X
where X
is a number, Project
, Drug
, Model
, Trial Design
or Simulation
)Link
: link to the videoKeywords
: keywords associated with the video (optional)This file should be placed in the pkpdapp/static/
directory and named tutorial_videos.csv
.
To link to an external help page url, set the REACT_APP_HELP_URL
variable in the .env.prod
file to the url of the help page.
The application is deployed using docker containers and docker-compose, so you will need to install these.
To build the containers, run the following command in the root directory of the repository. This runs a script that builds the containers (using docker compose build
).
$ ./build.sh
You can run the container with:
$ docker-compose up
You should be able to see the web application at 127.0.0.1.
To leave the container running in the background, use
$ docker-compose up -d
If you are interested in developing PKPDApp with us, or just run the app locally, you can clone the repository and follow the installation instructions below.
NOTE: the current version of the frontend does not currently use the rabbitmq server, so you can skip the installation of rabbitmq for the moment (later iterations of the frontend will use the rabbitmq server).
Install sundials, python dev libraries and rabbitmq server
apt-get install libsundials-dev python3-dev rabbitmq-server
Note: if you are in WSL then the rabbitmq server will not automatically start, you
can start it manually using sudo -u rabbitmq rabbitmq-server
brew install sundials rabbitmq
Note: to restart rabbitmq after an upgrade: brew services restart rabbitmq
Set environment variables
.env
file in the root of the repository and edit the following environment
variables to correspond to your particular setup. The most important
variables to alter are those corresponding to secret keys and passwords, others
you can probably leave as-is.Install requirements
python3 -m venv env
source env/bin/activate
pip install -r requirements.txt
cd pkpdapp
python manage.py migrate
celery -A pkpdapp worker --loglevel=INFO
python manage.py runserver
python manage.py createsuperuser
Running the frontend will require a local installation of Node.js. On Ubuntu 20.04 LTS,
for example, you can install using snap
sudo snap install node --classic
It is also useful to install the yarn
package manager
npm install --global yarn
Navigate to the frontend/
directory and install the Node.js dependencies
cd frontend
yarn install
You can run the frontend using
yarn start
You should be able to see the pkpd web app at 127.0.0.1:3000.
We run a range of tests each time a commit is pushed to an open pull request using Github Actions. Passing these tests is prerequisite for merging a pull request. Some of these can be run locally as described below:
python run-tests.py --copyright
flake8
python manage.py test
runs everything; to run a single test in
a file (say) called test_models.py
use
python manage.py test pkpdapp.tests.test_models
The Django app has a custom management command that runs snapshot tests for all
the models in the database. The following script will generate snapshots from the
main branch, verify them on the development branch, then clean up the generated
snapshots. Run these commands from the pkpdapp
directory.
git checkout master
python manage.py test_snapshots
git checkout development
python manage.py test_snapshots
git clean -df
You can find the custom command in pkpdapp/pkpdapp/management/commands/test_snapshots.py
.
The front-end communicates with the back-end using a REST API. The API can be described using the OpenAPI specification. To generate the OpenAPI specification, run the following command:
python manage.py spectacular --color --file schema.yml
The front-end uses the Redux Toolkit RTX Query tool to automatically generate a client for the api based on the OpenAPI spec described above. To generate the client, run the following command in the frontend directory:
npx @rtk-query/codegen-openapi openapi-config.json
Install the cache using
$ sudo apt install memcached
Run memcached using
$ memcached -p 11211
PKPDApp is fully open source. For more information about its license, see LICENSE.md.