parse-hipaa-dashboard


!dashboard

Example of how to setup and run your own parse-dashboard for viewing/modifying your data in the Cloud. Designed for parse-hipaa, but can be used with any parse-server.

Use at your own risk. There is not promise that this is HIPAA compliant and we are not responsible for any mishandling of your data

Deployment

parse-hipaa can be easily deployed or tested remote or locally.

$3

#### Heroku

You can use the one-button deployment to quickly deploy to Heroko. Note that this is non-HIPAA compliant when using Heroku's free services, so you need to work with Heroku to enable this. You can view this document for detailed instructions. Once you click the Heroku button do the following:

1. Select your App name
2. Under the Config vars section, set all required environment vars to connect to your parse-server
3. Scroll to the bottom of the page and press Deploy app

#### Using your own files for Heroku deployment
1. Fork the parse-hipaa-dashboard repo
2. Edit heroku.yml in your repo by changing Dockerfile.heroku to Dockerfile. This will build from your respective repo instead of using the pre-built docker image
3. Edit parse-dashboard-config.json to your desired configuration
4. You can then click the Heroku deployment button from your respective repo or you can then follow the directions on heroku's site for deployment and integration
5. Set the PARSE_DASHBOARD_CONFIG config variable to ./src/parse-dashboard-config.json

$3

To get started with parse-hipaa simply type:

``docker-compose up`

$3

#### parseplatform/parse-dashboard
`bash
PARSE_DASHBOARD_TRUST_PROXY: # Default is 1, this should always be left as 1 when using docker
PARSE_DASHBOARD_COOKIE_SESSION_SECRET: # Unique string. This should be constant across all deployments on your system
MOUNT_PATH: # The default is "/dashboard". This needs to be exactly what you plan it to be behind the proxy, i.e. If you want to access usc.edu/dashboard it should be "/dashboard"
`

$3

Parse-dashboard is binded to your localhost on port 4040 and can be accessed as such, e.g. http://localhost:4040/dashboard. The default login for the parse dashboard is username: "parse", password: "1234". For production you should change the password in the postgres-dashboard-config.json. Note that ideally the password should be hashed by using something like bcrypt-generator or using multi factor authentication. You can also add more users through this method.

1. Open your browser and go to http://localhost:4040/dashboard
2. Username: parse # You can use parseRead to login as a read only user
3. Password: 1234
4. Be sure to refresh your browser to see new changes synched from your CareKitSample app

$3


As mentioned, the default address and port the parse-server dashboard is binded to is 127.0.0.1:4040:4040 which means it can only be accessed by your local machine. If you want to change this, you should do it here. If you plan on using this image to deploy in production, it is recommended to run this behind a proxy and add the environment variable PARSE_DASHBOARD_TRUST_PROXY=1 to the dashboard container. Note that since the parse dashboard is running in docker, the following should remain in the yml, command: parse-dashboard --dev`.