#gitannex — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gitannex, aggregated by home.social.
-
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
-
@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
-
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
-
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
-
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
-
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
-
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 -
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 -
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 -
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 -
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 -
@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.
-
@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.
-
@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.
-
@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.
-
@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?
-
@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?
-
@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?
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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 -
@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 -
@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 -
@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 -
@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 -
#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
-
#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
-
#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
-
#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
-
#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.
-
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.
-
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.
-
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.
-
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.
-
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