Accessing Multiple Installs on same server: Difference between revisions

From nuBuilderForte
Jump to navigation Jump to search
No edit summary
No edit summary
Line 4: Line 4:


#Different subdomains for each instance is the best practice.
#Different subdomains for each instance is the best practice.
#[https://github.com/apmuthu/nubuilder4/commit/55cac0b9beca50e225df02047b07110c00202ceb The recent v4 code commit] allows one install at a time from being accessed even without logging out from another install in a single window's single tab.
#[https://github.com/apmuthu/nubuilder4/commit/55cac0b9beca50e225df02047b07110c00202ceb The recent v4 code commit] (and [https://github.com/nuBuilder/nuBuilder-4.5/commit/f5f76ec8eda7764ed6e5b5e25949dd4b6839f9fd v4.5]) allows one install at a time from being accessed even without logging out from another install in a single window's single tab.
#If different instances are used in different browser windows / tabs, session hijacking by last login will occur and hence it is advised to refrain from doing so and will require closure of all browser instances (windows and tabs) before going onto another install.
#If different instances are used in different browser windows / tabs, session hijacking by last login will occur and hence it is advised to refrain from doing so and will require closure of all browser instances (windows and tabs) before going onto another install.



Revision as of 03:39, 2 February 2021

Best practices for accessing multiple installs of nuBuilder from the same server:

  1. Different subdomains for each instance is the best practice.
  2. The recent v4 code commit (and v4.5) allows one install at a time from being accessed even without logging out from another install in a single window's single tab.
  3. If different instances are used in different browser windows / tabs, session hijacking by last login will occur and hence it is advised to refrain from doing so and will require closure of all browser instances (windows and tabs) before going onto another install.

Afterall the $_SESSION variable for nuBuilder is the same for all browser tabs/windows and so is the cookie and that for the nudb as well.

Before this, #2 could not be used and suffered the same issues as #3.