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

Jump to bottom

Keep old data? #393

Open
n8kim1 opened this issue Apr 15, 2020 · 2 comments
Open

Keep old data? #393

n8kim1 opened this issue Apr 15, 2020 · 2 comments
Assignees
@arvid220u @npfoss @n8kim1 @j-mao @wflms20110333
Labels
backend Related to competition website backend. infrastructure

Comments

@n8kim1
Copy link
Contributor

n8kim1 commented Apr 15, 2020

Should we keep old database? resumes? submissions? replays?

If we decide to:

  • Change these buckets to archival storage
  • Change the objects within them to archival storage
  • Ensure that these buckets won't be touched at all

(I think a database that's shut down is free; I'm not opposed to deleting it too though)
@n8kim1 n8kim1 added backend Related to competition website backend. infrastructure labels Apr 15, 2020
@npfoss
Copy link
Contributor

npfoss commented Apr 20, 2020

if there's little/no cost to keeping them I vote to keep.

@wflms20110333
Copy link
Contributor

+1 to above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arvid220u arvid220u

@npfoss npfoss

@n8kim1 n8kim1

@j-mao j-mao

@wflms20110333 wflms20110333

Labels
backend Related to competition website backend. infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@arvid220u @npfoss @n8kim1 @j-mao @wflms20110333