<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nixos on Nekomangini blog</title><link>https://nekomangini.github.io/tags/nixos/</link><description>Recent content in Nixos on Nekomangini blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 10 Nov 2026 13:27:11 +0800</lastBuildDate><atom:link href="https://nekomangini.github.io/tags/nixos/index.xml" rel="self" type="application/rss+xml"/><item><title>Fixing Hyprland Black Screen on NixOS With an NVIDIA GPU</title><link>https://nekomangini.github.io/post/fixing-hyprland-black-screen-on-nixos-with-an-nvidia-gpu/</link><pubDate>Tue, 10 Nov 2026 13:27:11 +0800</pubDate><guid>https://nekomangini.github.io/post/fixing-hyprland-black-screen-on-nixos-with-an-nvidia-gpu/</guid><description>&lt;p&gt;I wanted to move my NixOS desktop to Hyprland with a Lua config and the Noctalia shell. Logging in gave me a black screen and nothing else. This post is the path I took to fix it, including the dead ends, because the dead ends are where most of the learning happened.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Setup:&lt;/strong&gt; NixOS 26.05, Hyprland 0.55.2, Home Manager as a NixOS module, GTX 1050 Ti, three monitors, and a flake-based dotfiles repo.&lt;/p&gt;</description></item><item><title>Setting Up KDE Connect on NixOS</title><link>https://nekomangini.github.io/post/setting-up-kdeconnect-on-nixos/</link><pubDate>Tue, 02 Jun 2026 17:55:03 +0800</pubDate><guid>https://nekomangini.github.io/post/setting-up-kdeconnect-on-nixos/</guid><description>&lt;p&gt;No matter what desktop environment or window manager I use, KDE Connect is an absolute necessity. Clipboard sharing, receiving phone notifications on my desktop, and using my phone as an emergency trackpad are features I simply cannot live without.&lt;/p&gt;&#10;&lt;p&gt;But as with most things, setting up network-dependent services on NixOS requires a bit of planning. You can&amp;rsquo;t just install the package and expect device discovery to work out of the box—our system firewall has other plans.&lt;/p&gt;</description></item><item><title>Managing Secrets on NixOS: My Journey with Agenix</title><link>https://nekomangini.github.io/post/managing-secrets-on-nixos/</link><pubDate>Fri, 08 May 2026 12:07:22 +0800</pubDate><guid>https://nekomangini.github.io/post/managing-secrets-on-nixos/</guid><description>&lt;p&gt;As my NixOS configuration grows, so does the need to handle sensitive data securely. I’ve recently started using &lt;strong&gt;Agenix&lt;/strong&gt; to manage secrets, specifically to hide project folder paths.&lt;/p&gt;&#10;&lt;p&gt;The transition hasn&amp;rsquo;t been without its hurdles, particularly setting up Agenix as a noob.&lt;/p&gt;&#10;&lt;h2 id="the-challenge-installing-agenix"&gt;The Challenge: Installing Agenix&lt;/h2&gt;&#10;&lt;p&gt;As I continue to &amp;ldquo;rice&amp;rdquo; my system and automate my workflows, I’ve hit a common roadblock: how to handle sensitive data without leaking it to my public GitHub repository. My latest challenge involves using &lt;strong&gt;Agenix&lt;/strong&gt; to hide project folder paths for testing purposes.&lt;/p&gt;</description></item><item><title>Setting Up Helix for Vue.js Development on NixOS</title><link>https://nekomangini.github.io/post/setting-up-helix-for-vuejs-development-on-nixos/</link><pubDate>Thu, 30 Apr 2026 22:44:29 +0800</pubDate><guid>https://nekomangini.github.io/post/setting-up-helix-for-vuejs-development-on-nixos/</guid><description>&lt;p&gt;Following my move to NixOS and my shift toward &lt;strong&gt;Helix&lt;/strong&gt; as my primary editor, I recently tackled the challenge of setting up a robust Vue.js development environment. While the &lt;a href="https://github.com/helix-editor/helix/wiki/Language-Server-Configurations#vue"&gt;Helix Wiki&lt;/a&gt; provides a great starting point, NixOS adds a unique layer of complexity when it comes to locating plugins in the &lt;code&gt;/nix/store&lt;/code&gt;.&lt;/p&gt;&#10;&lt;p&gt;Here is how I got it working.&lt;/p&gt;&#10;&lt;h2 id="the-toolchain"&gt;The Toolchain&lt;/h2&gt;&#10;&lt;p&gt;First, we need to ensure the necessary language servers and formatters are available in the environment. I use Home Manager to manage these packages:&lt;/p&gt;</description></item><item><title>My Descent Into the NixOS Rabbithole: A Retrospective</title><link>https://nekomangini.github.io/post/my-descent-into-the-nixos-rabbithole/</link><pubDate>Fri, 24 Apr 2026 23:14:26 +0800</pubDate><guid>https://nekomangini.github.io/post/my-descent-into-the-nixos-rabbithole/</guid><description>&lt;p&gt;I’ve been using NixOS since October 2025. I’ll be honest: I’m still very much a beginner, so if you see me doing something &amp;ldquo;the wrong way,&amp;rdquo; I am more than happy to be corrected! To keep my head above water, I’ve been living by the &lt;a href="https://nixos-and-flakes.thiscute.world/nixos-with-flakes/get-started-with-nixos"&gt;NixOS &amp;amp; Flakes Book&lt;/a&gt;.&lt;/p&gt;&#10;&lt;h2 id="the-config-migration"&gt;The Config Migration&lt;/h2&gt;&#10;&lt;p&gt;At first, I kept my NixOS config in the standard &lt;code&gt;/etc/nixos/&lt;/code&gt; directory. But as a developer, I wanted to keep it in a GitHub repository, and managing a Git repo inside &lt;code&gt;/etc&lt;/code&gt; is&amp;hellip; a bit of a headache.&lt;/p&gt;</description></item><item><title>From openSUSE to NixOS: A Migration Story</title><link>https://nekomangini.github.io/post/from-opensuse-to-nixos/</link><pubDate>Tue, 03 Mar 2026 01:42:10 +0800</pubDate><guid>https://nekomangini.github.io/post/from-opensuse-to-nixos/</guid><description>&lt;p&gt;The last time I updated this blog was back in September 2024. If you’ve been wondering where I disappeared to, the answer is simple: I fell deep down the Neovim and Emacs rabbit holes. What started as &amp;ldquo;just a few tweaks&amp;rdquo; to my dotfiles turned into a month-long obsession with perfecting my development environment. Since then, my setup has evolved even further—I&amp;rsquo;ve actually switched from Neovim to &lt;strong&gt;Helix&lt;/strong&gt; for my main editing, while still keeping Emacs around specifically for the power of &lt;strong&gt;Org-mode&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>