-
Notifications
You must be signed in to change notification settings - Fork 2
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
annex: web uploads #25
Comments
I did a quick experiment: it seems that if you have then uploading a matching file will cause it to get stored in LFS: that's better than the UI I would have thought of! But I don't think my implementation in #1 behaves like this; so patch that and get it working. |
Tracing: Uploaded files get POSTed to the server sends back a pointer to the temp file (it uses UUIDs) the commit goes to POST /_upload/$BRANCH with the file pointers attached that ends up calling into this function which goes and digs out the tmp files and has also makes a temporary full working-tree copy of the repo; because it has to, it can't It then calls (git-check-attr produces something like
) and then that's used to detect if it needs to run this special LFS case: |
So I think the equivalent annex code would be something like:
but don't use |
I'm not unclear if Gitea supports uploading from the web into Git LFS. If it does, then we should tweak that UI to make git-annex an option too. Otherwise the "Upload a File" menu might mislead people so that they upload files to .git/objects instead of .git/annex/objects, which isn't the end of the world if it happens once but could be a pain in general.
The text was updated successfully, but these errors were encountered: