staging
A pre-production environment set up like production, where changes are tried out before they reach real users.
In more detail
Staging should match production as closely as possible, so a change that works there is likely to work for real. It uses separate data and credentials, so mistakes there do not reach users.
Example
In an Ansible project staging is usually an inventory group with its own group_vars and its own vault ID.Related terms
- production — The live environment where real users use the service, as opposed to development or testing.
- environment overlay — Keeping one shared playbook and putting the values that differ between environments in separate variable files, one per environment.
- vault ID — A label attached to Vault-encrypted data that names which password protects it, so one project can use different passwords for different environments.
- load testing — Measuring how a system behaves while a chosen amount of traffic is sent to it, to find its latency, throughput and limits.
- image promotion — Moving the exact same, already-tested image through environments, such as staging to production, without rebuilding it.
- release candidate — A specific build that might be released if it passes the remaining checks.
- environment — One place where a copy of the application runs with its own config, such as development, staging or production.
- dev/prod parity — Keeping development, staging and production as similar as possible in timing, people and tools.
- artifact promotion — Moving the exact artifact that passed testing on to the next environment, instead of building it again.
- salt — An extra value mixed into data before hashing so that otherwise identical inputs produce different hashes.
- environment variable — A named setting such as PORT=8000 that a program reads from its surroundings when it starts.
Taught in
- The Static Inventory File — Ansible Configuration Management at Scale
- Host Groups And Host Variables — Ansible Configuration Management at Scale
- Dynamic Inventory — Ansible Configuration Management at Scale
- Connections And Privilege Escalation — Ansible Configuration Management at Scale
- Vault IDs And Multiple Passwords — Ansible Configuration Management at Scale
- Environment Specific Configuration — Ansible Configuration Management at Scale
- Load Testing — Modern API Architecture: REST, GraphQL & gRPC
- Triggers and the Event Model — Continuous Integration & Continuous Delivery Pipelines
- Defining Environments in GitHub Actions — Continuous Integration & Continuous Delivery Pipelines
- Artifact Promotion: Staging to Production — Continuous Integration & Continuous Delivery Pipelines
- Codebase And Dependencies — DevOps & Site Reliability Engineering
- Config And Backing Services — DevOps & Site Reliability Engineering
- Building And Versioning The Artifact — DevOps & Site Reliability Engineering
- Unified Build Pipelines: Caching & Dependency Graphs — Production Full-Stack Engineering
- Environment Configuration: Secrets & Multi-Stage — Production Full-Stack Engineering
- Diagnostic Profiling: CPU Profiler & Heap Snapshots — Node.js Internals & Backend Services