Re lfs_prefix it kind of makes sense to create it on the server side, but it also doesn't - the uploading client should set it after
doing the upload, after all the server isn't uploading. I'm thinking that maybe the right solution would be an endpoint that
provides the "right" lfs_prefix, along with the LFS server URL and an auth token. This can be used by API clients to upload and
then set the right prefix. I'm not sure about this. What do you think?
Main issue:
Nowadays all the API calls on SDKs to upload files needs to know implementation details of the server to be able to set lfs_prefix correctly. How can we provide a better UX for this?
This is a follow up of #51
Main issue:
Nowadays all the API calls on SDKs to upload files needs to know implementation details of the server to be able to set
lfs_prefix
correctly. How can we provide a better UX for this?