WormBase / WormBase/caltech-curation-services
Sync data between prod and dev
Open
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 1
Description
This will make it easier for curators to test things on dev
We need to figure out what files need to be copied from prod to dev @WenChenWormBase @raymond91125 @azurebrd.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by identifying which files must be copied from production to development and how curators currently test on dev. Clarify the expected sync scope and safety requirements with the mentioned curators. Done means there is a defined, repeatable way to synchronize the required data between prod and dev.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100