|
|
# Preparation
|
|
|
|
|
|
* Ubuntu packages `openssl`, `libssl-dev`, `make` and `gcc` are required as dependencies
|
|
|
* copy `RMBTServer/*` to installation directory
|
|
|
* run `make server-prod random`
|
|
|
* make sure clock is in sync with control server
|
|
|
* prepare SSL cert somewhere on the server
|
|
|
* edit secret key in `secrets.h`
|
|
|
* it can be unique for only this server, however control server must have it in its database in `test_server` table
|
|
|
|
|
|
|
|
|
# Run
|
|
|
|
|
|
* run binary `rmbtd` with desired `-c path/to/cert.pem -k path/to/privkey`
|
|
|
* `--help` will print all options
|
|
|
* `-L` and `-l` configures ports
|
|
|
* `-w` determines, whether the server uses websocket or plain TCP
|
|
|
* it's recommended to have two instances running with and without `-w`
|
|
|
|
|
|
# Enable it in control server
|
|
|
|
|
|
* create a new record in `test_server` table in control server database
|
|
|
* every column should be filled in
|
|
|
* `active` column determines, whether the server is announced by the control server
|
|
|
* `type` should be `RMBT` or `RMBTws` depending on whether you used `-w` flag
|
|
|
* A row in the table refers to one instance of the server. If you deployed multiple instances, each one of them should have it's own row. |
|
|
\ No newline at end of file |