Merge pull request #273 from paritytech/eg-docker-build

fix unclear docker CI options

.github/workflows/backend.yml

@@ -22,14 +22,13 @@ jobs:
     - name: Build release and call executable
       working-directory: ./backend
       run: cargo run --release -- --help
-
     - name: Build and Push template image
-      working-directory: ./backend
       uses: docker/build-push-action@v1 # https://github.com/docker/build-push-action
       with:
         username: ${{ secrets.DOCKER_USERNAME }}
         password: ${{ secrets.DOCKER_PASSWORD }}
-        dockerfile: Dockerfile
+        path: ./backend/
+        dockerfile: ./backend/Dockerfile
         repository: parity/substrate-telemetry-backend
         push: ${{ startsWith(github.ref, 'refs/tags/') }}
         tags: latest

.github/workflows/frontend.yml

@@ -36,14 +36,13 @@ jobs:
     - name: Build
       working-directory: ./frontend
       run: yarn build
-
     - name: Build and Push template image
-      working-directory: ./frontend
       uses: docker/build-push-action@v1 # https://github.com/docker/build-push-action
       with:
         username: ${{ secrets.DOCKER_USERNAME }}
         password: ${{ secrets.DOCKER_PASSWORD }}
-        dockerfile: Dockerfile
+        path: ./frontend/
+        dockerfile: ./frontend/Dockerfile
         repository: parity/substrate-telemetry-frontend
         push: ${{ startsWith(github.ref, 'refs/tags/') }}
         tags: latest

README.md

@@ -54,6 +54,8 @@ polkadot --dev --telemetry-url ws://localhost:8000/submit
 
 ## Docker
 
+*Pre-built docker images are available at `parity/substrate-telemetry-frontend` and `parity/substrate-telemetry-backend`.*
+
 ### Run the backend and frontend
 
 Obviously, the frontend need to be aware of the backend. In a similar way, your node will need to connect to the backend.

frontend/Dockerfile

@@ -10,7 +10,6 @@ RUN yarn install && \
     yarn build && \
     yarn cache clean
 
-
 #### OUTPUT IMAGE ####
 FROM nginx:stable-alpine
 LABEL maintainer="Chevdor <chevdor@gmail.com>"