#gitannex — Public Fediverse posts

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

@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

@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

@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

@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

#GNOMEBoxes doesn't see symlinked ISOs:

https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/1085

Not ideal for tracking your installation image files with :gitannex: #gitAnnex...

EDIT: Fail... 🤦 Turns out the ISOs were 'git annex drop'ped, so the symlinks were broken and it makes sense that Gnome Boxes didn't list them.

Our fleet of #multicopter​s is growing as we prepare for our part in the #TeamX¹ campaign in 🇦🇹 #Austria next month.

We'll provide valuable in-situ #temperature, #humidity, #wind and #turbulence measurements with our custom meteorological PARASITE system on multiple copters in parallel across the Inn valley. This data will help with understanding wind shear in mountainous regions and eventually improve
#mountainWeather forecasts.

Our PARASITEs carry several atmospheric sensors and we derive the turbulent 3D wind vector from the copter movements. @nobodyinperson suggested to name them like #BugsLife characters 🐛😉. He put a nicely customized ❄️ #NixOS in there to stay in control of the software, integrate it all and sync data e.g. to a #forgejoAneksajo instance (#forgejo with #gitAnnex support), our own or the one of @fzj_rdm during the VITAL campaign last year.

#Austria #Österreich #Inntal #Innsbruck #meteorology

¹https://www.teamx-programme.org/observational-campaign/

Hier ist die Aufzeichnung meines #TdF4 talks letzten Samstag über „Das Leben in Git (Annex)”:

https://media.ccc.de/v/tdf4-26-das-leben-in-git-annex-

:git: #git :gitannex: #gitAnnex #radicale #opentimestamps #annextimelog #passwordStore

In the latest :sailfishos: #SailfishOS community news, @flypig wrote about my endeavour installing the :nixos: #nix package manager on SailfishOS:

https://forum.sailfishos.org/t/sailfish-community-news-14th-december-nix/17577

Also mentioned: #gitAnnex #passwordStore #NixOS #GnuPG

Git-Annex

https://git-annex.branchable.com/

#HackerNews #GitAnnex #DistributedVersionControl #DataManagement #OpenSource #TechNews

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

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

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

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

@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

@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

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

#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)?

https://codeberg.org/forgejo/forgejo/issues/9040

@datalad @forgejo

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

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

I"m currently thinking a bit how I want to organise my stuff.

I noticed that for a long time I only managed my calendar through the Nextcloud interface.
Which lead to the following questions.

- What if I would carry all my data with me?
- How much disk space would I need?
- Or what if I would go back to manually syncing things?
- How does #localfirst look like in 2026?
- Is #gitannex something that could help here?
- How do you play local music on an iPhone?

Does someone have experience with this and would like to share some inputs?

I've seen that #offlinefirst is a hashtag that is mainly used for a development practice, how do we call this for users?

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! :)

https://events.ccc.de/congress/2025/hub/event/detail/git-annex-workshop

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

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

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:

https://gitlab.com/nobodyinperson/yannix/-/blob/6353a52f63ec866b39fd50046f875587fcfed49e/packages/forgejo-aneksajo.nix

> 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

RE: https://mastodon.social/@whitequark/115635167578691059

Thank you

- @joeyh for :gitannex: #gitAnnex
- @matrss for maintaining #forgejoAneksajo
- @simonmic for :hledger: #hledger
- John Collins for #latexmk

and many people maintaining other #FOSS projects I rely upon

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

Do you have big data to share in a forge? Try #forgejoaneksajo! It's an active soft fork of @forgejo, adding git-annex support.
@matrss gave a nice talk about it on @distribits, which you can watch there. Thank you!

https://www.distribits.live/talks/2025/risse-forgejo-aneksajo-a-git-annex-datalad-forge/

PS: I wish #GinGNode (gin.g-node.org) will update to this at some point in the future! It goes one step further, adding DOIs to datasets/code.

#distribits2025 #forgejo #distribits #gitannex #DataLad

Anyone using #gitannex with a tape library or a bunch of smaller backup disks? Would be interested in seeing and hearing about your setup to learn from :)

Extremely new to git annex, but from what I've seen it is basically ideal for managing storing multiple copies of data on a bunch of independent disks especially when they should be able to go offline and be not directly available for most of the time.

wtf is "git annex" and why did I not hear about it earlier?

> > git-annex allows managing large files with git, without storing the file contents in git. It can sync, backup, and archive your data, offline and online. Checksums and encryption keep your data safe and secure. Bring the power and distributed nature of git to bear on your large files with git-annex.

> Annex supports (...) web, bittorrents, XMPP, and S3 to name a few.

