Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System Architecture #1

Open
Strum355 opened this issue Dec 23, 2018 · 3 comments
Open

System Architecture #1

Strum355 opened this issue Dec 23, 2018 · 3 comments

Comments

@Strum355
Copy link
Member

Strum355 commented Dec 23, 2018

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

@Strum355 Strum355 added the help wanted Extra attention is needed label Dec 23, 2018
@ocanty
Copy link
Member

ocanty commented Dec 23, 2018

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
Copy link
Member Author

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 Strum355 removed the help wanted Extra attention is needed label Jul 8, 2019
@Strum355
Copy link
Member Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants