As an admin, you will have access to two Lean Library environments:

  1. beta2.leanlibrary.com
    Designed to allow you early access to new features of Lean Library and short term experiments with configuration settings

  2. app2.leanlibrary.com
    The live environment your users have access to

Release Process

We employ a multi-stage release process. 

  1. Our development teams develop within their own environment 

  2. Test branches are made available for testing by Lean Library staff on a test server

  3. After internal testing by Lean Library staff, we will release new features to beta2.leanlibrary.com about one week before they are released to app2.leanlibrary.com (live). This will provide you with an opportunity to familiarize yourself with new features and conduct any testing you deem valuable.

We will inform via email as soon as a new beta or live release is available. 

Beta Environment

The beta environment is a perfect replica of the live environment both in terms of the technology and your data.

How to login to Beta Environment?

To log in to Beta environment, please send an email to support@leanlibrary.com to request an account. Once you have received your account activation email, please log in via beta2.leanlibrary.com

Connection between Live & Beta

Any change you make in beta will NOT be reflected in the live environment, as these two environments connect to their own distinct databases, which are not connected.

While both environments are hosted on AWS and are thus on the same virtual network, they are protected by distinct security groups to provide additional protection to you.

What is your Backup Process?

Our database is automatically backed up daily.

What is your Disaster Recovery Process?

  1. Lean Library utilizes an immutable server setup. In other words, we are able to rebuild our server infrastructure at any time, based on the configurations desired.

  2. After rebuilding the server environment, we would restore the database from the AWS hosted backup

  3. Lastly, we would rebuild the project from source

Obviously, we do absolutely everything to avoid needing to use this disaster recovery process, but it is good to know that we have a process that would allow us to recover from disaster within a reasonable amount of time.

How do you monitor your systems?

We employ a number of third party tools that are designed to help us monitor our systems for optimal performance.

We use a Software as a Service product for log-file analysis, allowing us to analyze our logfiles and set alert conditions, which will be brought to the attention of our development team.

Additionally, we use a Software as a Service product for performance monitoring of our server environments. It allows us to see up to the minute information on the health of our system, including alerts and traces for failure conditions.

Lastly, we utilize a monitoring tool provided by our hosting partner to ensure that we have a comprehensive view of performance.

For each of the tools, particular alert conditions have been set and are continuously reviewed for appropriateness to ensure that the right team members are informed of any noticeable system event, which would require their attention.

Did this answer your question?