Skip to content
This repository was archived by the owner on Sep 11, 2019. It is now read-only.

all HTTP(S) traffic needs to be converted on NGINX level !!! from enduser perspective #772

Open
despiegk opened this issue Aug 14, 2019 · 3 comments

Comments

@despiegk
Copy link

despiegk commented Aug 14, 2019

dont do http(s) traffic for customers directly on threebot server

the nginx is the layer in between

  • does https to http
  • does letsencrypt
  • does $somethong/$aname to localhost:$aport

we need to make sure all following over nginx

  • websockets work that way (can be websockets in gevent loop but the nginx as proxy)
  • chat bot
  • wiki (proxied)

this means gevent loop in threebot server only needs to do

  • http
  • on port level (no named hosts, all can be separate gevent servers with different ports)
@despiegk despiegk added this to the now milestone Aug 14, 2019
@despiegk despiegk changed the title all HTTPS traffic needs to be converted on NGINX level !!! all HTTP(S) traffic needs to be converted on NGINX level !!! from enduser perspective Aug 14, 2019
@despiegk
Copy link
Author

check all existing usecases that it works like this

@despiegk
Copy link
Author

remove ssl from gevent loop
ssl maybe on gedis server (to be discussed) because that one is no HTTP

@Hamdy Hamdy self-assigned this Aug 14, 2019
@Hamdy
Copy link
Contributor

Hamdy commented Aug 22, 2019

added support for tcp, websocket reverse proxies
now nginx can serve (http, tcp, websocket) protocols
added reverse proxies in threebot for the different kinds of servers we are having

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

No branches or pull requests

3 participants