home.social

#homemanager — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #homemanager, aggregated by home.social.

fetched live
  1. You know... I been using #nix #homemanager for weeks and it only now occurred to me, all my files are to a derivation. 😆

    Tried to modify by hand. 😅

    On the plus side, it means I been truly following all edits are on home manager bit for it to take this long. 😎

  2. You know... I been using for weeks and it only now occurred to me, all my files are to a derivation. 😆

    Tried to modify by hand. 😅

    On the plus side, it means I been truly following all edits are on home manager bit for it to take this long. 😎

  3. You know... I been using #nix #homemanager for weeks and it only now occurred to me, all my files are to a derivation. 😆

    Tried to modify by hand. 😅

    On the plus side, it means I been truly following all edits are on home manager bit for it to take this long. 😎

  4. You know... I been using #nix #homemanager for weeks and it only now occurred to me, all my files are to a derivation. 😆

    Tried to modify by hand. 😅

    On the plus side, it means I been truly following all edits are on home manager bit for it to take this long. 😎

  5. You know... I been using #nix #homemanager for weeks and it only now occurred to me, all my files are to a derivation. 😆

    Tried to modify by hand. 😅

    On the plus side, it means I been truly following all edits are on home manager bit for it to take this long. 😎

  6. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```
    #NixOS #Nix #HomeManager

  7. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```
    #NixOS #Nix #HomeManager

  8. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```
    #NixOS #Nix #HomeManager

  9. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```
    #NixOS #Nix #HomeManager

  10. The generated plugin that delivers managed MCP and LSP configuration to Claude Code now uses the manifest name `hm` (previously `claude-code-home-manager`). Claude Code derives the MCP tool namespace from the plugin manifest, so this shortens every plugin-loaded MCP tool prefix to `mcp__plugin_hm_<server>__<tool>`. See [issue #9446](github.com/nix-community/home-). The personal skills directory stays `~/.claude/skills/claude-code-home-manager` unchanged, so it does not collide with user plugins or skills. This is a breaking change. If you allow or deny these tools by name in {file}`<project>/.claude/settings.{, local.}json` or via {option}`programs.claude-code.settings`, update any references from `claude-code-home-manager` to `hm`, for example: ```json { "permissions": { "allow": ["mcp__plugin_hm_github"] } } ```

  11. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.
    #NixOS #Nix #HomeManager

  12. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.
    #NixOS #Nix #HomeManager

  13. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.
    #NixOS #Nix #HomeManager

  14. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.
    #NixOS #Nix #HomeManager

  15. A new module is available: 'programs.crush'. Crush is Charm's coding agent for the terminal. The module installs Crush, writes its JSON configuration, and manages Agent Skills. It can also take MCP servers from the shared 'programs.mcp' module.

  16. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`
    #NixOS #Nix #HomeManager

  17. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`
    #NixOS #Nix #HomeManager

  18. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`
    #NixOS #Nix #HomeManager

  19. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`
    #NixOS #Nix #HomeManager

  20. A new module is available: 'programs.flake-edit', featuring a '.settings' option to generate {file}`$XDG_CONFIG_HOME/flake-edit/config.toml`

  21. Shout out to #nixos and #homemanager 🎉

    These two together are just amazing.

  22. Shout out to #nixos and #homemanager 🎉

    These two together are just amazing.

  23. Shout out to #nixos and #homemanager 🎉

    These two together are just amazing.

  24. Shout out to #nixos and #homemanager 🎉

    These two together are just amazing.

  25. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).
    #NixOS #Nix #HomeManager

  26. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).
    #NixOS #Nix #HomeManager

  27. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).
    #NixOS #Nix #HomeManager

  28. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).
    #NixOS #Nix #HomeManager

  29. A new option is available: 'launchd.agents.<name>.waitForNixStore'. By default, launchd agents are started through a '/bin/sh' wrapper that waits for the Nix store to be mounted, which makes every agent show up as "sh" in System Settings > Login Items & Extensions. When this option is disabled, the agent is instead started through a launcher script named after the agent, so it is displayed under its own name. Note that disabling it means the agent will fail to start if launchd runs it before the Nix store volume is mounted (e.g. early during login when the store volume is encrypted).

  30. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.
    #NixOS #Nix #HomeManager

  31. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.
    #NixOS #Nix #HomeManager

  32. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.
    #NixOS #Nix #HomeManager

  33. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.
    #NixOS #Nix #HomeManager

  34. 'programs.rclone' mounts now support a 'mountType' option that can be set to "nfsmount" to mount remotes via rclone's built-in NFS server and the system NFS client instead of FUSE. On macOS this removes the need for macFUSE and its kernel extension (and the Reduced Security boot policy the extension requires). When "nfsmount" is selected, 'nfs-cache-type = "disk"' is added to the mount's options by default so NFS file handles survive rclone restarts.

  35. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg
    #NixOS #Nix #HomeManager

  36. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg
    #NixOS #Nix #HomeManager

  37. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg
    #NixOS #Nix #HomeManager

  38. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg
    #NixOS #Nix #HomeManager

  39. The config path for 'senpai' on Darwin now defaults to: ~/Library/Application Support/senpai/senpai.scfg

  40. Day 3 :
    ( I'm more eager for this day personally)
    I planned a stall for 2 topics combined:
    ecosystem and Holos.Social . Love to explain curious minds how some projects in the nix ecosystem does things in a way which many wouldn't have thought of. Like , , -wrapper-modules, , , , etc

  41. Day 3 #Stalls:
    ( I'm more eager for this day personally)
    I planned a stall for 2 topics combined:
    #Nix ecosystem and Holos.Social . Love to explain curious minds how some projects in the nix ecosystem does things in a way which many wouldn't have thought of. Like #devenv, #nixos, #nix-wrapper-modules, #nixdockerTools, #homemanager, #nixsystemmanager, etc

    #tossconf #tossconf26 #tamil #foss #ksv236

  42. Day 3 #Stalls:
    ( I'm more eager for this day personally)
    I planned a stall for 2 topics combined:
    #Nix ecosystem and Holos.Social . Love to explain curious minds how some projects in the nix ecosystem does things in a way which many wouldn't have thought of. Like #devenv, #nixos, #nix-wrapper-modules, #nixdockerTools, #homemanager, #nixsystemmanager, etc

    #tossconf #tossconf26 #tamil #foss #ksv236

  43. Day 3 #Stalls:
    ( I'm more eager for this day personally)
    I planned a stall for 2 topics combined:
    #Nix ecosystem and Holos.Social . Love to explain curious minds how some projects in the nix ecosystem does things in a way which many wouldn't have thought of. Like #devenv, #nixos, #nix-wrapper-modules, #nixdockerTools, #homemanager, #nixsystemmanager, etc

    #tossconf #tossconf26 #tamil #foss #ksv236

  44. Day 3 #Stalls:
    ( I'm more eager for this day personally)
    I planned a stall for 2 topics combined:
    #Nix ecosystem and Holos.Social . Love to explain curious minds how some projects in the nix ecosystem does things in a way which many wouldn't have thought of. Like #devenv, #nixos, #nix-wrapper-modules, #nixdockerTools, #homemanager, #nixsystemmanager, etc

    #tossconf #tossconf26 #tamil #foss #ksv236

  45. Home Manager launchd agents now support the `launchd.agents.<name>.domain` option. Agents use the GUI launchd domain by default. Set `launchd.agents.<name>.domain = "user"` for agents that should run without an active graphical login session.
    #NixOS #Nix #HomeManager

  46. Home Manager launchd agents now support the `launchd.agents.<name>.domain` option. Agents use the GUI launchd domain by default. Set `launchd.agents.<name>.domain = "user"` for agents that should run without an active graphical login session.
    #NixOS #Nix #HomeManager

  47. Home Manager launchd agents now support the `launchd.agents.<name>.domain` option. Agents use the GUI launchd domain by default. Set `launchd.agents.<name>.domain = "user"` for agents that should run without an active graphical login session.
    #NixOS #Nix #HomeManager

  48. Home Manager launchd agents now support the `launchd.agents.<name>.domain` option. Agents use the GUI launchd domain by default. Set `launchd.agents.<name>.domain = "user"` for agents that should run without an active graphical login session.
    #NixOS #Nix #HomeManager

  49. Home Manager launchd agents now support the `launchd.agents.<name>.domain` option. Agents use the GUI launchd domain by default. Set `launchd.agents.<name>.domain = "user"` for agents that should run without an active graphical login session.

  50. @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.

    -parts

  51. @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

  52. @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

  53. @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

  54. What are we using for standardizing our directories and file structures for Nix system and home-manager configurations?

    nixpkgs dropping support for x86_64-darwin has finally broken the somewhat unmaintained project I was using.

    Blueprint? numtide.github.io/blueprint/ma

    I hear stuff about this Dendritic pattern but it seems to be more of an approach to roll-your-own and I just wanna drop stuff in and move on github.com/mightyiam/dendritic

    #Nix #NixOS #HomeManager

  55. What are we using for standardizing our directories and file structures for Nix system and home-manager configurations?

    nixpkgs dropping support for x86_64-darwin has finally broken the somewhat unmaintained project I was using.

    Blueprint? numtide.github.io/blueprint/ma

    I hear stuff about this Dendritic pattern but it seems to be more of an approach to roll-your-own and I just wanna drop stuff in and move on github.com/mightyiam/dendritic

    #Nix #NixOS #HomeManager

  56. What are we using for standardizing our directories and file structures for Nix system and home-manager configurations?

    nixpkgs dropping support for x86_64-darwin has finally broken the somewhat unmaintained project I was using.

    Blueprint? numtide.github.io/blueprint/ma

    I hear stuff about this Dendritic pattern but it seems to be more of an approach to roll-your-own and I just wanna drop stuff in and move on github.com/mightyiam/dendritic

    #Nix #NixOS #HomeManager

  57. What are we using for standardizing our directories and file structures for Nix system and home-manager configurations?

    nixpkgs dropping support for x86_64-darwin has finally broken the somewhat unmaintained project I was using.

    Blueprint? numtide.github.io/blueprint/ma

    I hear stuff about this Dendritic pattern but it seems to be more of an approach to roll-your-own and I just wanna drop stuff in and move on github.com/mightyiam/dendritic

    #Nix #NixOS #HomeManager