#flake — Public Fediverse posts

I want to code, so I should use:

- nix #flake #direnv
- #devbox/#devenv/#flox #direnv
- #mise
- #devcontainer
- {{ insert_other_arcane }}

And then #TaskFile or #JustFile for the command runner.

This is all in a move to progress yes. But it can be a lot for people wanting to work. 🫠

I want to code, so I should use:

- nix #flake #direnv
- #devbox/#devenv/#flox #direnv
- #mise
- #devcontainer
- {{ insert_other_arcane }}

And then #TaskFile or #JustFile for the command runner.

This is all in a move to progress yes. But it can be a lot for people wanting to work. 🫠

I want to code, so I should use:

- nix #flake #direnv
- #devbox/#devenv/#flox #direnv
- #mise
- #devcontainer
- {{ insert_other_arcane }}

And then #TaskFile or #JustFile for the command runner.

This is all in a move to progress yes. But it can be a lot for people wanting to work. 🫠

I want to code, so I should use:

- nix #flake #direnv
- #devbox/#devenv/#flox #direnv
- #mise
- #devcontainer
- {{ insert_other_arcane }}

And then #TaskFile or #JustFile for the command runner.

This is all in a move to progress yes. But it can be a lot for people wanting to work. 🫠

I want to code, so I should use:

- nix #flake #direnv
- #devbox/#devenv/#flox #direnv
- #mise
- #devcontainer
- {{ insert_other_arcane }}

And then #TaskFile or #JustFile for the command runner.

This is all in a move to progress yes. But it can be a lot for people wanting to work. 🫠

#GitHub down? Nixpkgs can and should in most cases be fetched from channels.nixos.org because that is redistributed world-wide via #fastly with much higher availability and IPv6 support.

E.g. in your #flake use

nixpkgs.url = "https://channels.nixos.org/nixos-26.05-small/nixexprs.tar.zst";

instead of the github-flavored expression. Works for all supported channels.

#nixos #nixpkgs

#GitHub down? Nixpkgs can and should in most cases be fetched from channels.nixos.org because that is redistributed world-wide via #fastly with much higher availability and IPv6 support.

E.g. in your #flake use

nixpkgs.url = "https://channels.nixos.org/nixos-26.05-small/nixexprs.tar.zst";

instead of the github-flavored expression. Works for all supported channels.

#nixos #nixpkgs

#GitHub down? Nixpkgs can and should in most cases be fetched from channels.nixos.org because that is redistributed world-wide via #fastly with much higher availability and IPv6 support.

E.g. in your #flake use

nixpkgs.url = "https://channels.nixos.org/nixos-26.05-small/nixexprs.tar.zst";

instead of the github-flavored expression. Works for all supported channels.

#nixos #nixpkgs

#GitHub down? Nixpkgs can and should in most cases be fetched from channels.nixos.org because that is redistributed world-wide via #fastly with much higher availability and IPv6 support.

E.g. in your #flake use

nixpkgs.url = "https://channels.nixos.org/nixos-26.05-small/nixexprs.tar.zst";

instead of the github-flavored expression. Works for all supported channels.

#nixos #nixpkgs

#GitHub down? Nixpkgs can and should in most cases be fetched from channels.nixos.org because that is redistributed world-wide via #fastly with much higher availability and IPv6 support.

E.g. in your #flake use

nixpkgs.url = "https://channels.nixos.org/nixos-26.05-small/nixexprs.tar.zst";

instead of the github-flavored expression. Works for all supported channels.

#nixos #nixpkgs

@yisraeldov
Now if we make the flake.nixosModules.somename : {arg1, arg2} = {}
Then we can start composing too.

In short: it's a very neat approach to modularize the options which scales better.

Those who are using nix flake-parts and dendritic pattern, feel free to correct me or simplify this please.

#nix #flakes #nixos #homemanager #nixhomemanager #flake-parts #dendritic #dendriticpattern

@yisraeldov
Now if we make the flake.nixosModules.somename : {arg1, arg2} = {}
Then we can start composing too.

