regression on deploy:
attribute 'lib' missing
WIP: Use
closureInfo
to avoid having to declare extra dependencies manually
Is this still relevant and did this ever work?
button works deployed
Shall we close this, as it seems to be mostly exploratory code? The TF migration is in the other PR, so what's left here as substance?
WIP: untangling
fricklerhandwerk
pushed to simplify-binpath at fricklerhandwerk/Fediversity
2025-06-12 15:19:11 +02:00
Editorial nits on architecture
As discussed yesterday I don't think the project proposal should tie itself to any implementation detail, or the success of any particular project.
bypass native flake input for Nixpkgs
fricklerhandwerk
created branch bypass-flake-inputs in fricklerhandwerk/Fediversity
2025-06-12 03:54:47 +02:00
fricklerhandwerk
pushed to bypass-flake-inputs at fricklerhandwerk/Fediversity
2025-06-12 03:54:47 +02:00
use deployed environment for launching nixops4 from the panel
fricklerhandwerk
pushed to simplify-binpath at fricklerhandwerk/Fediversity
2025-06-11 21:47:29 +02:00
fricklerhandwerk
created branch simplify-binpath in fricklerhandwerk/Fediversity
2025-06-11 21:45:53 +02:00
fricklerhandwerk
pushed to simplify-binpath at fricklerhandwerk/Fediversity
2025-06-11 21:45:53 +02:00
name paths for purity, preventing double-hash store paths
initial gantt chart for proposal rewrite
I recommend simplifying this to just the three stages (and possibly subdividing them if needed, but rather not): implementation, outreach, productive sample applications.
Editorial nits
yeah it'll likely up in a physical folder so you better have the change log printed literally