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

Plan for moving files server to S3 #127

Closed
wants to merge 6 commits into from
Closed

Plan for moving files server to S3 #127

wants to merge 6 commits into from

Conversation

jar398
Copy link
Member

@jar398 jar398 commented Mar 14, 2017

Mainly look at the README

@jar398 jar398 requested review from mtholder and kcranston March 14, 2017 15:15
@jar398
Copy link
Member Author

jar398 commented Mar 14, 2017

Intended to address #126 (when plan is executed)

@mtholder
Copy link
Member

We've changed a few things about files since it moved, so this doesn't work as it. But this branch has some nice documentation. So, I'm going to delete the PR for now and leave the branch.

@mtholder mtholder closed this May 15, 2020
@mtholder
Copy link
Member

(sorry "close the PR" not "delete the PR")

@jimallman
Copy link
Member

Thanks for taking a closer look. What needs to happen to preserve the docs (I assume you mean
this new stuff in file-server/README.md
)? Should we make/assign an issue for this?

@mtholder
Copy link
Member

good idea. I created #156 when files comes back on line, I can walk through it and check the docs from this PR against the current system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants