Containerize Frontend & Backend

[aashkir]

What is this PR about?

This change builds a multi-stage docker image for eelbot-ui, the output images are frontendand backend. The multi-stage build has 4 phases:

• staging (frontend): Start with a Node.js base image, and copies relevant source files.
• staging (backend): Start with a Python base image, Installs poetry, and copies relevant source files.
• development (frontend): Installs the frontend project in editable mode.
• development (backend): Installs the backend project in editable mode.
• build (frontend): Build the frontend project into a index.html file
• build (backend): Build the backend project into a wheel file
• production (frontend): A clean python-alpine image that installs the build wheel file & serves it
• production (backend): A clean nginx image that serves the index.html file & proxies requests to the backend server.

You can create development or production images by using the --target keyword during builds.

Additional changes:

• Consolidated readme files to root directory
• Added config file for backend, called configmodule.py resolves issue Add config support #7
• (backend) Installed psycopg2 (hot fix, since it wasn't present in last change)
• (frontend) Installed https-proxy-middleware and created setupProxy file so dev builds can specify which host & port to use via env variable, frontend:PORT/api/X now proxies to backend:PORT/X (for dev only)

link to my config set up

[right-mouse]

You'd be better of splitting this into two dockerfiles and putting them into their respective directories (frontend and backend)

[right-mouse]

Is this line needed? I always assumed .dockerignore would be automatically ignored, but correct me if I'm wrong.

[right-mouse]

Another good candidate to ignore is the .git/ folder, as well as the .gitignore file.