Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FAQ: Pre-production environment #417

Merged
merged 2 commits into from
Jan 13, 2020
Merged

FAQ: Pre-production environment #417

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e5ee7bd
add pre-production environment
drnickiw Mar 18, 2019
07dc26d
Merge branch 'master' into preproduction
goruha Mar 19, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions content/faq/pre-production-environment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: "What is a pre-production environment?"
description: "Pre-production is for tagged release candidates and runs the same technologies as production, but not on the same scale."
tags:
- pre-production
- staging
- cluster
---

## Question

What does a pre-production environment look like?


## Answer

Pre-production runs in the staging account on the staging cluster. The staging cluster will also run a traditional staging environment, which is pinned to `master`. Pre-production is for tagged release candidates and runs the same technologies as production, but not on the same scale (e.g. RDS and ElastiCache, not containers for those). It lets you deploy a production release without shipping it to production in an environment that most developers have access to.