https://walkergriggs.com/2023/04/01/how_to_overcomplicate_offline_storage/

#gitannex #git #storage #filesystem

@olm_e @FreeCAD You could use :gitannex: #gitAnnex and/or :datalad: #dataLad to version control your designs. I have not tried it with #FreeCAD, but I do it all the time with #solveSpace and #OpenSCAD. Git Annex allows version-controlling arbitrarily-large files and provides a simple 'git annex assist` command to 'do the git stuff' and sync everyone up. Don't know how assemblies work in FreeCAD, but if it is one file that sources other, independent files, then it should work.

I need some #nixos #followerpower

I have a #beancount git repository. I want to push that to one of my hosts. That host should run the #fava software and automatically update its checkout (and restart fava) after I pushed to it.
Having a bare repository and a checkout for hosting is ok, the checkout should be a shallow clone in this case (dont need the history for serving a specific commit/latest master).

Of course I want to conf all that using nix. It is ok to use containers, but not docker, only nixos containers (systemd-nspawn).

How to?

Bonus points: that repository is also a #gitannex repo!

:boost_ok:

Oh wow and C++ #nix (now?) apparently doesn't mind :gitannex: #gitAnnex anymore. #lix for example refuses to do anything if the flake.lock is behind a smudge filter and your worktree is clean. You have to *manually* dirtyfy the worktree to be able to work with lix. Multiple good arguments to stay on #cppnix for me.

Oh wow and C++ #nix (now?) apparently doesn't mind :gitannex: #gitAnnex anymore. #lix for example refuses to do anything if the flake.lock is behind a smudge filter and your worktree is clean. You have to *manually* dirtyfy the worktree to be able to work with lix. Multiple good arguments to stay on #cppnix for me.

Oh wow and C++ #nix (now?) apparently doesn't mind :gitannex: #gitAnnex anymore. #lix for example refuses to do anything if the flake.lock is behind a smudge filter and your worktree is clean. You have to *manually* dirtyfy the worktree to be able to work with lix. Multiple good arguments to stay on #cppnix for me.

Oh wow and C++ #nix (now?) apparently doesn't mind :gitannex: #gitAnnex anymore. #lix for example refuses to do anything if the flake.lock is behind a smudge filter and your worktree is clean. You have to *manually* dirtyfy the worktree to be able to work with lix. Multiple good arguments to stay on #cppnix for me.

Oh wow and C++ #nix (now?) apparently doesn't mind :gitannex: #gitAnnex anymore. #lix for example refuses to do anything if the flake.lock is behind a smudge filter and your worktree is clean. You have to *manually* dirtyfy the worktree to be able to work with lix. Multiple good arguments to stay on #cppnix for me.

My daughter prettified my #EGU25 poster, I love it 😂

Come find me in hall X5 poster X5.166 talk about our copter measurements and how I use :gitannex: #gitAnnex to manage the data.

#UAS #multicopter #meteorology #PapaSein #parenting #FediEltern

Next year I'll be working on atmospheric measurements with multicopters. I really look forward to use :gitannex: #gitAnnex on all those drones to asynchronously sync data, history and state and to make sure all measurement data was properly transferred off the system.

#UAS #multicopter #drone #meteorology

📝 #NoteToSelf: Write an #scrypt key backend for #gitAnnex to securely store secrets in a #git repository. The default (unsalted #SHA256 with the file size known) is good for file integrity but not ideal for secrets.

https://git-annex.branchable.com/backends/

Our fleet of #multicopter​s is growing as we prepare for our part in the #TeamX¹ campaign in 🇦🇹 #Austria next month.

We'll provide valuable in-situ #temperature, #humidity, #wind and #turbulence measurements with our custom meteorological PARASITE system on multiple copters in parallel across the Inn valley. This data will help with understanding wind shear in mountainous regions and eventually improve
#mountainWeather forecasts.

Our PARASITEs carry several atmospheric sensors and we derive the turbulent 3D wind vector from the copter movements. @nobodyinperson suggested to name them like #BugsLife characters 🐛😉. He put a nicely customized ❄️ #NixOS in there to stay in control of the software, integrate it all and sync data e.g. to a #forgejoAneksajo instance (#forgejo with #gitAnnex support), our own or the one of @fzj_rdm during the VITAL campaign last year.

#Austria #Österreich #Inntal #Innsbruck #meteorology

¹https://www.teamx-programme.org/observational-campaign/

Our fleet of #multicopter​s is growing as we prepare for our part in the #TeamX¹ campaign in 🇦🇹 #Austria next month.

