#homemanager — Public Fediverse posts

@TimothyRoes I'm a #vim'er, and yes I do that on the go. #pass for passwords, #ssh to check or fix my servers, etc.

Later I also want to make #homeManager modules for #SailfishOS settings, especially those that aren't stored in a SFOS backup. Endgame would be to distribute SFOS apps via #nix, which would be awesome!

@TimothyRoes I'm a #vim'er, and yes I do that on the go. #pass for passwords, #ssh to check or fix my servers, etc.

Later I also want to make #homeManager modules for #SailfishOS settings, especially those that aren't stored in a SFOS backup. Endgame would be to distribute SFOS apps via #nix, which would be awesome!

@TimothyRoes I'm a #vim'er, and yes I do that on the go. #pass for passwords, #ssh to check or fix my servers, etc.

Later I also want to make #homeManager modules for #SailfishOS settings, especially those that aren't stored in a SFOS backup. Endgame would be to distribute SFOS apps via #nix, which would be awesome!

@TimothyRoes I'm a #vim'er, and yes I do that on the go. #pass for passwords, #ssh to check or fix my servers, etc.

Later I also want to make #homeManager modules for #SailfishOS settings, especially those that aren't stored in a SFOS backup. Endgame would be to distribute SFOS apps via #nix, which would be awesome!

@TimothyRoes I'm a #vim'er, and yes I do that on the go. #pass for passwords, #ssh to check or fix my servers, etc.

Later I also want to make #homeManager modules for #SailfishOS settings, especially those that aren't stored in a SFOS backup. Endgame would be to distribute SFOS apps via #nix, which would be awesome!

:nixos: #nix on :sailfishos: #SailfishOS on the new #JollaPhone 😎

I have finally begun sorting my user config into #homeManager in a way that I can directly reuse on my phone. Really nice having your exact, comfy shell environment right and natively in your pocket.

:nixos: #nix on :sailfishos: #SailfishOS on the new #JollaPhone 😎

I have finally begun sorting my user config into #homeManager in a way that I can directly reuse on my phone. Really nice having your exact, comfy shell environment right and natively in your pocket.

:nixos: #nix on :sailfishos: #SailfishOS on the new #JollaPhone 😎

I have finally begun sorting my user config into #homeManager in a way that I can directly reuse on my phone. Really nice having your exact, comfy shell environment right and natively in your pocket.

:nixos: #nix on :sailfishos: #SailfishOS on the new #JollaPhone 😎

I have finally begun sorting my user config into #homeManager in a way that I can directly reuse on my phone. Really nice having your exact, comfy shell environment right and natively in your pocket.

:nixos: #nix on :sailfishos: #SailfishOS on the new #JollaPhone 😎

I have finally begun sorting my user config into #homeManager in a way that I can directly reuse on my phone. Really nice having your exact, comfy shell environment right and natively in your pocket.

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. 😎

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. 😎

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. 😎

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. 😎

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. 😎

Why does github:sodiboo/niri-flake exist?

https://piefed.blahaj.zone/c/nix/p/922160/why-does-github-sodiboo-niri-flake-exist

Why does github:sodiboo/niri-flake exist?

https://piefed.blahaj.zone/c/nix/p/922160/why-does-github-sodiboo-niri-flake-exist

Why does github:sodiboo/niri-flake exist?

https://piefed.blahaj.zone/c/nix/p/922160/why-does-github-sodiboo-niri-flake-exist

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](https://github.com/nix-community/home-manager/issues/9446). 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

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](https://github.com/nix-community/home-manager/issues/9446). 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

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](https://github.com/nix-community/home-manager/issues/9446). 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

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](https://github.com/nix-community/home-manager/issues/9446). 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

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](https://github.com/nix-community/home-manager/issues/9446). 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

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

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

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

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

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

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

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

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

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

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

Shout out to #nixos and #homemanager 🎉

These two together are just amazing.

Shout out to #nixos and #homemanager 🎉

These two together are just amazing.

Shout out to #nixos and #homemanager 🎉

These two together are just amazing.

Shout out to #nixos and #homemanager 🎉

These two together are just amazing.

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

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

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

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

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

'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

'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

'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

'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

'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

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

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

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

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

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

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

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

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

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

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

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

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

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