#gitannex — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #gitannex, aggregated by home.social.
-
-
-
-
-
-
And apparently :gitannex: #gitAnnex can't do importtree-only remotes¹ (without exporttree), so one really has to reimplement the rsync logic when something needs to be copied and then install the file manually...
¹https://git-annex.branchable.com/todo/importtree_only_remotes/
-
And apparently :gitannex: #gitAnnex can't do importtree-only remotes¹ (without exporttree), so one really has to reimplement the rsync logic when something needs to be copied and then install the file manually...
¹https://git-annex.branchable.com/todo/importtree_only_remotes/
-
And apparently :gitannex: #gitAnnex can't do importtree-only remotes¹ (without exporttree), so one really has to reimplement the rsync logic when something needs to be copied and then install the file manually...
¹https://git-annex.branchable.com/todo/importtree_only_remotes/
-
And apparently :gitannex: #gitAnnex can't do importtree-only remotes¹ (without exporttree), so one really has to reimplement the rsync logic when something needs to be copied and then install the file manually...
¹https://git-annex.branchable.com/todo/importtree_only_remotes/
-
And apparently :gitannex: #gitAnnex can't do importtree-only remotes¹ (without exporttree), so one really has to reimplement the rsync logic when something needs to be copied and then install the file manually...
¹https://git-annex.branchable.com/todo/importtree_only_remotes/
-
@usul nope, never got around to reviving it.
But it's really simple: Install Debian on SSD, add ~5 pieces of spinning rust, put a RAIDz2 over them, run `zpool scrub yourname` on it every few months.
Put your important data into #gitannex, and you can use that to sync data from your e.g. laptop onto the NAS. Add 1-3 external drives for git-annex to sync onto. Set it to three copies minimum.
My NAS is mostly switched off, I really only use it for cold-ish storagt.
-
@usul nope, never got around to reviving it.
But it's really simple: Install Debian on SSD, add ~5 pieces of spinning rust, put a RAIDz2 over them, run `zpool scrub yourname` on it every few months.
Put your important data into #gitannex, and you can use that to sync data from your e.g. laptop onto the NAS. Add 1-3 external drives for git-annex to sync onto. Set it to three copies minimum.
My NAS is mostly switched off, I really only use it for cold-ish storagt.
-
@usul nope, never got around to reviving it.
But it's really simple: Install Debian on SSD, add ~5 pieces of spinning rust, put a RAIDz2 over them, run `zpool scrub yourname` on it every few months.
Put your important data into #gitannex, and you can use that to sync data from your e.g. laptop onto the NAS. Add 1-3 external drives for git-annex to sync onto. Set it to three copies minimum.
My NAS is mostly switched off, I really only use it for cold-ish storagt.
-
@usul nope, never got around to reviving it.
But it's really simple: Install Debian on SSD, add ~5 pieces of spinning rust, put a RAIDz2 over them, run `zpool scrub yourname` on it every few months.
Put your important data into #gitannex, and you can use that to sync data from your e.g. laptop onto the NAS. Add 1-3 external drives for git-annex to sync onto. Set it to three copies minimum.
My NAS is mostly switched off, I really only use it for cold-ish storagt.
-
@usul nope, never got around to reviving it.
But it's really simple: Install Debian on SSD, add ~5 pieces of spinning rust, put a RAIDz2 over them, run `zpool scrub yourname` on it every few months.
Put your important data into #gitannex, and you can use that to sync data from your e.g. laptop onto the NAS. Add 1-3 external drives for git-annex to sync onto. Set it to three copies minimum.
My NAS is mostly switched off, I really only use it for cold-ish storagt.
-
Thanks to @knue and Vahideh Alizadeh from @HZDR / CASUS for a fun workshop at the #ISC #HighPerformance conference today in Hamburg! We talked about #gitannex, @datalad and the #datalad-slurm extension, and met a friendly and interested crowd from across the world. It was cool to introduce decentral version control for large data to this technically highly proficient audience! :git: :unix:
-
Thanks to @knue and Vahideh Alizadeh from @HZDR / CASUS for a fun workshop at the #ISC #HighPerformance conference today in Hamburg! We talked about #gitannex, @datalad and the #datalad-slurm extension, and met a friendly and interested crowd from across the world. It was cool to introduce decentral version control for large data to this technically highly proficient audience! :git: :unix:
-
Thanks to @knue and Vahideh Alizadeh from @HZDR / CASUS for a fun workshop at the #ISC #HighPerformance conference today in Hamburg! We talked about #gitannex, @datalad and the #datalad-slurm extension, and met a friendly and interested crowd from across the world. It was cool to introduce decentral version control for large data to this technically highly proficient audience! :git: :unix:
-
Thanks to @knue and Vahideh Alizadeh from @HZDR / CASUS for a fun workshop at the #ISC #HighPerformance conference today in Hamburg! We talked about #gitannex, @datalad and the #datalad-slurm extension, and met a friendly and interested crowd from across the world. It was cool to introduce decentral version control for large data to this technically highly proficient audience! :git: :unix:
-
Thanks to @knue and Vahideh Alizadeh from @HZDR / CASUS for a fun workshop at the #ISC #HighPerformance conference today in Hamburg! We talked about #gitannex, @datalad and the #datalad-slurm extension, and met a friendly and interested crowd from across the world. It was cool to introduce decentral version control for large data to this technically highly proficient audience! :git: :unix:
-
Wow, :gitannex: #gitAnnex not generally forcing existence of a synced/main branch anymore? Sounds like an amazing change that will reduce confusion and the branch juggling. 👍
-
Wow, :gitannex: #gitAnnex not generally forcing existence of a synced/main branch anymore? Sounds like an amazing change that will reduce confusion and the branch juggling. 👍
-
Wow, :gitannex: #gitAnnex not generally forcing existence of a synced/main branch anymore? Sounds like an amazing change that will reduce confusion and the branch juggling. 👍
-
Wow, :gitannex: #gitAnnex not generally forcing existence of a synced/main branch anymore? Sounds like an amazing change that will reduce confusion and the branch juggling. 👍
-
:git: #git really needs an easy way to temporarily disable specific remotes (e.g. when they're unresponsive right now) that does not involve completely removing (then recreating) it or commenting it out in `git config --edit`. Would also be very beneficial for :gitannex: #gitAnnex which gets painfully slow if a remote is unresponsive as it keeps retrying at different phases e.g. in a single `git annex assist` call.
-
:git: #git really needs an easy way to temporarily disable specific remotes (e.g. when they're unresponsive right now) that does not involve completely removing (then recreating) it or commenting it out in `git config --edit`. Would also be very beneficial for :gitannex: #gitAnnex which gets painfully slow if a remote is unresponsive as it keeps retrying at different phases e.g. in a single `git annex assist` call.
-
:git: #git really needs an easy way to temporarily disable specific remotes (e.g. when they're unresponsive right now) that does not involve completely removing (then recreating) it or commenting it out in `git config --edit`. Would also be very beneficial for :gitannex: #gitAnnex which gets painfully slow if a remote is unresponsive as it keeps retrying at different phases e.g. in a single `git annex assist` call.
-
:git: #git really needs an easy way to temporarily disable specific remotes (e.g. when they're unresponsive right now) that does not involve completely removing (then recreating) it or commenting it out in `git config --edit`. Would also be very beneficial for :gitannex: #gitAnnex which gets painfully slow if a remote is unresponsive as it keeps retrying at different phases e.g. in a single `git annex assist` call.
-
:git: #git really needs an easy way to temporarily disable specific remotes (e.g. when they're unresponsive right now) that does not involve completely removing (then recreating) it or commenting it out in `git config --edit`. Would also be very beneficial for :gitannex: #gitAnnex which gets painfully slow if a remote is unresponsive as it keeps retrying at different phases e.g. in a single `git annex assist` call.
-
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! 🥳
-
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! 🥳
-
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! 🥳
-
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! 🥳
-
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