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! 🥳
@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
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...
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
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
@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.
Yann Büchau 
Matthias Riße
Stewart V. Wright
Caleb Maclennan
