This is a Django project forked from the openshift/django-ex repository.

eDivorce was developed by the British Columbia Ministry of Justice to help self represented litigants fill out the paperwork for their divorce. It replaces existing fillable PDF forms with a friendly web interface.

The steps in this document assume that you have access to an OpenShift deployment that you can deploy applications on.

Prerequesites:

• Docker
• Python 3.5

To run this project in your development machine, follow these steps:

1. (optional) Create and activate a virtualenv (you may want to use virtualenvwrapper).

2. Clone this repo:

   git clone https://github.com/bcgov/eDivorce.git

3. Install dependencies:

   pip3.5 install -r requirements.txt (try pip if pip3.5 is not recognized)

4. Create an environment settings file by copying .env.example to .env (.env will be ignored by Git)

5. Create a development database:

   python3.5 ./manage.py migrate (try python if python3.5 is not recognized)

6. Load questions from fixtures:

   python3.5 ./manage.py loaddata edivorce/fixtures/Question.json

7. If everything is alright, you should be able to start the Django development server:

   python3.5 ./manage.py runserver 0.0.0.0:8000

8. Start the Weasyprint server server on port 5005

   1. Bind the IP address 10.200.10.1 to the lo0 interface on your Mac computer. Weasyprint has been configured to use this IP address to request CSS files from Django.

      sudo ifconfig lo0 alias 10.200.10.1/24
      

   2. Start docker

      docker run -d -p 5005:5001 aquavitae/weasyprint
      

9. Open your browser and go to http://127.0.0.1:8000, you will be greeted with the eDivorce homepage. In dev mode, you can log in with any username and the password 'divorce'.

SASS compilation is now handled by the internal django-sass-processor package. In local development, it compiles *.scss files it finds into the same directory when they're loaded in the browser (thereafter it recompiles on load when it detects changes by timestamp difference). The file is collected into the staticfiles directory during build, so doesn't add overhead in production.

See: openshift/README.md

For local development a SQLite database will be used. For OpenShift deployments data will be stored in a PostgreSQL database, with data files residing on a persistent volume.

Copyright 2017 Province of British Columbia

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.