mtcontrib/mtsatellite
1
0
Fork 0
mirror of https://bitbucket.org/s_l_teichmann/mtsatellite synced 2025-01-23 06:40:20 +01:00
Code Issues Projects Releases Wiki Activity

SETUP: Wrote final paragraph about configuring the Minetest server.

Browse Source
This commit is contained in:
Sascha L. Teichmann 2014-10-05 15:08:25 +02:00
parent bf07b042e9
commit 6d263533c2
1 changed files with 16 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
SETUP.md
View File

@ -1,4 +1,4 @@
# SETUP MTSatellite \[WIP\]
# SETUP MTSatellite
You will need a Minetest server with Redis support compiled in. Consult the Minetest documentation to figure out how to get such build.
Furthermore you need the binaries `mtdbconverter`, `mtseeder`, `mtredisalize` and `mtwebmapper` in your **PATH**.
@ -118,7 +118,20 @@ To see all the available options use `mtwebmapper --help`.
The `GOMAXPROCS=`/`-workers=` setting has to be adjusted to your system capacity. Do not
give to much ressources to this if you planning to run the mapping webserver on the
same machine as the Minetest server.
same machine as the Minetest server. On the other hand assigning more cores to it definitely
helps to boost up the performance.
## Configure and restart the Minetest server
**TODO: Write me!**
Now everything is in place and the only thing left ist to re-configure the Minetest server
itself. You have to open your `/path/to/your/world.mt` file in your text editor and replace the
backend with a Redis configuration:
backend = redis
redis_hash = IGNORED
redis_address = localhost
You may have to set `redis_port` too if you run `mtredisalize` not on port 6379.
Now we are all done and you can fire your Minetest server up again. :-)