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!  
This week's upcoming #gitAnnex release is shaping up to be a big hashing update, with support for using Botan for faster hashing, as well as the very fast Blake3, and XXH3 for when you need super-fast and small but non-cryptographically secure.

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 😅

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. 👍

http://source.git-annex.branchable.com/?p=source.git;a=commitdiff;h=3417200fc47eba03d03955511b1f639d34aa8af8

 #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.

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

@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...

https://discourse.nixos.org/t/public-reusable-flake-with-private-parts/73049

Public, reusable flake with private parts

I am looking for a way to have a public flake that is reusable as inputs in other flakes, but some parts of the flake are private. I think this is a very common thing, people sharing their config, but don’t want to share their secrets of course or some network settings. If those private parts are just plain files, then agenix or sops can be used, encrypted versions of those secrets are published (still kinda meh, but okay). The problem arises if some nix code should be concealed as well. Here a...

NixOS Discourse
@dbat the same issue exists in the research data management world with #DataLad / #gitAnnex. One thing that I am doing for our storage servers is regularly run #duperemove on it. It requires filesystem support (xfs/btrfs), but deduplicates on an extent basis, so below the file level. If the difference between two versions only affects a small part of a file it should be able to help. I wonder if it could be run as a post-commit hook, or something like that.

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

http://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

git-annex