Valentin Gagarin fricklerhandwerk
  • Hamburg, Germany
  • Nix documentarian, information janitor

  • Joined on 2024-06-12
fricklerhandwerk commented on pull request fediversity/fediversity#450 2025-07-09 11:46:21 +02:00
Restrict fileset necessary for deployment tests

Ah got it

fricklerhandwerk commented on pull request fediversity/fediversity#450 2025-07-09 11:28:08 +02:00
Restrict fileset necessary for deployment tests

it's a very magical attrset, let's just take it for granted and link to reference documentation

fricklerhandwerk commented on pull request fediversity/fediversity#450 2025-07-09 11:26:49 +02:00
Restrict fileset necessary for deployment tests

But you can literally lib.fileset.subtract <this> <deployment/check>

fricklerhandwerk commented on pull request fediversity/fediversity#448 2025-07-09 11:24:28 +02:00
Grab git-hooks from npins

Not exactly convinced we should give carte blanche here as it may bloat the closure, I'd at least wish for a comment that reassures us this is a good idea.

fricklerhandwerk commented on pull request fediversity/fediversity#449 2025-07-09 11:00:42 +02:00
Unflakify deployment tests

I thought it was but seems like it's not.

fricklerhandwerk commented on pull request fediversity/fediversity#449 2025-07-09 11:00:16 +02:00
Unflakify deployment tests

CI-killing comments...

fricklerhandwerk commented on pull request fediversity/fediversity#449 2025-07-09 10:35:27 +02:00
Unflakify deployment tests

Yes agreed. And I didn't imply we should do anything about that in this PR.

fricklerhandwerk commented on pull request fediversity/fediversity#449 2025-07-09 10:25:13 +02:00
Unflakify deployment tests

Regarding the slowness -- do we even need the flake-under-test to have flake inputs? If we make the right store paths available in the test VM (e.g. by mounting the host store) we may as well get the sources in that flake-under-test from npins and save ourselves the lock override.

fricklerhandwerk commented on pull request fediversity/fediversity#449 2025-07-09 10:22:59 +02:00
Unflakify deployment tests

Arguably we don't need flake inputs here at all as we can pass store paths via sources here, which means we don't need flakes at all at the project level (unless flake-parts wants a root flake to do its thing). Not saying we need to pull through with that now, just trying to separate accidental from essential complexity.

fricklerhandwerk commented on pull request fediversity/fediversity#449 2025-07-09 10:19:32 +02:00
Unflakify deployment tests

It may be worth noting here that we're otherwise using the entire repository as is. Otherwise it's slightly too magical when you try to trace it through in your head.

fricklerhandwerk pushed to main at fediversity/fediversity 2025-07-09 10:12:48 +02:00
48c6a1f22b Extract mkFlake to own file - get flake-parts from npins (#447)
fricklerhandwerk merged pull request fediversity/fediversity#447 2025-07-09 10:12:48 +02:00
Extract `mkFlake` to own file - get `flake-parts` from npins
fricklerhandwerk commented on pull request fediversity/fediversity#447 2025-07-09 08:36:44 +02:00
Extract mkFlake to own file - get flake-parts from npins

Could be! I’ll think about it. Not a priority right now though.

fricklerhandwerk approved fediversity/fediversity#449 2025-07-09 08:34:52 +02:00
Unflakify deployment tests

LGTM conceptually! More comments on mkFlake in the respective PR.

fricklerhandwerk pushed to main at fediversity/meta 2025-07-08 12:57:28 +02:00
82a86f4515 add configuration-to-deployment dataflow diagram
fricklerhandwerk commented on pull request fediversity/fediversity#447 2025-07-08 12:47:37 +02:00
Extract mkFlake to own file - get flake-parts from npins

I was not planning to have any other changes to dependencies in the extraction of the flake under test.

I presume the flake under test will simply take the inputs in the current flake.nix,…

fricklerhandwerk approved fediversity/fediversity#447 2025-07-08 12:11:09 +02:00
Extract mkFlake to own file - get flake-parts from npins

Do I understand correctly that the next step will be extracting the flake under test, which will probably take the remaining flake inputs with it?

fricklerhandwerk pushed to main at fediversity/meta 2025-07-08 11:04:21 +02:00
343f77ef61 2025-07-08 weekly planning
fricklerhandwerk commented on issue fediversity/fediversity#103 2025-07-08 10:10:58 +02:00
code-based data model

I think we should split this into deployment data model (almost done) and migration data model (still needs research).

fricklerhandwerk opened issue fediversity/fediversity#446 2025-07-08 10:06:58 +02:00
Mid-term technical report