-
Notifications
You must be signed in to change notification settings - Fork 485
Configuration
Do not create issue reports over our project page if you can't get it working. Please only use issues page for actual bugs & feature requests.
If you can't get it working, try support methods here and remember that we also provide paid support & consulting services.
This guide will help you get through configuring CoiniumServ server and getting it working. If you have still not installed it on your system, start by reading our getting started guide. This guide assumes you already completed the steps related to getting the project & compiling.
Once you got the project compiled, you have to first arrange configuration files.
Let's assume that you have downloaded CoiniumServ to
/home/user/Desktop/CoiniumServYour config files will exist in one of the following locations based on the mode you compiled the project;
/home/user/Desktop/CoiniumServ/bin/Debug/config
/home/user/Desktop/CoiniumServ/bin/Release/configGlobal configuration file hosts common settings (stack, website and logging). First we have copy config-example.json as config.json
cd /home/bonesoul/Desktop/CoiniumServ/bin/Debug/config
cp config-example.json config.jsonThen we have to open config.json with your favorite text editor (gedit, vim, pico etc..) and change it according to our needs.
As configuration files host their own documentation for all sections & parameters, it's pretty self explanatory.
As CoiniumServ can host multiple pools together, you have to also create per-pool configuration files. You need to create per-pool configuration files in;
/home/user/Desktop/CoiniumServ/bin/Debug/config/poolsBy default, you'll see the following per-pool example files;
As CoiniumServ uses a very flexible configuration sub-system you have two different methods to configure pools.
You can use advanced-example.json as a starting point and configure every specific bits;
cd /home/bonesoul/Desktop/CoiniumServ/bin/Debug/config
cp advanced-example.json your-pool.jsonadvanced-example.json hosts every available configuration option and you can fine them based on your needs. Yet again per-pool configuration files also host their own documentation for all sections & parameters and it's pretty self explanatory.
While loading per-pool configuration files, CoiniumServ will merge them with the default.json if it does exist, basically allowing you to put your common settings and then only change the required parameters in your per-pool configuration files.
cd /home/bonesoul/Desktop/CoiniumServ/bin/Debug/config
cp default-example.json default.json

