Skip to content

Issues: prior-art-archive/migration-2019

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

9 Open 6 Closed
9 Open 6 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

v2-dev and v2-prod database schemas differ
#16 opened Jul 22, 2019 by reefdog v2 Migration
1
Identify the uploads linked to no discernible Organization enhancement New feature or request
#14 opened Jul 18, 2019 by reefdog
4
Re-index v2-prod ElasticSearch? enhancement New feature or request question Further information is requested
#13 opened Jul 5, 2019 by reefdog
Copy v1-prod S3 objects to v2-prod
#12 opened Jul 5, 2019 by reefdog v2 Migration
Configure v2-prod to point to ElasticSearch 5.6.16 deployment
#11 opened Jul 5, 2019 by reefdog v2 Migration
Copy v1-prod S3 objects to v2-dev
#10 opened Jul 5, 2019 by reefdog v2 Migration
Copy v2-prod S3 objects to v2-dev
#9 opened Jul 5, 2019 by reefdog v2 Migration
Ensure v2-dev/v2-prod are using the same Postgres icebox Things we are tabling for now
#2 opened Jul 5, 2019 by reefdog v2 Migration
2
Setup and configure fresh v2-dev and v2-prod ElasticSearch 5.6.16 deployments
#1 opened Jul 5, 2019 by reefdog
4 of 6 tasks
v2 Migration
3
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.