Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Commit

Permalink
Update DEPLOYMENT_GUIDE.md
Browse files Browse the repository at this point in the history
Remove "none" from documentation for clarity but leave it as an option for convenience (testing, etc.)
  • Loading branch information
MatthewDorner authored Aug 18, 2018
1 parent eb30068 commit 9e2855a
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions DEPLOYMENT_GUIDE.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,8 +63,6 @@ Follow these five easy steps to get HospitalRun up and running
To use automatic SSL cert generation, edit the `DOMAIN_NAME` argument and replace `www.example.com` as shown in the image below with the publicly accessible domain name that HospitalRun will run on.

To instead use your own SSL cert, change the `SSL_TYPE` argument to `self` and place your certificate files at `data/nginx/cert/ssl.crt` and `data/nginx/cert/ssl.key`. You will need to create a `data/nginx/cert` path from the root folder if you haven't run the server yet.

To use no SSL cert, change the `SSL_TYPE` argument to `none`, but your server will only be accessible locally.

4. Save the file and run `docker-compose up --build -d`. You should wait for some ten minutes or less for your environment to be up and running. Deployment speed will vary based on your internet connection speed and the quality of your infrastructure

Expand Down

0 comments on commit 9e2855a

Please sign in to comment.