home.social

#gitannex — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gitannex, aggregated by home.social.

fetched live
  1. @joeyh No rush, it's amazing that exists at all, I am very thankful for your work. 💚

  2. @joeyh No rush, it's amazing that #gitAnnex exists at all, I am very thankful for your work. 💚

  3. And apparently :gitannex: can't do importtree-only remotes¹ (without exporttree), so one really has to reimplement the rsync logic when something needs to be copied and then install the file manually...

    ¹git-annex.branchable.com/todo/

  4. And apparently :gitannex: #gitAnnex can't do importtree-only remotes¹ (without exporttree), so one really has to reimplement the rsync logic when something needs to be copied and then install the file manually...

    ¹git-annex.branchable.com/todo/

  5. I wish had a flag --delete-target-before-copy-if-a-copy-is-deemed-necessary

    I couldn't convince rsync to just copy stuff into a repository (with "locked" symlinks to readonly or even nonexistant targets), as it would die if the links are broken or readonly...

  6. I wish #rsync had a flag --delete-target-before-copy-if-a-copy-is-deemed-necessary

    I couldn't convince rsync to just copy stuff into a #gitAnnex repository (with "locked" symlinks to readonly or even nonexistant targets), as it would die if the links are broken or readonly...

  7. @usul nope, never got around to reviving it.

    But it's really simple: Install Debian on SSD, add ~5 pieces of spinning rust, put a RAIDz2 over them, run `zpool scrub yourname` on it every few months.

    Put your important data into #gitannex, and you can use that to sync data from your e.g. laptop onto the NAS. Add 1-3 external drives for git-annex to sync onto. Set it to three copies minimum.

    My NAS is mostly switched off, I really only use it for cold-ish storagt.

  8. @usul nope, never got around to reviving it.

    But it's really simple: Install Debian on SSD, add ~5 pieces of spinning rust, put a RAIDz2 over them, run `zpool scrub yourname` on it every few months.

    Put your important data into #gitannex, and you can use that to sync data from your e.g. laptop onto the NAS. Add 1-3 external drives for git-annex to sync onto. Set it to three copies minimum.

    My NAS is mostly switched off, I really only use it for cold-ish storagt.

  9. @usul #openzfs raidz2 with everything important in #gitannex with three copies (two on removable disks)

  10. @usul #openzfs raidz2 with everything important in #gitannex with three copies (two on removable disks)

  11. Thanks to @knue and Vahideh Alizadeh from @HZDR / CASUS for a fun workshop at the #ISC #HighPerformance conference today in Hamburg! We talked about #gitannex, @datalad and the #datalad-slurm extension, and met a friendly and interested crowd from across the world. It was cool to introduce decentral version control for large data to this technically highly proficient audience! :git: :unix:

  12. Thanks to @knue and Vahideh Alizadeh from @HZDR / CASUS for a fun workshop at the #ISC #HighPerformance conference today in Hamburg! We talked about #gitannex, @datalad and the #datalad-slurm extension, and met a friendly and interested crowd from across the world. It was cool to introduce decentral version control for large data to this technically highly proficient audience! :git: :unix:

  13. My :forgejo: now takes >20s to load the activity page 🤡

    This is on cold starts, subsequent refreshes are fast. I think I have reached the limit storing forgejo's data on a WD4TB USB disk, using an sqlite database and having a *ridiculous* amount of commits due to :gitannex: 😅

  14. My :forgejo: #forgejo now takes >20s to load the activity page 🤡

    This is on cold starts, subsequent refreshes are fast. I think I have reached the limit storing forgejo's data on a WD4TB USB disk, using an sqlite database and having a *ridiculous* amount of commits due to :gitannex: #gitAnnex 😅

  15. Wow, :gitannex: not generally forcing existence of a synced/main branch anymore? Sounds like an amazing change that will reduce confusion and the branch juggling. 👍

    source.git-annex.branchable.co

  16. :git: really needs an easy way to temporarily disable specific remotes (e.g. when they're unresponsive right now) that does not involve completely removing (then recreating) it or commenting it out in `git config --edit`. Would also be very beneficial for :gitannex: which gets painfully slow if a remote is unresponsive as it keeps retrying at different phases e.g. in a single `git annex assist` call.

  17. :git: #git really needs an easy way to temporarily disable specific remotes (e.g. when they're unresponsive right now) that does not involve completely removing (then recreating) it or commenting it out in `git config --edit`. Would also be very beneficial for :gitannex: #gitAnnex which gets painfully slow if a remote is unresponsive as it keeps retrying at different phases e.g. in a single `git annex assist` call.

  18. Hey @matrss, did you teach to update the default branch to whatever comes after anything named *git-annex on push-to-create?

    I just witnessed a git annex push first creating a repo with only a git-annex branch (would previously be used as the default branch), but after it was finished, the *main* branch was suddenly the default on my forgejo-aneksajo instance! 🤯

    That's really cool, so you can just `git annex push` to create a repo now, amazing! 🥳

  19. Hey @matrss, did you teach #forgejoAneksajo to update the default branch to whatever comes after anything named *git-annex on push-to-create?

    I just witnessed a git annex push first creating a repo with only a git-annex branch (would previously be used as the default branch), but after it was finished, the *main* branch was suddenly the default on my forgejo-aneksajo instance! 🤯

    That's really cool, so you can just `git annex push` to create a repo now, amazing! 🥳

    #git #gitAnnex #forgejo

  20. @ivan @schmittlauch agenix is also for runtime, not evaltime secrets, so that's not what they meant. For a long time I also had a public config and looked for good ways to conceal private parts (e.g. with ) but eventually realised it's too much pain and hinders reusage by others, so went the arguably cleaner way: utilities in a public repo that you and others can source in their private ones. Can't point to specific service configs then, though...

    discourse.nixos.org/t/public-r

  21. @ivan @schmittlauch agenix is also for runtime, not evaltime secrets, so that's not what they meant. For a long time I also had a public #nixos config and looked for good ways to conceal private parts (e.g. with #gitAnnex) but eventually realised it's too much pain and hinders reusage by others, so went the arguably cleaner way: utilities in a public repo that you and others can source in their private ones. Can't point to specific service configs then, though...

    discourse.nixos.org/t/public-r

  22. And here is my published dissertation @umphy, about quantifying the natural CO2 exhaust at the Starzach site in Southwest Germany (my result: ~10t/d):

    hdl.handle.net/10900/176213

    I used a lot of software and hardware for all of it and it was amazing. Honorable mentions: , , , , , , . I just wish I'd used / sooner.

    licensed under CC-BY-4.0

  23. And here is my published dissertation @umphy, about quantifying the natural CO2 exhaust at the Starzach site in Southwest Germany (my result: ~10t/d):

    hdl.handle.net/10900/176213

    I used a lot of #FOSS software and hardware for all of it and it was amazing. Honorable mentions: #gitAnnex, #dataLad, #KiCAD, #OpenSCAD, #PlatformIO, #Arduino, #TexLaTeX. I just wish I'd used #nix / #nixOS sooner.

    licensed #OpenAccess under #CreativeCommons CC-BY-4.0

    #PhDLife

  24. I noticed that the aarch64 git annex standalone build test suite (emulated on NixOS under x86_64) is *far* slower than the the nixpkgs-provided one:

    > nix run nixpkgs#legacyPackages.aarch64-linux.git-annex test
    # ... takes ~8min

    > nix run gitlab:nobodyinperson/yannix#packages.aarch64-linux.git-annex-standalone test
    # ... takes ~35min

  25. I noticed that the aarch64 git annex standalone build test suite (emulated on NixOS under x86_64) is *far* slower than the the nixpkgs-provided one:

    > nix run nixpkgs#legacyPackages.aarch64-linux.git-annex test
    # ... takes ~8min

    > nix run gitlab:nobodyinperson/yannix#packages.aarch64-linux.git-annex-standalone test
    # ... takes ~35min

    #nix #gitAnnex #NixOS

  26. @xdej Just to be clear: is a caldav/carddav server which just uses files as storage and can be configured to commit any changes to git. My module services.radicale.git implements that and also automatic sync with given remotes. It's not a general-purpose syncing module, but that's on my todo list as well, using plain or .

  27. @xdej Just to be clear: #radicale is a caldav/carddav server which just uses files as storage and can be configured to commit any changes to git. My #nixos module services.radicale.git implements that and also automatic sync with given remotes. It's not a general-purpose syncing module, but that's on my todo list as well, using plain #git or #gitAnnex.

  28. @nobodyinperson I'm asking you first because involving #gitannex would be high on my priority list. Really this wouldn't need to be #hledger specific as it could just as well be paired with #ledgercli or #beancount either directly or via CSV or whatever. I'm not a huge GitLab fan these days but can do it if you prefer. Codeberg seems more aligned or GitHub having the advantage of contributor pool. Thoughts?

  29. @nobodyinperson I'm asking you first because involving #gitannex would be high on my priority list. Really this wouldn't need to be #hledger specific as it could just as well be paired with #ledgercli or #beancount either directly or via CSV or whatever. I'm not a huge GitLab fan these days but can do it if you prefer. Codeberg seems more aligned or GitHub having the advantage of contributor pool. Thoughts?

  30. Hi :gitannex: and crowd. How do I configure git so a `git annex assist` (or the assistant) will *never* stop in a merge conflict? It should just choose one side, I don't care about conflicts.

    @joeyh @musicmatze @datalad @matrss

  31. Hi :gitannex: #git and #gitAnnex crowd. How do I configure git so a `git annex assist` (or the assistant) will *never* stop in a merge conflict? It should just choose one side, I don't care about conflicts.

    @joeyh @musicmatze @datalad @matrss

  32. @musicmatze What I am also interested in is how to bring the information from paperless back into my . Paperless can't replace a shared folder where you put e.g. SVGs, spreadsheets or documents you edit, it's an archive for static content.

    @Atemu regularly runs an export and uses that as a git annex special remote. But the configurable directory structure is rather limited. Maybe I'll import it to a subdirectory of our git annex repo+metadata would be amazing.

    ¹github.com/Atemu/nixos-config/

  33. @musicmatze What I am also interested in is how to bring the information from paperless back into my #gitAnnex. Paperless can't replace a shared folder where you put e.g. SVGs, spreadsheets or documents you edit, it's an archive for static content.

    @Atemu regularly runs an export and uses that as a git annex special remote. But the configurable directory structure is rather limited. Maybe I'll import it to a subdirectory of our git annex repo+metadata would be amazing.

    ¹github.com/Atemu/nixos-config/

  34. @musicmatze Yeah, I dumped our shared :gitannex: folder into it and it's a lot 😅 Also the ASN QR code thing¹ is amazing, put a QR code on the start of every related bunch of papers, then scan the whole stack at once → splits it automatically and sets the ASN metadata field.

    Dokumente im Posteingang: 110
    Dokumente insgesamt: 4805
    Zeichen insgesamt: 45.402.448
    Aktuelle ASN: 122

    ¹youtube.com/watch?v=E1Rjb5bIw-A

  35. @musicmatze Yeah, I dumped our shared :gitannex: #gitAnnex folder into it and it's a lot 😅 Also the ASN QR code thing¹ is amazing, put a QR code on the start of every related bunch of papers, then scan the whole stack at once → #paperless splits it automatically and sets the ASN metadata field.

    Dokumente im Posteingang: 110
    Dokumente insgesamt: 4805
    Zeichen insgesamt: 45.402.448
    Aktuelle ASN: 122

    ¹youtube.com/watch?v=E1Rjb5bIw-A

  36. crowd:

    Anyone else running into this experience-crippling bug causing the activity page (de facto landing page for every user) to take extremely long to load (for me 10 seconds)?

    codeberg.org/forgejo/forgejo/i

    @datalad @forgejo

  37. #forgejoAneksajo #gitAnnex #dataLad crowd:

    Anyone else running into this experience-crippling #forgejo bug causing the activity page (de facto landing page for every user) to take extremely long to load (for me 10 seconds)?

    codeberg.org/forgejo/forgejo/i

    @datalad @forgejo

  38. Some more `git subtree push` quirks:

    • `git subtree push` (obviously) does not push :gitannex: files to the remote. Syncing annexed files there is unergonomic.
    • `git subtree push` also strips commit signatures (e.g. GPG and as such timestamps). The truth lies in the monorepo only. Understandable, but very uncool.

    git submodules have neither problem, but without tools like :datalad: you can't commit at once.

  39. Some more `git subtree push` quirks:

    • `git subtree push` (obviously) does not push :gitannex: #gitAnnex files to the remote. Syncing annexed files there is unergonomic.
    • `git subtree push` also strips commit signatures (e.g. GPG and as such #OpenTimeStamps timestamps). The truth lies in the monorepo only. Understandable, but very uncool.

    git submodules have neither problem, but without tools like :datalad: #datalad you can't commit at once.

    #git #gitSubTree

  40. My kids are tech-privileged. They're playing Super Mario 64 on the steamdeck via #RetroArch, and wanted to play Kirby. While they played, I SSHed onto the Steamdeck, and #GitAnnex get'ed the Kirby ROM from my fileserver. #techdad

  41. My kids are tech-privileged. They're playing Super Mario 64 on the steamdeck via #RetroArch, and wanted to play Kirby. While they played, I SSHed onto the Steamdeck, and #GitAnnex get'ed the Kirby ROM from my fileserver. #techdad

  42. I've set up a #gitAnnex self-organised session for at #39c3 day 3 0:30.

    If you're already a user or just curious about the tool, come by and have a chat! :)

    events.ccc.de/congress/2025/hu

  43. @alerque Ooh, I have a feeling that this can come in very handy with :gitannex: !

  44. @alerque Ooh, I have a feeling that this can come in very handy with :gitannex: #gitAnnex!

  45. @agowa338 Yes, and if you have many files (e.g. with :gitannex: ), then subtrees are not a way to work around slowness.

  46. @agowa338 Yes, and if you have many files (e.g. with :gitannex: #gitAnnex), then subtrees are not a way to work around slowness.

  47. Organising my :nixos: code and splitting out sharable things into a separate repo. Here for example is my package for (:forgejo: + :gitannex: support) with a couple of my patches applied:

    gitlab.com/nobodyinperson/yann

    > nix build --refresh gitlab:nobodyinperson/yannix#forgejo-aneksajo
    > result/bin/forgejo -v
    forgejo version 13.0.3-git-annex2 built with go1.25.4 : sqlite, sqlite_unlock_notify

  48. Organising my :nixos: #nix code and splitting out sharable things into a separate repo. Here for example is my package for #forgejoAneksajo (:forgejo: #forgejo + :gitannex: #gitAnnex support) with a couple of my patches applied:

    gitlab.com/nobodyinperson/yann

    > nix build --refresh gitlab:nobodyinperson/yannix#forgejo-aneksajo
    > result/bin/forgejo -v
    forgejo version 13.0.3-git-annex2 built with go1.25.4 : sqlite, sqlite_unlock_notify

  49. @inlovewithpda Is it still not resolved, what a mess. I switched to :gitannex: #gitAnnex for file syncing a while ago, so I am unaffected, but man...