From 1da0a51acedddb81f11e40690a744d759a5be311 Mon Sep 17 00:00:00 2001 From: James Lyne Date: Tue, 31 May 2022 12:13:18 +0100 Subject: [PATCH] Updated Configuring Multiple Servers (markdown) --- Configuring-Multiple-Servers.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/Configuring-Multiple-Servers.md b/Configuring-Multiple-Servers.md index aee1e38..40b07f9 100644 --- a/Configuring-Multiple-Servers.md +++ b/Configuring-Multiple-Servers.md @@ -34,7 +34,9 @@ This subdirectory-based approach was chosen for its relative simplicity and beca LiveAtlas needs to be accessible via the URLs of all servers you wish to use. For example if you want your server maps to be accessible via `https://example.com/map/` with servers named `creative` and `survival`, you will need to ensure LiveAtlas is accessible via `https://example.com/map/survival` and `https://example.com/map/creative`. - A simple way to do this is to host LiveAtlas at `https://example.com/map/` (note the trailing `/`) and configure your webserver to route requests for nonexistant files to LiveAtlas' index.html. The below example for nginx routes requests to non-existant files for `/map/` URLs to LiveAtlas: + A simple way to do this is to host LiveAtlas at `https://example.com/map/` (note the trailing `/`) and configure your webserver to route requests for nonexistant files to LiveAtlas' index.html. + + Here is a an nginx configuration example which routes requests to non-existant files for `/map/` URLs to LiveAtlas: location ~ ^/map/ { index index.html; @@ -49,6 +51,13 @@ This subdirectory-based approach was chosen for its relative simplicity and beca fastcgi_param SCRIPT_FILENAME $request_filename; } } + + An apache example, which should be in an .htaccess file within `/map`: + + RewriteEngine On + RewriteCond %{REQUEST_FILENAME} !-d + + FallbackResource /index.html 2. Configure LiveAtlas for multiple servers