The initial implementation of the docker image has only 1 image for both daemon and webinterface. The goal of this task is to create a second and third image who only implements 1 thing (Webinterface or daemon)
Design
We'll propably need 2 dockerfiles. The dockerfile for the webinterface has to build the javascript and css, while the daemon-docker will not require this.
Nontheless, it's probably better to work with a intermediate container as we don't want to have unnecessary assets in this container.
Ref: #1 (Create docker image)
"Do 1 thing and do it well"
## Why do we need this?
The initial implementation of the docker image has only 1 image for both daemon and webinterface. The goal of this task is to create a second and third image who only implements 1 thing (Webinterface or daemon)
## Design
We'll propably need 2 dockerfiles. The dockerfile for the webinterface has to build the javascript and css, while the daemon-docker will not require this.
Nontheless, it's probably better to work with a intermediate container as we don't want to have unnecessary assets in this container.
Ref: #1 (Create docker image)
"Do 1 thing and do it well"
Why do we need this?
The initial implementation of the docker image has only 1 image for both daemon and webinterface. The goal of this task is to create a second and third image who only implements 1 thing (Webinterface or daemon)
Design
We'll propably need 2 dockerfiles. The dockerfile for the webinterface has to build the javascript and css, while the daemon-docker will not require this.
Nontheless, it's probably better to work with a intermediate container as we don't want to have unnecessary assets in this container.