Alternate Production Deployment Setup

[frinzekt]

Basic Information

There are cases where we want to ship the control entirely to the client. This will mean that we want a setup where the frontend is not controlled in our end. While I don't recommend this approach because it's much more complex of a setup than just hosting the backend in a linux box, and chucking frontend in vercel.

What you'll need to do

You probably still need to do #8 , but this issue is specific to handling frontend.

When you've done #8, you'll need to add the following

1. A new build for github action on a frontend
2. The docker compose created in Production Deployment Setup #8 will need to add 2 new containers (frontend, nginx for redirector for container service)

Other Information

Alternate of #8