This topic is under construction for the 24.3 (March 2024) release of LabKey Server with embedded Tomcat 10. For the previous documentation, click here.
When using LabKey Server in any working lab or institution, using a
staging server gives you a test platform for upgrades and any other changes prior to deploying them in your production environment. The staging server typically runs against a snapshot of the production database, giving testers and developers a real-world platform for validation. In this topic, the term "staging" is a catchall for any server that is not your institution's production machine, but is using a copy of the database.
Staging servers are used for many different reasons, including:
- Ensuring that an upgrade of LabKey Server does not break any customization.
- Testing new modules, views, or queries being developed.
- Running usage scenarios on test data prior to launching to a large group of users.
Overview
This topic outlines some recommended settings to change when configuring a staging server. Not all possible changes are listed here, but this subset is the most useful. Doing things like changing the
color scheme on the staging server will help users know which environment they are working on and avoid inadvertent changes to the production environment.
TBD
Related Topics