Updated Configuring Multiple Servers (markdown)
parent
da34bb2a61
commit
ebb633b5f6
@ -52,7 +52,7 @@ This subdirectory-based approach was chosen for its relative simplicity and beca
|
|||||||
|
|
||||||
Multiple server support is configured in index.html. Look for the `<script>` containing the `window.liveAtlasConfig` object and edit the `servers` property to include the servers you want to be accessible within LiveAtlas. The key of each server object will be used in the URL to access it.
|
Multiple server support is configured in index.html. Look for the `<script>` containing the `window.liveAtlasConfig` object and edit the `servers` property to include the servers you want to be accessible within LiveAtlas. The key of each server object will be used in the URL to access it.
|
||||||
|
|
||||||
Each server object should contain a `dynmap` or `pl3xmap` property which contains the URLs necessary for displaying the map. Dynmap maps require several URLs which can typically be found in the `standalone/config.js` file for the server. Pl3xmap maps require just the URL the map is currently viewable at. Making all URLs absolute is recommended to avoid ambiguity.
|
Each server object should contain a `dynmap` or `pl3xmap` property which contains the URLs necessary for displaying the map. Dynmap maps require several URLs which can be found in the `standalone/config.js` file for the server. Pl3xmap maps require just the URL the map is currently viewable at. Making all URLs absolute is recommended to avoid ambiguity.
|
||||||
|
|
||||||
An example with 2 dynmap servers named `creative` and `survival` and a 3rd Pl3xmap server:
|
An example with 2 dynmap servers named `creative` and `survival` and a 3rd Pl3xmap server:
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user