Skip to content

Conversation

@Janhouse
Copy link

@Janhouse Janhouse commented Jul 5, 2016

Fixes #103 by introducing new configuration variables.
I'm now using eBot behind NAT in lxc container.

@Janhouse
Copy link
Author

Janhouse commented Jul 5, 2016

I also managed to set up HTTP proxy with web socket proxying using Apache, so access to port 12360 can be limited only to CS:GO servers.

Here is the Apache config I use:

<VirtualHost *:80>
ServerName ebot.example.com
ServerAdmin admin@ebot.example.com
DocumentRoot /var/www

RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket
RewriteRule /socket.io/(.*)           ws://ebot.lxc:12360/socket.io/$1 [P,L]
RewriteCond %{HTTP:Upgrade} !=websocket
RewriteRule /socket.io/(.*)           http://ebot.lxc:12360/socket.io/$1 [P,L]

ProxyPass /socket.io http://ebot.lxc:12360/socket.io
ProxyPassReverse /socket.io http://ebot.lxc:12360/socket.io

ProxyPass / http://ebot.lxc/
ProxyPassReverse / http://ebot.lxc/

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Similar setup should also allow using eBot in Docker.

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

Successfully merging this pull request may close these issues.

1 participant