ekivemark

Publish FHIR IG Publisher zip file to build.fhir.org

This process outlines the steps to publish a FHIR publisher zip file output generated by Lantana's Trifolia service and move it to the HL7 FHIR CCI build server via a github repository.

Compile the following information:

• location of IG on build.fhir.org. e.g. for PDEx it is: http://build.fhir.org/ig/HL7/davinci-epdx/
• location of IG on HL7 Github. e.g. foor PDEx it is: https://github.com/HL7/davinci-epdx

Pre-requisite software to be installed

ekivemark

The django settings file currently have a hard coded SECRET_KEY. We need to keep the production key secret.

The following change is proposed:

Current setting: ################################################

SECURITY WARNING: keep the secret key used in production secret!

SECRET_KEY = 'some_random_really_long_string'

ekivemark

Server Credential Map

Author: mark Created: 2019-09-25.12:43

Repository: https://github.com/TransparentHealth/cdex-deploy

Introduction

The Share My Health Platform consists of four connected systems.

ekivemark

I recommend modfying wsgi.py for VMI/SMH/SMH_APP to enable some flexibility in the call to the EC2 parameter store. 

THe current code is:

###########################################
import os
from .ssmenv import EC2ParameterStore

from django.core.wsgi import get_wsgi_application

ekivemark

### Keybase proof

I hereby claim:

  * I am ekivemark on github.
  * I am ekivemark (https://keybase.io/ekivemark) on keybase.
  * I have a public key ASD5ROsEB99aGh0jJ5Kr68Y7ea1keciYvJCaLpfEbV2fqAo

To claim this, I am signing this object:

ekivemark

# docker build -t ubuntu1604py36
FROM ubuntu:16.04

RUN apt-get update
RUN apt-get install -y software-properties-common vim
RUN add-apt-repository ppa:jonathonf/python-3.6
RUN apt-get update

RUN apt-get install -y build-essential python3.6 python3.6-dev python3-pip python3.6-venv
RUN apt-get install -y git

ekivemark

# Set Configuration Variables outside of the Repo

Passwords and confguration data should not be stored in a public (or private repo). 
We therefore need a robust but predictable mechanism to allow machine/environment specific configuration settings to be defined.
The settings need to be loaded by the server that runs the application. In a production environment this is usually done in the wsgi file.

## Designed for Virtual Environments and Git

A common design pattern with python and git is to create a virtual environment. This usually includes creating a folder from which
a git clone is run to import code.