@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

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

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

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

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

¹https://github.com/Atemu/nixos-config/blob/c770aad303e18b0360dcc6b79aecf2084daa4ec2/modules/paperless/module.nix#L83

nixos-config/modules/paperless/module.nix at c770aad303e18b0360dcc6b79aecf2084daa4ec2 · Atemu/nixos-config

My NixOS configurations. Contribute to Atemu/nixos-config development by creating an account on GitHub.

GitHub

@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 → #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

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

ASN-Labels in paperless-ngx: So gehts (inkl. Praxis-Demo)!

YouTube