Find Seafile related calls that we will need to emulated from the seafile API.

[aguzmans]

The objective is to list the API calls to our current system we will need and why.

Keep present the following points should be the guiding light here too: a. The react app will use multipart uploads and will implement calls to functions using the Seafile standard: https://download.seafile.com/published/web-api/home.md This means it will can endpoints with the same names, but only for things we need in this project. The idea is for it to be interoperable with Seafile. b. The react uploader has to implement something similar to this chunks uploader: https://github.com/muxinc/upchunk project, but with some important differences. We will not use exactly their API call, but try to re-use the Seafile philosophy as stated before.

Related to Non-Functional prototype: https://github.com/Sesame-Disk/cool-storage-api/issues/9 they depend on each other, as the non-functional prototype has to define those. Probably you should both take these two tasks each takes one and discuss in teh group.

Story points: 2

[ezielramos]

Seafile related calls

ping

• curl curl http://localhost:3001/api/v1/ping
• output "pong"

  obtain auth token

• curl curl -d "username=julio&password=abc" http://localhost:3001/api/v1/auth-token/ curl --data-urlencode username=julio -d password=abc http://localhost:3001/api/v1/auth-token/
• output {"token":"_Yy-JjnOsENOb3h-Yx88BwFmGcNM_XLGWEbw_3k70EI="}

  current registration

• curl curl -X POST http://localhost:3001/registrations -H "Content-Type: application/x-www-form-urlencoded" -d "username=julio&password=abc"
• output Success

  auth ping

• curl curl -H "Authorization: Token DIDDLJfEMLkhSzDeYIx9K8CBdsQo78tq6BDqBq2YlQA=" http://localhost:3001/auth/ping/
• output "pong" or the token is expired or invalid access token

[aguzmans]

hi @ezielramos , I think we should only use aphanumeric token for now. as they might need to be scaped, etc. Could you please double check on that?