mtcontrib/mtsatellite
1
0
Fork 0
mirror of https://bitbucket.org/s_l_teichmann/mtsatellite synced 2024-12-24 01:00:18 +01:00
Code Issues Projects Releases Wiki Activity

Improved SETUP.md wording a bit.

Browse Source
This commit is contained in:
Sascha L. Teichmann 2015-03-04 12:53:07 +01:00
parent f2b139eabb
commit 02c3916bc8
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
SETUP.md
View File

@ -126,7 +126,7 @@ give to much ressources to this if you planning to run the mapping webserver on
same machine as the Minetest server. On the other hand assigning more cores to it definitely same machine as the Minetest server. On the other hand assigning more cores to it definitely
helps to boost up the performance. helps to boost up the performance.
Setting the`-websockets=true` flag enables websocket support for the server. With this Setting the `-websockets=true` flag enables websocket support for the server. With this
feature turned on and changing the line (in `web/index.html`) from feature turned on and changing the line (in `web/index.html`) from
var useWebsocket = false; // Set to true if you want websocket support var useWebsocket = false; // Set to true if you want websocket support
@ -135,9 +135,10 @@ to
var useWebsocket = true; // Set to true if you want websocket support var useWebsocket = true; // Set to true if you want websocket support
the web client gets an extra 'auto update' mode. When switched on the server the web client gets an extra 'auto update' button. When switched on the server
informs the client if something in the maps has changed. The displayed map will informs the client if something in the maps has changed. The displayed map will
then update automatically. Of cause your browser needs Websocket support, too. then update automatically without the need of manual pressing the 'update view'
button. Of cause your browser needs Websocket support, too.
## Configure and restart the Minetest server ## Configure and restart the Minetest server
@ -152,4 +153,3 @@ backend with a Redis configuration:
You may have to set `redis_port` too if you run `mtredisalize` not on port 6379. 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. :-) Now we are all done and you can fire your Minetest server up again. :-)