We currently have two separate repositories: one for the web app code (SPA frontend + FastAPI backend) and another for Docker Compose configurations. This setup complicates the process for users, requiring them to manage both repos to run the application.
I propose merging the Docker Compose configurations into the main repo to simplify setup. This would allow users to clone a single repository and run the Compose YAML file to get everything up and running quickly, improving reproducibility and reducing friction.
Specifically, we could:
Create a new bbc_portal folder
Move bbc_frontend and bbc_backend into bbc_portal
Move the Docker Compose YAML file into bbc_portal
Add a README in bbc_portal with updated instructions for running the app
What do you think of this approach?
PS: The YAML would spin up the proxy, frontend server, backend server, and PostgreSQL in one go.
PS2: At least until all Docker images are available on a hub, so that a single YAML file will be sufficient to spin up the entire application.
We currently have two separate repositories: one for the web app code (SPA frontend + FastAPI backend) and another for Docker Compose configurations. This setup complicates the process for users, requiring them to manage both repos to run the application.
I propose merging the Docker Compose configurations into the main repo to simplify setup. This would allow users to clone a single repository and run the Compose YAML file to get everything up and running quickly, improving reproducibility and reducing friction.
Specifically, we could:
bbc_portalfolderbbc_frontendandbbc_backendintobbc_portalbbc_portalREADMEinbbc_portalwith updated instructions for running the appWhat do you think of this approach?
PS: The YAML would spin up the proxy, frontend server, backend server, and PostgreSQL in one go. PS2: At least until all Docker images are available on a hub, so that a single YAML file will be sufficient to spin up the entire application.