In short: it's a very neat approach to modularize the options which scales better.

Those who are using nix flake-parts and dendritic pattern, feel free to correct me or simplify this please.

#nix #flakes #nixos #homemanager #nixhomemanager #flake-parts #dendritic #dendriticpattern

@yisraeldov
Now if we make the flake.nixosModules.somename : {arg1, arg2} = {}
Then we can start composing too.

In short: it's a very neat approach to modularize the options which scales better.

Those who are using nix flake-parts and dendritic pattern, feel free to correct me or simplify this please.

#nix #flakes #nixos #homemanager #nixhomemanager #flake-parts #dendritic #dendriticpattern

@yisraeldov
Now if we make the flake.nixosModules.somename : {arg1, arg2} = {}
Then we can start composing too.

In short: it's a very neat approach to modularize the options which scales better.

Those who are using nix flake-parts and dendritic pattern, feel free to correct me or simplify this please.

#nix #flakes #nixos #homemanager #nixhomemanager #flake-parts #dendritic #dendriticpattern

@yisraeldov
Personally in my config :
https://github.com/vivekanandan-ks/ksvnixospcconfigs/blob/main/flakepartsModules/xremap-fp.nix

see here how xremap requires both nixos and homeManager options to work, so I keep both in same file. Now when I don't want xremap, I just need to remove this file from the scene, that's all . No need to go to separate places like nixos module folder and homemanager module folder to delete.

#nix #flake #flake-parts #dendriticpattern

@yisraeldov
Personally in my config :
https://github.com/vivekanandan-ks/ksvnixospcconfigs/blob/main/flakepartsModules/xremap-fp.nix

see here how xremap requires both nixos and homeManager options to work, so I keep both in same file. Now when I don't want xremap, I just need to remove this file from the scene, that's all . No need to go to separate places like nixos module folder and homemanager module folder to delete.

#nix #flake #flake-parts #dendriticpattern

@yisraeldov
Personally in my config :
https://github.com/vivekanandan-ks/ksvnixospcconfigs/blob/main/flakepartsModules/xremap-fp.nix

see here how xremap requires both nixos and homeManager options to work, so I keep both in same file. Now when I don't want xremap, I just need to remove this file from the scene, that's all . No need to go to separate places like nixos module folder and homemanager module folder to delete.

#nix #flake #flake-parts #dendriticpattern

@yisraeldov
Personally in my config :
https://github.com/vivekanandan-ks/ksvnixospcconfigs/blob/main/flakepartsModules/xremap-fp.nix

see here how xremap requires both nixos and homeManager options to work, so I keep both in same file. Now when I don't want xremap, I just need to remove this file from the scene, that's all . No need to go to separate places like nixos module folder and homemanager module folder to delete.

#nix #flake #flake-parts #dendriticpattern

@yisraeldov
But in dendritic pattern we wrap option A to F under common top level attribute in same file:
flake.nixosModules.somename = {option A to C here}
flake.homeModules.somerelatedname = {option D to F here}

And then we can do like
In nixos:-
imports =
[ self.flake.nixosModules.somename ]
In hm:-
imports = [self.flake.nixosModules.someothername]

This way we can declare options of same aspects in same file and the import them later respectively.

#nix #dendritic #flake #flake-parts

@yisraeldov
But in dendritic pattern we wrap option A to F under common top level attribute in same file:
flake.nixosModules.somename = {option A to C here}
flake.homeModules.somerelatedname = {option D to F here}

And then we can do like
In nixos:-
imports =
[ self.flake.nixosModules.somename ]
In hm:-
imports = [self.flake.nixosModules.someothername]

This way we can declare options of same aspects in same file and the import them later respectively.

#nix #dendritic #flake #flake-parts

@yisraeldov
But in dendritic pattern we wrap option A to F under common top level attribute in same file:
flake.nixosModules.somename = {option A to C here}
flake.homeModules.somerelatedname = {option D to F here}

And then we can do like
In nixos:-
imports =
[ self.flake.nixosModules.somename ]
In hm:-
imports = [self.flake.nixosModules.someothername]

