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

FAQ: Duplication between respositories #440

Closed
wants to merge 1 commit into from
Closed

FAQ: Duplication between respositories #440

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
21 changes: 21 additions & 0 deletions content/faq/duplication-between-repositories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: "Is it safe to assume significant duplication between the staging and production infrastructure repositories?"
description: "Yes, there will be a mirror image in the staging account."
tags:
- duplication
- staging
- production
- infrastructure
- repositories
---

## Question

Is it safe to assume significant duplication between the staging and production infrastructure repositories? For example, as we roll out new resources, will we need to commit & roll them out to both repositories/environments completely & separately, every time?


## Answer

Yes, there will be a mirror image in the staging account. There may be some confusion per our Codefresh demo, whereby there were two git organizations (one for staging & development, one for prod). This is typically not how we do things, but was required by the customer.

We do recommend production vs. staging Docker registries. When doing this, we recommend pushing tagged releases to both registries. However, development and staging only goes to one registry.