This script helps you get eBot up and running using php7. The frontend still runs php5 (as of the date this was written) on a standard apache2 installation. Only tested on on a Xen virtualized machine running Debian Jessie, but it should work on any Debian based system with apt-get.
Run these targets in order:
- php7-zts
- ebotv3
- ebotv3-config password=PASSWORD mysql=MYSQLROOTPASSWORD
- (Optional) ebotv3-ip ip=IP
- (Optional) apache-alias
- run
This install a lot of dependencies, including mysql-server. As such apt-get might ask you to enter a root password for your new MySQL installation. It then downloads php-src and verifies that it is version 7 before making it and installing it into /usr/local/php7-zts. In order to make eBot run on php7 pthreads (and some more) modules are included which doesn't make it very suitable for regular usage. The php binary is symlinked to /usr/local/bin/php7-zts so it shouldn't mess up any already installed versions of php.
Some more dependencies are installed and then eBot-CSGO and eBot-CSGO-Web are downloaded and built. This creates the user 'ebotv3'. eBot is broken as fuck so some patches are included (and auto-installed) to fix that.
Takes two arguments: 'password' and 'mysql'.
'password' will be the password used by eBot to login to MySQL and also the password that you will use to login to the admin panel.
'mysql' must be the root password you entered when setting up mysql-server.
You can (probably) ignore these errors that might occur:
- SQLSTATE[HY000]: General error: 1005 Can't create table 'ebotv3.#sql-3728_93' (errno: 121)
- SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'admin@ebotv3' for key 'email_address'
Takes one argument: 'ip'.
This changes two things:
- The IP in eBot-CSGO/config/config.ini, which is the IP eBot will send to your CSGO server so that the server can talk back to eBot.
- The IP in eBot-CSGO-Web/config/app_user.yml, which is the IP your browser will use to connect to eBot when in the admin panel.
In most cases these will be the same but if you say want to have the admin panel accessible from the internet then you should edit app_user.yml yourself and point it to your exernal IP. In that case also forward port 12360, since that is the port eBot listens to by default.
Hostnames (such as localhost) or loopback addresses (such as 127.0.0.1) doesn't always work so use the machines internal IP for best results.
Adds an apache2 VirtualHost so that the eBot frontend is accessible from a browser. The target is named apache-alias because of reasons.
Runs eBot as the user 'ebotv3'