This way we can declare options of same aspects in same file and the import them later respectively.

#nix #dendritic #flake #flake-parts

@yisraeldov
But in dendritic pattern we wrap option A to F under common top level attribute in same file:
flake.nixosModules.somename = {option A to C here}
flake.homeModules.somerelatedname = {option D to F here}

And then we can do like
In nixos:-
imports =
[ self.flake.nixosModules.somename ]
In hm:-
imports = [self.flake.nixosModules.someothername]

This way we can declare options of same aspects in same file and the import them later respectively.

#nix #dendritic #flake #flake-parts

@yisraeldov
(Follow this thread)
#dendritic nix is the idea of modularising in a very top level option. And #flake-parts is just one tool to achieve that, there are many custom functions that many use personally on their config too.
Eg:
optionA, optionB, optionC are nixos options
optionD, optionE, optionF are home-manager options

We use A to C in a nixos module file and D to F in hm module file and we can use both in same file, coz we typically import the whole file as module.
#nix #flake

@yisraeldov
(Follow this thread)
#dendritic nix is the idea of modularising in a very top level option. And #flake-parts is just one tool to achieve that, there are many custom functions that many use personally on their config too.
Eg:
optionA, optionB, optionC are nixos options
optionD, optionE, optionF are home-manager options

We use A to C in a nixos module file and D to F in hm module file and we can use both in same file, coz we typically import the whole file as module.
#nix #flake

@yisraeldov
(Follow this thread)
#dendritic nix is the idea of modularising in a very top level option. And #flake-parts is just one tool to achieve that, there are many custom functions that many use personally on their config too.
Eg:
optionA, optionB, optionC are nixos options
optionD, optionE, optionF are home-manager options

We use A to C in a nixos module file and D to F in hm module file and we can use both in same file, coz we typically import the whole file as module.
#nix #flake

@yisraeldov
(Follow this thread)
#dendritic nix is the idea of modularising in a very top level option. And #flake-parts is just one tool to achieve that, there are many custom functions that many use personally on their config too.
Eg:
optionA, optionB, optionC are nixos options
optionD, optionE, optionF are home-manager options

We use A to C in a nixos module file and D to F in hm module file and we can use both in same file, coz we typically import the whole file as module.
#nix #flake

@yisraeldov
(Follow this thread)
#dendritic nix is the idea of modularising in a very top level option. And #flake-parts is just one tool to achieve that, there are many custom functions that many use personally on their config too.
Eg:
optionA, optionB, optionC are nixos options
optionD, optionE, optionF are home-manager options

We use A to C in a nixos module file and D to F in hm module file and we can use both in same file, coz we typically import the whole file as module.
#nix #flake

@arichtman
Recently started using #dendritic pattern using #flake parts it's really helpful.

Earlier: A new module file means I add it to a folder, then import them in my configuration.nix home.nix accordingly.

Now: a module file added to a folder. That's it.

And more awesome is that I can place both a nixos module and home module in the same file to have aspects together🔥 much more benefits

It's worth doing things this way

#nix #nixos #dendriticpattern #config #management #flakeparts

@arichtman
Recently started using #dendritic pattern using #flake parts it's really helpful.

Earlier: A new module file means I add it to a folder, then import them in my configuration.nix home.nix accordingly.

Now: a module file added to a folder. That's it.

And more awesome is that I can place both a nixos module and home module in the same file to have aspects together🔥 much more benefits

It's worth doing things this way

#nix #nixos #dendriticpattern #config #management #flakeparts

@arichtman
Recently started using #dendritic pattern using #flake parts it's really helpful.

Earlier: A new module file means I add it to a folder, then import them in my configuration.nix home.nix accordingly.

Now: a module file added to a folder. That's it.

And more awesome is that I can place both a nixos module and home module in the same file to have aspects together🔥 much more benefits

It's worth doing things this way

#nix #nixos #dendriticpattern #config #management #flakeparts

@arichtman
Recently started using #dendritic pattern using #flake parts it's really helpful.