We'll provide valuable in-situ #temperature, #humidity, #wind and #turbulence measurements with our custom meteorological PARASITE system on multiple copters in parallel across the Inn valley. This data will help with understanding wind shear in mountainous regions and eventually improve
#mountainWeather forecasts.

Our PARASITEs carry several atmospheric sensors and we derive the turbulent 3D wind vector from the copter movements. @nobodyinperson suggested to name them like #BugsLife characters 🐛😉. He put a nicely customized ❄️ #NixOS in there to stay in control of the software, integrate it all and sync data e.g. to a #forgejoAneksajo instance (#forgejo with #gitAnnex support), our own or the one of @fzj_rdm during the VITAL campaign last year.

#Austria #Österreich #Inntal #Innsbruck #meteorology

¹https://www.teamx-programme.org/observational-campaign/

Our fleet of #multicopter​s is growing as we prepare for our part in the #TeamX¹ campaign in 🇦🇹 #Austria next month.

We'll provide valuable in-situ #temperature, #humidity, #wind and #turbulence measurements with our custom meteorological PARASITE system on multiple copters in parallel across the Inn valley. This data will help with understanding wind shear in mountainous regions and eventually improve
#mountainWeather forecasts.

Our PARASITEs carry several atmospheric sensors and we derive the turbulent 3D wind vector from the copter movements. @nobodyinperson suggested to name them like #BugsLife characters 🐛😉. He put a nicely customized ❄️ #NixOS in there to stay in control of the software, integrate it all and sync data e.g. to a #forgejoAneksajo instance (#forgejo with #gitAnnex support), our own or the one of @fzj_rdm during the VITAL campaign last year.

#Austria #Österreich #Inntal #Innsbruck #meteorology

¹https://www.teamx-programme.org/observational-campaign/

Our fleet of #multicopter​s is growing as we prepare for our part in the #TeamX¹ campaign in 🇦🇹 #Austria next month.

We'll provide valuable in-situ #temperature, #humidity, #wind and #turbulence measurements with our custom meteorological PARASITE system on multiple copters in parallel across the Inn valley. This data will help with understanding wind shear in mountainous regions and eventually improve
#mountainWeather forecasts.

Our PARASITEs carry several atmospheric sensors and we derive the turbulent 3D wind vector from the copter movements. @nobodyinperson suggested to name them like #BugsLife characters 🐛😉. He put a nicely customized ❄️ #NixOS in there to stay in control of the software, integrate it all and sync data e.g. to a #forgejoAneksajo instance (#forgejo with #gitAnnex support), our own or the one of @fzj_rdm during the VITAL campaign last year.

#Austria #Österreich #Inntal #Innsbruck #meteorology

¹https://www.teamx-programme.org/observational-campaign/

If you are attending this year's @distribits end of October¹ and you want to be dressed 'appropriately' 😉, last year I organised that hellotux.com offers :gitannex: #gitAnnex² and :datalad: #dataLad³ shirts, sweaters. Now also backpacks 🎒 and towels can be ordered.

I ordered several items and the quality is good. Properly stitched logos that never wash off. They are a small family business that uses and supports #FOSS.

²https://www.hellotux.com/git-annex
³https://www.hellotux.com/datalad
¹https://www.distribits.live/

@diegolakatos If you like :gitannex: #gitAnnex, there's a fork of #forgejo: #forgejoAneksajo:

https://codeberg.org/forgejo-aneksajo/forgejo-aneksajo

With this, you can also store arbitrarily big files on your forgejo, use it as a file syncing service like #syncthing, organise your research data or media database with #datalad, etc.

@umphy :gitannex: #gitAnnex and :datalad: #dataLad organize the data and sync it to our own :forgejo: #forgejoAneksajo instance. You can instantly see if everything is there and worked. A great workflow!

#forgejo

There is now a #gitAnnex package on #PyPi: https://pypi.org/project/git-annex/

This should make it simpler to deploy git-annex in Python virtual environments, also as versioned dependencies for software like #Datalad

Packages are built for Linux, Windows, and Mac via GitHub actions: https://github.com/psychoinformatics-de/git-annex-wheel/

Contributions to cover more platforms are most welcome!

I want a build system that:

- is as powerful and flexible as #SCons
- as readable and concise as #SnakeMake
- has a fricking progress bar+ETA
- is :datalad: #datalad / :gitannex: #gitannex agnostic (knows that files can be fetched from elsewhere
- remembers how long building things takes
- balances that to decide if rebuilding locally instead of fetching gigabytes via slow internet is favorable
- integrates well with :nixos: #nix for reproducibility

#rdm #dataAnalysis