single entrypoint docker-compose

[gnunicorn]

• a slim Dockerfile to put the entire build (binary & JS build) into
• a docker-compose.yml, that uses the docker-image and provides a single http-endpoint (potentially with an nginx in front) to
  1. host and serve the static-html
  2. allow access to the JSON-RPC
  3. pass-through to the websocket

[uLan08]

Hi, I'd like to work on this.

[gnunicorn]

go for it @uLan08 !

I was also thinking that it'd be good to have ipfs combined, too... at least in the docker-compose also immediately set up n ipfs

[uLan08]

alright, I'll see what I can do.

[gnunicorn]

here is what I currently use at gather.wtf:

Dockerfile:

FROM ubuntu:18.04

MAINTAINER "ben@gnunicorn.org"
RUN apt update && apt install -y libssl-dev curl && apt clean
RUN mkdir /gather
WORKDIR /gather
COPY target/release/gather gather
RUN  chmod 770 gather
EXPOSE 9933 9944 30333
VOLUME /gather/local
CMD ./gather --chain=demo -d /gather/local --rpc-external --ws-external --rpc-cors all --validator --name "node-gather-wtf"

[uLan08]

Will this be for local dev use?

[gnunicorn]

I don't think a docker-image for local usage makes a lot of sense for a rust build ... I mean, we could provide a pre-image, but the built is pretty straight forward.

No, I was thinking of using docker and docker-compose for deploying a node and its interface.

[uLan08]

That makes sense. But I am thinking of creating two Dockerfiles, one for the binary build and one for the JS frontend build. Having both of them into one image would mean that two process would need to be run in the container (the binary and nginx for serving content) and that would go against Docker's principles.