The Environments

A look into the local, beta and production environments and what is done on each.


We recommend three environments to work within: Development, Beta, and Production. Standard software development process requires at least three stages of environments to ensure quality control. When releasing, it is vital to make sure everything is working as expected in the previous environment before progressing it onto the next one.

Image

Local Environment

The local environment is used by the development team to build the application. All members have their own local version running on their computers, where they work on the tickets currently in the iteration.
Location: The development team’s secure local machines.
Access: This environment is available only for the development team and isn’t shown to the product manager.

Beta Environment

Once an iteration has been completed and all tests are passing, the product is released to beta for testing. The testing is completed both by the development team and the product manager as part of Conducting User Acceptance Tests.
As this can be a volatile environment, it is not recommended that any sort of important information is kept on this environment as the database may need to be wiped at any moment.
Location: Hosted on the cloud using the customer’s nominated service
Access: Typically, this is a closed environment and therefore not open to everyday users, though the product manager may choose to invite some people for user testing. Anyone with the URL can get to it, though a login is normally required.

Production Environment

The production environment is the final stage where only the most thoroughly tested code ends up. Nothing can end up in this environment without first being reviewed in the other ones.
While most people associate the production environment with the product being live, this is not necessarily the case. Until the URL is actually shared with the public, the production site can act as a platform where the public-ready code is kept.
Location: Hosted on the cloud using the customer’s nominated service
Access: Anyone with the URL (and login if required).

Helpful resources

Last updated: 15 January 2020


Start modelling your app today.