Earlier: A new module file means I add it to a folder, then import them in my configuration.nix home.nix accordingly.

Now: a module file added to a folder. That's it.

And more awesome is that I can place both a nixos module and home module in the same file to have aspects together🔥 much more benefits

It's worth doing things this way

#nix #nixos #dendriticpattern #config #management #flakeparts

@arichtman
Recently started using #dendritic pattern using #flake parts it's really helpful.

Earlier: A new module file means I add it to a folder, then import them in my configuration.nix home.nix accordingly.

Now: a module file added to a folder. That's it.

And more awesome is that I can place both a nixos module and home module in the same file to have aspects together🔥 much more benefits

It's worth doing things this way

#nix #nixos #dendriticpattern #config #management #flakeparts

So, I gave #devenv a try.

I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
So, yeah, I'll keep my #flake for now.
At work and at home.

CC @Ilygad

So, I gave #devenv a try.

I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
So, yeah, I'll keep my #flake for now.
At work and at home.

CC @Ilygad

So, I gave #devenv a try.

I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
So, yeah, I'll keep my #flake for now.
At work and at home.

CC @Ilygad

So, I gave #devenv a try.

I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
So, yeah, I'll keep my #flake for now.
At work and at home.

CC @Ilygad

So, I gave #devenv a try.

I'm used to work with #nix #flakes but I have to admin the devenv.nix file is less cluttered which lead to a better UX. But this comes at the cost of an extra devenv.yaml file. Why not, not a fan, but it works.

But, while #devenv configs are composable locally, they can't import a remote config as #flake does.

Also, `devenv shell` breaks my #tmux / #nvim setup where my #flake works like a charm.
So, yeah, I'll keep my #flake for now.
At work and at home.

CC @Ilygad

#DNSCryptProxy2
#nixos #flake #part example (yes, made with Claude Code) made to see how many hoops are needed to be jumped through to not even get remotely close to the privacy that #reticulum provides over #nomadnet
Reticulum is remarkable as compared with the info leaky internet infrastructure we use daily. https://github.com/DNSCrypt/dnscrypt-proxy/discussions/3246

#dnsencryption #DoT #DoH #DNS

#DNSCryptProxy2
#nixos #flake #part example (yes, made with Claude Code) made to see how many hoops are needed to be jumped through to not even get remotely close to the privacy that #reticulum provides over #nomadnet
Reticulum is remarkable as compared with the info leaky internet infrastructure we use daily. https://github.com/DNSCrypt/dnscrypt-proxy/discussions/3246

#dnsencryption #DoT #DoH #DNS

#DNSCryptProxy2
#nixos #flake #part example (yes, made with Claude Code) made to see how many hoops are needed to be jumped through to not even get remotely close to the privacy that #reticulum provides over #nomadnet
Reticulum is remarkable as compared with the info leaky internet infrastructure we use daily. https://github.com/DNSCrypt/dnscrypt-proxy/discussions/3246

#dnsencryption #DoT #DoH #DNS

#DNSCryptProxy2
#nixos #flake #part example (yes, made with Claude Code) made to see how many hoops are needed to be jumped through to not even get remotely close to the privacy that #reticulum provides over #nomadnet
Reticulum is remarkable as compared with the info leaky internet infrastructure we use daily. https://github.com/DNSCrypt/dnscrypt-proxy/discussions/3246

#dnsencryption #DoT #DoH #DNS

#DNSCryptProxy2
#nixos #flake #part example (yes, made with Claude Code) made to see how many hoops are needed to be jumped through to not even get remotely close to the privacy that #reticulum provides over #nomadnet
Reticulum is remarkable as compared with the info leaky internet infrastructure we use daily. https://github.com/DNSCrypt/dnscrypt-proxy/discussions/3246

#dnsencryption #DoT #DoH #DNS

