split frontend and backend images

Author: felixgabler

README.md

@@ -1,49 +1,2 @@
 # Toolkit-Docker
-Dockerfiles for the toolkit's docker image. It should be built automatically by DockerCloud.
-
-To build it manually, run:
-``docker image build -t "proteinevolution/toolkit-docker:1.1.6" -t "proteinevolution/toolkit-docker:latest" .``
-
-To push the image, run:
-``docker push proteinevolution/toolkit-docker:latest``
-
-## Using image with docker file
-
-The most minimal `docker-compose.yml` file is:
-
-```
-version: '3.7'
-services:
-  sbt:
-    image: proteinevolution/toolkit-docker:latest
-    volumes:
-      - .:/toolkit
-```
-
-But it's not optimal if you have anything cached in `~/ivy2` which most probably you do if you develop Scala. To benefit from caching; thus reducing startup time, use the following:
-
-```
-version: '3.7'
-services:
-  sbt:
-    image: proteinevolution/toolkit-docker:latest
-    volumes:
-      - .:/toolkit
-      - ~/.ivy2:/root/.ivy2
-      - ~/.sbt:/root/.sbt
-      - ~/.coursier:/root/.coursier
-```
-
-It's still the minimal version; in real project you will probably need to expose ports etc.
-
-## Overriding CMD
-
-By default (i.e. if you don't provide CMD in your `docker run` or `docker-compose.yml`) it will run sbt's `shell`. It's a reasonable default because from there you can invoke any SBT task you want.
-
-If default does not fit your needs then override CMD in either `docker run` or `docker-compose.yml`. Example:
-
-```
-docker run -v :.:/toolkit proteinevolution/toolkit-docker:latest projects test:compile
-```
-
-Here we also used ability to "chain" sbt commands.
+Dockerfiles for the toolkit's docker images. They should be built automatically by DockerCloud.

Dockerfile backend/DockerfileDockerfile renamed to backend/Dockerfile

@@ -2,57 +2,9 @@ FROM hseeberger/scala-sbt:8u212_2.12.8_1.2.8
 
 LABEL maintainer="fgabler@tue.mpg.de"
 
-# since scala-sbt is based on stretch-scm instead of stretch, install missing packages. see: https://github.com/docker-library/buildpack-deps/blob/d7da72aaf3bb93fecf5fcb7c6ff154cb0c55d1d1/stretch/Dockerfile
-RUN apt-get update && apt-get install -y --no-install-recommends \
-		autoconf \
-		automake \
-		bzip2 \
-		file \
-		g++ \
-		gcc \
-		imagemagick \
-		libbz2-dev \
-		libc6-dev \
-		libcurl4-openssl-dev \
-		libevent-dev \
-		libffi-dev \
-		libgeoip-dev \
-		libglib2.0-dev \
-		libjpeg-dev \
-		liblzma-dev \
-		libmagickcore-dev \
-		libmagickwand-dev \
-		libncurses-dev \
-		libpng-dev \
-		libpq-dev \
-		libreadline-dev \
-		libsqlite3-dev \
-		libssl-dev \
-		libtool \
-		libwebp-dev \
-		libxml2-dev \
-		libxslt-dev \
-		libyaml-dev \
-		make \
-		patch \
-		xz-utils \
-		zlib1g-dev \
-	&& rm -rf /var/lib/apt/lists/*
-
-# install node and yarn
-RUN curl -sL https://deb.nodesource.com/setup_10.x | bash -
-RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
-RUN echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list
-RUN apt-get update -qqy && apt-get -qqyy install \
-    nodejs \
-    yarn \
-  && rm -rf /var/lib/apt/lists/*
-
 ENV TK_BASE_PATH "/root/Toolkit"
 ENV MAXMIND_DB "$TK_BASE_PATH/data/GeoLite2-City.mmdb"
 
-ENV CHOKIDAR_USEPOLLING=true
-
 RUN mkdir -p $TK_BASE_PATH/bioprogs/tools
 RUN mkdir -p $TK_BASE_PATH/databases
 RUN mkdir -p $TK_BASE_PATH/data
@@ -100,13 +52,11 @@ WORKDIR /toolkit
 
 RUN sbt update
 
-# expose frontend port
-EXPOSE 8080
 # expose backend port
 EXPOSE 1234
 
 RUN mv ~/.ivy2 ~/.ivy_image
-COPY ./docker-entrypoint.sh /
+COPY ../docker-entrypoint.sh /
 ENTRYPOINT ["/docker-entrypoint.sh"]
 
 CMD ["shell"]

backend/README.md

@@ -0,0 +1,49 @@
+# Toolkit Backend Docker Image
+Dockerfile for the toolkit's backend docker image. It should be built automatically by DockerCloud.
+
+To build it manually, run:
+``docker image build -t "proteinevolution/toolkit-docker:1.1.6" -t "proteinevolution/toolkit-docker:latest" .``
+
+To push the image, run:
+``docker push proteinevolution/toolkit-docker:latest``
+
+## Using image with docker file
+
+The most minimal `docker-compose.yml` file is:
+
+```
+version: '3.7'
+services:
+  sbt:
+    image: proteinevolution/toolkit-docker:latest
+    volumes:
+      - .:/toolkit
+```
+
+But it's not optimal if you have anything cached in `~/ivy2` which most probably you do if you develop Scala. To benefit from caching; thus reducing startup time, use the following:
+
+```
+version: '3.7'
+services:
+  sbt:
+    image: proteinevolution/toolkit-docker:latest
+    volumes:
+      - .:/toolkit
+      - ~/.ivy2:/root/.ivy2
+      - ~/.sbt:/root/.sbt
+      - ~/.coursier:/root/.coursier
+```
+
+It's still the minimal version; in real project you will probably need to expose ports etc.
+
+## Overriding CMD
+
+By default (i.e. if you don't provide CMD in your `docker run` or `docker-compose.yml`) it will run sbt's `shell`. It's a reasonable default because from there you can invoke any SBT task you want.
+
+If default does not fit your needs then override CMD in either `docker run` or `docker-compose.yml`. Example:
+
+```
+docker run -v :.:/toolkit proteinevolution/toolkit-docker:latest projects test:compile
+```
+
+Here we also used ability to "chain" sbt commands.

docker-entrypoint.sh backend/docker-entrypoint.shdocker-entrypoint.sh renamed to backend/docker-entrypoint.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 
-# The only point of that entrypoint file is to merge `ivy2_image/local` (where sbt libraries built in Dockerfile reside)
+# The only point of that entrypoint file is to merge `ivy2_image/local` (where sbt libraries built in Dockerfile.backend reside)
 # into `/root/.ivy2/local`. `.ivy2/local` is where image user could mount his host ivy cache
 # IMPORTANT: always use LF line endings for this file
 

frontend/Dockerfile

@@ -0,0 +1,17 @@
+FROM node:10.16
+
+LABEL maintainer="fgabler@tue.mpg.de"
+
+RUN yarn global add yarn@1.16.0
+RUN yarn global add @vue/cli npm-check-updates
+
+ENV CHOKIDAR_USEPOLLING=true
+
+VOLUME /toolkit/frontend
+WORKDIR /toolkit/frontend
+
+# expose frontend port
+ENV PORT=8080
+EXPOSE 8080
+
+CMD yarn install

frontend/README.md

@@ -0,0 +1,13 @@
+# Toolkit Frontend Docker Image
+Dockerfile for the toolkit's frontend docker image. It should be built automatically by DockerCloud.
+
+To build it manually, run:
+``docker image build -t "proteinevolution/toolkit-docker-frontend:1.0.0" -t "proteinevolution/toolkit-docker-frontend:latest" .``
+
+To push the image, run:
+``docker push proteinevolution/toolkit-docker-frontend:latest``
+
+## Various commands
+To access the shell, run:
+``docker run --name tk-frontend -p 8080:8080/tcp -v "$PWD:/toolkit" --rm -it proteinevolution/toolkit-docker-frontend bash``
+