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

The design/idea #1

Open
yarikoptic opened this issue Mar 1, 2024 · 0 comments
Open

The design/idea #1

yarikoptic opened this issue Mar 1, 2024 · 0 comments

Comments

@yarikoptic
Copy link
Member

Problem: quite often it is difficult to understand the "topology" of available clones of a git (git-annex) repository. Especially it is hard for git which allows different names for remotes across clones.

git-annex provides each git-annex capable clone clone with a unique UUID which helps to identify clones.

git-annex info is handy to visualize the known to git annex remotes. By default their descriptions are in the form hostname:path which provides a great hint to discover them.

Desire: a tool which would automagically crawl through the the clones and draw a schematic figure providing a "map" of the remotes/clones/git-annex special remotes. A somewhat crude motivation example was to draw a schematic for

I would like the tool capable (aspects should be configurable) of

  • automatically going through
    • ssh git remotes
    • https? remotes
    • git annex special remotes
  • groupping them per each hostname or medium (e.g. multiple S3 special remotes in the same "cloud" on diagram)
  • establishing errors as corresponding remote names
  • showing git-annex UUID (may be abbreviated as cc9...835 for cc937fa9-542c-49ec-b3fc-b7c4df5d4835)
  • expressing that "map" as mermaid diagram (so similar to what I did manually in [DOC] ultimate datalad mermaid figure spatialtopology/spacetop-prep#67 (comment))

OR may be such a tool already exists?

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

1 participant