This project is based on VecNet-CI - https://github.com/vecnet/vnetsource

OpenMalaria portal is a user-friendly web interface for OpenMalaria model. User can create simulation, define environment and explore effect of interventions (drugs, spraying, bednets) on malaria transmission levels. Model can be executed from the web interface using our high-performance cluster. Model output can be easily visualized or downloaded for further processing.

This Django project has been tested on Windows 8 x64, RedHat 7 and CentOS 7

• Django 1.11
• Python 2.7
• PostgreSQL 9.4
• Apache 2.4

1. Set a local SECRET_KEY and use local settings module.

   export SECRET_KEY=some-value
   export DJANGO_SETTINGS_MODULE=website.settings.local

2. Create database structures ./manage.py migrate

3. Check if there are database migrations by reviewing the list of known migrations: ./manage.py migrate --list

4. Create an admin user ./manage.py createsuperuser

5. Load fixtures

   python manage.py loaddata AnophelesSnippets
   python manage.py loaddata BaselineScenarios
   python manage.py loaddata DemographicsSnippets
   python manage.py loaddata Interventions

6. Run the server.

python manage.py runserver

docker-compose up

1. Create Virtualbox VM vagrant up. It may take a while when starting VM for the first time

2. Login to VM using vagrant ssh command or your favorite ssh client. Login: vagrant, password vagrant

3. Switch to /vagrant directory cd /vagrant

4. Start django server python manage.py runserver 0.0.0.0:8000 Note you have to use 0.0.0.0 as server address, otherwise port forwarding may not work

You can edit files in your project directory, and changes will be visible to the virtual machine (in /vagrant directory)

Credentials

SSH Login: vagrant, password vagrant

PostgreSQL Database: om, Login: om, Password: om

Note: To utilize the PostgreSQL database, create a settings_local.py file containing the following:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql_psycopg2',
        'NAME': 'om',
        'USER': 'om',
        'PASSWORD': 'om',
        'HOST': '127.0.0.1',
        'PORT': '5432',
    }
}

0. By default, website.settings.dev is used for manage.py and website.settings.production is used in wsgi.py It is typically required to change default settings file used in manage.py in production and qa environments

1. Export DJANGO_SETTINGS_MODULE variable

This method works well on the command line, but it doesn't seem to work with apache - SetEnv doesn't seem to have any effect when mod_wsgi is initalizing wsgi application object.

2. Create config_local.py in the root folder (next to wsgi.py and manage.py)

Note if DJANGO_SETTINGS_MODULE is defined, it takes precedence over settings_module in config_local.py

Example:

settings_module = "website.settings.qa"

Check wsgi.py and manage.py to see how it works - they are different from default versions generated by Django.

1. Change database to PostgreSQL in settings_local.py

2. Set DEBUG to False in settings_local.py

3. Generate new SECRET_KEY

4. Change ALLOWED_HOSTS and ADMINS accordingly

5. Set APP_ENV to 'production'

6. Setup cron jobs: python manage.py crontab add

1. Install django-auth-pubtkt package pip install django-auth-pubtkt

2. Copy public key for validating pubtkt tickets to /etc/httpd/conf/sso/tkt_pubkey_dsa.pem