search

UCCNetsoc / Windlass

Self-hosted multi-tenant and multi-host Containers as a Service platform using LXD or Firecracker
16 stars 3 forks source link

System Architecture #1

Open Strum355 opened 5 years ago

Strum355 commented 5 years ago

Decide on database, any modularization of the main process that may be required etc

Do we separate the backend and have the frontend interact via an API? Probably best idea

ocanty commented 5 years ago

If we are going to be using nginx for our reverse proxying, instead of writing our own scripts, we can automate it using this:

https://github.com/jwilder/nginx-proxy

Strum355 commented 5 years ago

Ooo this could be very good. Depending on where we deploy this, we might have to reverse proxy from apache to this container. ill also look into how configurable this is for our purposes etc

Strum355 commented 5 years ago

architecture diagrams are in the doc folder and will need to be continuously updated so this is a constant WIP. Using traefik as the reverse proxy as has an API that the workers can use to update routing rules