lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

64
active users

#gitAnnex

2 posts1 participant0 posts today
Continued thread

And here another one: #gitAnnex is notorious for making many commits in the background to the branches synced/<yourbranch>, synced/git-annex and git-annex. These have a perfectly valid technical reason and make git annex as awesome as it is, but in a #forgejo dashboard feed, these are massively confusing as they mask the really important changes. With a little bit of template massaging, these can be filtered out. Probably better to make this configurable somehow (checkbox? 🤔), but this is a workable solution for now.

(This might interest the @datalad people @matrss @mih)

It's very useful if you self-host the #FOSS tools you need, because then you can fix little issues you have here and there on your own.

For example, we use #forgejoAneksajo (#forgejo with #gitAnnex support) to sync and collaborate on code and data. We often have long filenames, which are unfortunately obstructed by forgejo's gigantic commit message column 😅 But a bit of #CSS later and that's fixed so we can more easily browse through our multicopter flight plots 😌

🎉 Registrations are now re-opened for #distribits2025, taking place 23-24 October!
distribits.live/news/2025-dist

Join us in person (spots are limited) or remotely - sign up now at distribits.live/.

Please note:
⛔ The call for contributions is closed
🤖 The #hackathon is full, but you can ask to join the waitlist in your registration form

@datalad #gitannex #distributed #data #opendata #rdm #tech #open_source_software #conference

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

¹teamx-programme.org/observatio

🗓️ The preliminary #distribits2025 schedule is now available: distribits.live/news/2025-dist.

You can expect to hear talks about federated data management across disciplines, deep dives into :gitannex: #gitAnnex and special remotes, how to make your analysis pipelines #FAIR from beginning to end (and tools you can use to make it happen), and so much more.

If you missed the registration deadline but would still like to participate, stay tuned - we will be able to accommodate late registrations soon.

distribits · Distribits 2025: Schedule now availableThank you to everyone who has registered for and submitted contributions to the distribits 2025 meeting!

Is there a tool to set up #GitAnnex to calculate archive unpackings yet? Something™ could look at a repo's .zip / .tar.gz files, check whether any file in the repo is also in there, and annotate it as computed / computable. (I'm not aiming to restore the zip files from the content –that'd be pristine-tar territory. I'd already be happy if the compute path would be there so that the single files don't need to be in the archive).

Replied in thread

@gvwilson I try to keep all my works, when permissible, in public spaces - GitHub, public data archives etc. For anything which has sizeable data component (including containers) I use #gitannex with our @datalad , again, trying to deposit to public space. When no space publicly - "my" datasets.datalad.org and now hub.datalad.org. I do use Google for a lot unfortunately too, so periodically I take Takeout, and also place into a #gitannex repo, so I can take advantage if it's features

datasets.datalad.orgDataLad Repository

⏰ The clock is ticking — only 3 weeks left to register and submit talk ideas for #distribits2025 (deadline 01 May): distribits.live/.

We want to hear from YOU about the technologies for #distributed #data_management in your life. We also hope you’ll join us for a collaborative #hackathon to further network with other people who get excited about #rdm and #opendata. 😎

When? 🗓️ 23-25 October, 2025
Where? 📍 Düsseldorf, Germany (and online)
Cost? 💰 Nothing — it’s free!

@datalad #gitAnnex

In the latest DataLad blog post I try out two changes which were introduced in git-annex within the last year: git-remote-annex Git remote helper (this is the big one!) and a small change to enabling WebDAV special remotes. They work brilliantly, and combined they enable read-only data publishing on Nextcloud instances.

blog.datalad.org/posts/annex-n

To be distributed... · Putting new git-annex features to use with Nextcloud
More from Michał Szczepanik

The events of the past weeks have again upped the urgency of moving away from the US tech cloud. After forever Google and 18 years GitHub this is hard for me.

I am lucky that @distribits gave me the enthusiasm and the tools to make this happen for me and the #infrastructure of the #research group I am heading.

This is the first post in a series that documents our new #selfhosted setup, starting with the centerpiece forgejo-aneksajo -- #forgejo with #gitAnnex built in.

blog.datalad.org/posts/lab-inf

To be distributed... · Collaborative infrastructure for a lab: ForgejoThe first installment of a mini-series on a self-hosted, collaborative infrastructure: Run Forgejo on a small VPS or NAS as a central collaboration platform for a lab or group.

It seems that in #nix flakes one still can't use files that have to go through a git smudge filter. This apparently includes:

- git-crypt (selectively encrypt some files)
- :gitannex: #gitAnnex (manage large files outside of git)
- git-lfs (same, but less powerful than git annex)

For credentials, #agenix et al. might suffice, but for secret configs in #nix files or just for large files you want deployed to your system, the lack of support for the above tools is a huge flake blocker for me.