home.social

#gitannex — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gitannex, aggregated by home.social.

  1. Hey @matrss, did you teach 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! 🥳

  2. @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 config and looked for good ways to conceal private parts (e.g. with ) 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...

    discourse.nixos.org/t/public-r

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

    discourse.nixos.org/t/public-r

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

    discourse.nixos.org/t/public-r

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

    discourse.nixos.org/t/public-r

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

    discourse.nixos.org/t/public-r

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

    hdl.handle.net/10900/176213

    I used a lot of software and hardware for all of it and it was amazing. Honorable mentions: , , , , , , . I just wish I'd used / sooner.

    licensed under CC-BY-4.0

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

    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

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

    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

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

    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

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

    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

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

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

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

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

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

  17. @xdej Just to be clear: is a caldav/carddav server which just uses files as storage and can be configured to commit any changes to git. My 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 or .

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

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

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

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

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

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

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

  25. Hi :gitannex: and 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

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

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

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

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

  30. @musicmatze What I am also interested in is how to bring the information from paperless back into my . 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.

    ¹github.com/Atemu/nixos-config/

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

    ¹github.com/Atemu/nixos-config/

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

    ¹github.com/Atemu/nixos-config/

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

    ¹github.com/Atemu/nixos-config/

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

    ¹github.com/Atemu/nixos-config/

  35. @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 → splits it automatically and sets the ASN metadata field.

    Dokumente im Posteingang: 110
    Dokumente insgesamt: 4805
    Zeichen insgesamt: 45.402.448
    Aktuelle ASN: 122

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

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

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

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

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

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

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

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

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

  40. crowd:

    Anyone else running into this experience-crippling bug causing the activity page (de facto landing page for every user) to take extremely long to load (for me 10 seconds)?

    codeberg.org/forgejo/forgejo/i

    @datalad @forgejo

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

    codeberg.org/forgejo/forgejo/i

    @datalad @forgejo

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

    codeberg.org/forgejo/forgejo/i

    @datalad @forgejo

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

    codeberg.org/forgejo/forgejo/i

    @datalad @forgejo

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

    codeberg.org/forgejo/forgejo/i

    @datalad @forgejo

  45. Some more `git subtree push` quirks:

    • `git subtree push` (obviously) does not push :gitannex: files to the remote. Syncing annexed files there is unergonomic.
    • `git subtree push` also strips commit signatures (e.g. GPG and as such timestamps). The truth lies in the monorepo only. Understandable, but very uncool.

    git submodules have neither problem, but without tools like :datalad: you can't commit at once.

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

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

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

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

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