see post above:
1) repo of a #nixos #flake with #reticulum tools
2) install reticulum >= 1.3.4 run it with e.g. rnsd -v
3) install #Nomadnet / #meshchatx
4) rns://2348f5d47af0253e773334ed288adae9/public/reticulum_nixos_flake_rngit_mirror
5) 8331ef3af688e4153234a5910608dc30
6) [interfaces]
[[adingbatponder-repos]]
type = TCPClientInterface
interface_enabled = true
target_host = repoducible.net
target_port = 57001
name = adingbatponder-repos
2/3

see post above:
1) repo of a #nixos #flake with #reticulum tools
2) install reticulum >= 1.3.4 run it with e.g. rnsd -v
3) install #Nomadnet / #meshchatx
4) rns://2348f5d47af0253e773334ed288adae9/public/reticulum_nixos_flake_rngit_mirror
5) 8331ef3af688e4153234a5910608dc30
6) [interfaces]
[[adingbatponder-repos]]
type = TCPClientInterface
interface_enabled = true
target_host = repoducible.net
target_port = 57001
name = adingbatponder-repos
2/3

see post above:
1) repo of a #nixos #flake with #reticulum tools
2) install reticulum >= 1.3.4 run it with e.g. rnsd -v
3) install #Nomadnet / #meshchatx
4) rns://2348f5d47af0253e773334ed288adae9/public/reticulum_nixos_flake_rngit_mirror
5) 8331ef3af688e4153234a5910608dc30
6) [interfaces]
[[adingbatponder-repos]]
type = TCPClientInterface
interface_enabled = true
target_host = repoducible.net
target_port = 57001
name = adingbatponder-repos
2/3

see post above:
1) repo of a #nixos #flake with #reticulum tools
2) install reticulum >= 1.3.4 run it with e.g. rnsd -v
3) install #Nomadnet / #meshchatx
4) rns://2348f5d47af0253e773334ed288adae9/public/reticulum_nixos_flake_rngit_mirror
5) 8331ef3af688e4153234a5910608dc30
6) [interfaces]
[[adingbatponder-repos]]
type = TCPClientInterface
interface_enabled = true
target_host = repoducible.net
target_port = 57001
name = adingbatponder-repos
2/3

see post above:
1) repo of a #nixos #flake with #reticulum tools
2) install reticulum >= 1.3.4 run it with e.g. rnsd -v
3) install #Nomadnet / #meshchatx
4) rns://2348f5d47af0253e773334ed288adae9/public/reticulum_nixos_flake_rngit_mirror
5) 8331ef3af688e4153234a5910608dc30
6) [interfaces]
[[adingbatponder-repos]]
type = TCPClientInterface
interface_enabled = true
target_host = repoducible.net
target_port = 57001
name = adingbatponder-repos
2/3

@Pol Thanks. Yes, it should ALL be upstream derivations but the hate campaign against AI generated PRs is so bad I do not do it & make it all local. The flake uses 'parts' so you can pull in just the part/s you want: very handy so you do not need the whole flake & can test before maybe importing/harvesting the nix code The readme is not up to date, sorry. As you can see from the number of commits, even with Claude Code doing the heavy lifting, it is a very long term project to make my #flake.

@Pol Thanks. Yes, it should ALL be upstream derivations but the hate campaign against AI generated PRs is so bad I do not do it & make it all local. The flake uses 'parts' so you can pull in just the part/s you want: very handy so you do not need the whole flake & can test before maybe importing/harvesting the nix code The readme is not up to date, sorry. As you can see from the number of commits, even with Claude Code doing the heavy lifting, it is a very long term project to make my #flake.

@Pol Thanks. Yes, it should ALL be upstream derivations but the hate campaign against AI generated PRs is so bad I do not do it & make it all local. The flake uses 'parts' so you can pull in just the part/s you want: very handy so you do not need the whole flake & can test before maybe importing/harvesting the nix code The readme is not up to date, sorry. As you can see from the number of commits, even with Claude Code doing the heavy lifting, it is a very long term project to make my #flake.

