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.

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

Cloning mechanism for staging -> dev #1837

Open
1 task
AetherUnbound opened this issue Nov 2, 2021 · 0 comments
Open
1 task

Cloning mechanism for staging -> dev #1837

AetherUnbound opened this issue Nov 2, 2021 · 0 comments
Labels
🤖 aspect: dx Concerns developers' experience with the codebase 🌟 goal: addition Addition of new feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: catalog Related to the catalog and Airflow DAGs

Comments

@AetherUnbound
Copy link
Contributor

Description

It would be ideal to have an easy way to replicate, copy, or clone our future staging database to our local dev database for easier bootstrapping of live data. This would reduce the time it would take to populate a local database and allow it to be jettisoned more easily.

Alternatives

We could potentially point dev instances directly at staging.

Additional context

Implementation

  • 🙋 I would be interested in implementing this feature.
@AetherUnbound AetherUnbound added 🌟 goal: addition Addition of new feature 🤖 aspect: dx Concerns developers' experience with the codebase labels Nov 2, 2021
@krysal krysal added the 🟩 priority: low Low priority and doesn't need to be rushed label Nov 18, 2022
@obulat obulat added the 🧱 stack: catalog Related to the catalog and Airflow DAGs label Feb 24, 2023
@obulat obulat transferred this issue from WordPress/openverse-catalog Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤖 aspect: dx Concerns developers' experience with the codebase 🌟 goal: addition Addition of new feature 🟩 priority: low Low priority and doesn't need to be rushed 🧱 stack: catalog Related to the catalog and Airflow DAGs
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants