HospitalRun – Docker Containerized
Hi Guys,
i just ran the containerized version of the HospitalRun Application on my digitalocean droplet using my own self signed certificate.
Please Watch my Youtube Video:-
apt-get install \
apt-transport-https \
ca-certificates \
curl \
gnupg-agent \
software-properties-commoncurl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add –
apt-key fingerprint 0EBFCD88
add-apt-repository \
“deb [arch=amd64] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) \
stable”apt-get update
apt-get install docker-ce docker-ce-cli containerd.io
apt-get install docker-compose
git clone https://github.com/HospitalRun/hospitalrun-server.git
openssl req -new -newkey rsa:2048 -nodes -keyout ssl.key -out ssl.csr
openssl x509 -req -in ssl.csr -signkey ssl.key -out ssl.crt
Hari's Technical Space 
Hi Hari
I am trying to install hospitalrun in my Azure VM and hit a snag when i get the npm install, it seems the npm repository for hospitalrun 1.0.0 beta no longer exists? I tried to reach out via the project’s github page as well as their spectrum, no luck yet. Any ideas?
…
sudo docker-compose up –build -d
Building logstash
Step 1/6 : FROM docker.elastic.co/logstash/logstash:5.3.1
—> b10356faedc8
Step 2/6 : LABEL maintainer Mofesola BABALOLA
—> Using cache
—> 05bc3a09ee36
Step 3/6 : RUN logstash-plugin update –no-verify logstash-input-couchdb_changes
—> Using cache
—> 35fc05a8e5f6
Step 4/6 : RUN rm -f /usr/share/logstash/pipeline/logstash.conf
—> Using cache
—> 1f4b100fb0e0
Step 5/6 : ADD pipeline/ /usr/share/logstash/pipeline/
—> Using cache
—> 1b4f344cca4b
Step 6/6 : ADD config/ /usr/share/logstash/config/
—> Using cache
—> 1222bcab13c7
Successfully built 1222bcab13c7
Successfully tagged hospitalrun_logstash:latest
Building hospitalrun
Step 1/14 : FROM node:10-slim
—> 9bfd5b64f034
Step 2/14 : LABEL maintainer Mofesola Babalola
—> Using cache
—> f34dc8f64c56
Step 3/14 : ENV DEBIAN_FRONTEND noninteractive
—> Using cache
—> 927e4a753c1f
Step 4/14 : RUN apt-get update && apt-get install -y git
—> Using cache
—> a11f28c72f99
Step 5/14 : WORKDIR /usr/src/app
—> Using cache
—> 4f2753cba1a1
Step 6/14 : COPY package.json /usr/src/app
—> Using cache
—> 92f6053a476c
Step 7/14 : COPY package-lock.json /usr/src/app
—> Using cache
—> e682e82e5895
Step 8/14 : RUN npm install
—> Running in 6fbed0bf24a6
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/yargs-parser-0197c404/CHANGELOG.md’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/hospitalrun-dblisteners-24ce0aa6/README.md’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/nconf-3a1bbd67/LICENSE’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/hospitalrun-dblisteners-24ce0aa6/yarn.lock’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/csv-parse-40c3e5df/lib/sync.js’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/nconf-3a1bbd67/README.md’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/raml-typesystem-9e6a18c2/dist/src/exampleBuilder.js.map’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/snyk-policy-2774e7b7/.nyc_output/4157.json’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/moment-593114f6/package.js’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/prompt-63f584e7/.travis.yml’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/z-schema-707191d1/dist/ZSchema-browser-min.js.map’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/acorn-874f442d/dist/acorn.js’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/raml-json-validation-9735393a/browser_version/package.json’
npm WARN tar ENOENT: no such file or directory, open ‘/usr/src/app/node_modules/.staging/relational-pouch-a9e02bc8/dist/pouchdb.relational-pouch.min.js’
npm ERR! code E404
npm ERR! 404 Not Found – GET https://registry.npmjs.org/hospitalrun/-/hospitalrun-1.0.0-beta.tgz
npm ERR! 404
npm ERR! 404 ‘hospitalrun@1.0.0-beta’ is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of ‘app’
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-09-10T15_12_56_544Z-debug.log
ERROR: Service ‘hospitalrun’ failed to build: The command ‘/bin/sh -c npm install’ returned a non-zero code: 1
…
LikeLike