Updated Configuring Multiple Servers (markdown)
parent
4126719af2
commit
03acf7c2d7
@ -7,6 +7,9 @@ When multi-server support is enabled in LiveAtlas, the URL will be appended with
|
|||||||
|
|
||||||
This subdirectory-based approach was chosen for its relative simplicity and because it allows for any old URLs to be redirected without losing information. Adding the server name to the URL hash was another option, but as hashes are not sent to the server redirects would lose any locations present in the initial URL. Fully configurable URLs would also add additional challenges when working within the limitations of the same origin policy and ensuring the relative asset URLs in index.html resolved correctly.
|
This subdirectory-based approach was chosen for its relative simplicity and because it allows for any old URLs to be redirected without losing information. Adding the server name to the URL hash was another option, but as hashes are not sent to the server redirects would lose any locations present in the initial URL. Fully configurable URLs would also add additional challenges when working within the limitations of the same origin policy and ensuring the relative asset URLs in index.html resolved correctly.
|
||||||
|
|
||||||
|
## Limitations
|
||||||
|
- Login/register functionality is not currently supported for multiple servers. Support will be added once login/register is integrated into LiveAtlas itself.
|
||||||
|
|
||||||
## Requirements
|
## Requirements
|
||||||
- External webserver
|
- External webserver
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user