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

Binary attachements #83

Open
matthiasbeyer opened this issue May 2, 2017 · 1 comment
Open

Binary attachements #83

matthiasbeyer opened this issue May 2, 2017 · 1 comment

Comments

@matthiasbeyer
Copy link
Collaborator

Discussion issue for binary attachements.

Two options which I currently see here:

  • git-annex, which is an awesome tool and fits perfectly well for the job, but has the one disadvantage that it uses symlinks (so in-tree "files") for referencing content
  • ipfs, which is wonderful and works great, but then binary content is not tied to the repository. This means that binary blobs can be dropped (and would be lost then) without modifying the repository at all. I'm not sure whether we want such a thing. With IPLD, though, we could still refer from the content to the issue (more accurately: To a hash) it belongs to. So that's not a problem.

Of course this is not a thing which might be solved tomorrow, but I'd like to open this anyways to keep track of ideas.

@Profpatsch
Copy link

Profpatsch commented May 2, 2017

git annex is awesome, but quite a heavyweight (500+ modules when compiling, dozens of dependencies). Binary data should be stored inside the repo though (otherwise the big advantage of git—offline development—is partly lost).

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

No branches or pull requests

2 participants