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

Add first draft for guide #68

Closed
wants to merge 6 commits into from
Closed

Add first draft for guide #68

wants to merge 6 commits into from

Conversation

Acconut
Copy link
Member

@Acconut Acconut commented Sep 21, 2015

This PR is a work in progress. We'll evolve a Developer Guide in it that contains best practices for implementing and deploying tus - and explains some of the design choices

@Acconut Acconut added this to the 1.1 milestone Oct 17, 2015
@kvz kvz mentioned this pull request Nov 19, 2015
@kvz
Copy link
Member

kvz commented Nov 19, 2015

Just a reminder that we had a discussion about consistency in the tus Slack channel just now and I will:

  • Add a section that you should disable redispatch on any intermediate proxy and leave retries / resumes to tus. This is the best way to be sure that no 2 servers are writing to the same storage backend endpoint.

@Acconut Acconut removed this from the 1.1 milestone Aug 30, 2016
@Acconut
Copy link
Member Author

Acconut commented Sep 24, 2019

This PR has been superseded by the FAQ available at https://tus.io/faq.html

@Acconut Acconut closed this Sep 24, 2019
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.

2 participants