@Pol Thanks. Yes, it should ALL be upstream derivations but the hate campaign against AI generated PRs is so bad I do not do it & make it all local. The flake uses 'parts' so you can pull in just the part/s you want: very handy so you do not need the whole flake & can test before maybe importing/harvesting the nix code The readme is not up to date, sorry. As you can see from the number of commits, even with Claude Code doing the heavy lifting, it is a very long term project to make my #flake.

@Pol Thanks. Yes, it should ALL be upstream derivations but the hate campaign against AI generated PRs is so bad I do not do it & make it all local. The flake uses 'parts' so you can pull in just the part/s you want: very handy so you do not need the whole flake & can test before maybe importing/harvesting the nix code The readme is not up to date, sorry. As you can see from the number of commits, even with Claude Code doing the heavy lifting, it is a very long term project to make my #flake.

Using a repo like codeberg and #git for managing a #flake for #nixos that applies for all multiple machines of a fleet each, having their own git branch, using the .#<machine_of_fleet> is really hard. Does anyone do this too? Why is it so hard? For example I have stopped using #checkout as a command because it makes no sense to me and leads to confusion, and use switch and restore. Also I have made a mental note not to refer to "main" in any operation other than the one master machine. Tips?

Using a repo like codeberg and #git for managing a #flake for #nixos that applies for all multiple machines of a fleet each, having their own git branch, using the .#<machine_of_fleet> is really hard. Does anyone do this too? Why is it so hard? For example I have stopped using #checkout as a command because it makes no sense to me and leads to confusion, and use switch and restore. Also I have made a mental note not to refer to "main" in any operation other than the one master machine. Tips?

Using a repo like codeberg and #git for managing a #flake for #nixos that applies for all multiple machines of a fleet each, having their own git branch, using the .#<machine_of_fleet> is really hard. Does anyone do this too? Why is it so hard? For example I have stopped using #checkout as a command because it makes no sense to me and leads to confusion, and use switch and restore. Also I have made a mental note not to refer to "main" in any operation other than the one master machine. Tips?

Using a repo like codeberg and #git for managing a #flake for #nixos that applies for all multiple machines of a fleet each, having their own git branch, using the .#<machine_of_fleet> is really hard. Does anyone do this too? Why is it so hard? For example I have stopped using #checkout as a command because it makes no sense to me and leads to confusion, and use switch and restore. Also I have made a mental note not to refer to "main" in any operation other than the one master machine. Tips?

Using a repo like codeberg and #git for managing a #flake for #nixos that applies for all multiple machines of a fleet each, having their own git branch, using the .#<machine_of_fleet> is really hard. Does anyone do this too? Why is it so hard? For example I have stopped using #checkout as a command because it makes no sense to me and leads to confusion, and use switch and restore. Also I have made a mental note not to refer to "main" in any operation other than the one master machine. Tips?

https://www.wacoca.com/media/640079/ 大阪・南堀江のレコード＆CDショップ
「FLAKE RECORDS」の20周年記念
イベントの開催が決定！ – NEWS | ぴあ関西版WEB #20周年 #DAWA #FLAKE #FLAKERECORDS #music #pia #ticket #チケット #ぴあ #ぴあ関西版WEB #ブレイク #フレイクレコード #レコード屋 #南堀江 #関西 #音楽

https://www.wacoca.com/media/640079/ 大阪・南堀江のレコード＆CDショップ
「FLAKE RECORDS」の20周年記念
イベントの開催が決定！ – NEWS | ぴあ関西版WEB #20周年 #DAWA #FLAKE #FLAKERECORDS #music #pia #ticket #チケット #ぴあ #ぴあ関西版WEB #ブレイク #フレイクレコード #レコード屋 #南堀江 #関西 #音楽

https://www.wacoca.com/media/640079/ 大阪・南堀江のレコード＆CDショップ
「FLAKE RECORDS」の20周年記念
イベントの開催が決定！ – NEWS | ぴあ関西版WEB #20周年 #DAWA #FLAKE #FLAKERECORDS #music #pia #ticket #チケット #ぴあ #ぴあ関西版WEB #ブレイク #フレイクレコード #レコード屋 #南堀江 #関西 #音楽