Get rid of docker/backend and switch to pure frontend js only with graphql/web3 about escrow-dashboard HOT 5 CLOSED

For now let's just include instructions for how to npm out the js files for static file inclusion and call it a day.

from escrow-dashboard.

What is the reason of getting rid from docker here? It is already a pure frontend.js application which may be running without docker. The docker wrapper here is only for deployment purposes

from escrow-dashboard.

Let’s get rid of it in deployment, so the deployment doesn’t require docker at all. Just a tiny bit of js

from escrow-dashboard.

By getting rid of the docker we will just move the phase of starting the app in the prod to a different place: this includes webpack build, serving instructions + some tools for monitoring the state of the app(in this case it is a docker, but it might be the pm2 or any other tool which controls the state). We definitely don't want to use bare "yarn start" and control this manually on remote machines

Also, just for the notice - there is no backend(except the server which serves static files) in the dashboard

Regarding pure js. Considering all features that we are planning to add to the dashboard in the future, I won't advise moving it to the pure js, because the code will be messy and hard to read imho

cc @makarofalex3 @ivhus

from escrow-dashboard.

docker ≠ backend

getting rid of backend would be nice (but as @vkomodey said there is no backend particularly here)

Docker container is a portable thing which works same in ECS, EKS, OpenShift, locally, wherever in any other environment we may ever want

And with switchng to pure JS we are going to get dependent on the environment and it's confuguration consistency will become
yet another thing to maintain

from escrow-dashboard.