Some cleanup to the #Caddy #NixOS wiki page, especially documentation on the new plugin support with NixOS 25.05 
wiki.nixos.orgCaddy - NixOS Wiki
Recent searches
Search options
Administered by:
#nixos
51 posts44 participants1 post today
Hello world from #NixOS meetup in #Darmstadt Germany 
ALT
Pünktlich zum heutigen #NixOS Stammtisch weihen wir offiziell unsere neue Wanddekoration ein
ALTGIF
Replied to Elias Probst
Vendor just confirmed: the board is dead, replacements with 32GB memory aren't available at the moment, only a downgrade to 16GB would be possible.
Looks like I'm going for a refund then and will invest in a brand new laptop - a @frameworkcomputer 13 - instead of a refurbished one for the first time in nearly 15 years.
Downside is: will be shipped at some point in May and might not arrive before June and until then, my #NixOS configuration runs on a poor little Raspberry Pi 4B until then 
@nobodyinperson This is the simplest native mail server setup I know on #NixOS https://wiki.nixos.org/wiki/Stalwart
Otherwise you could go with Thunderbird local mail archives (MBOX) similar to Outlook PST archives
wiki.nixos.orgStalwart - NixOS Wiki
#eMail #selfHosting gurus: I am looking for the simplest possible way to host myself a mailbox I can add to my email clients (Thunderbird, phone, etc.) as usual, so I can move mails there to free up space on the 3rd party "real" emails, then back them up separately on my server.
I do not want receiving or sending emails to work. Just an IMAP or whatever box I can shove emails in the face by dragging them in Thunderbird or with a script.
Ideally available in 
#NixOS
@craige @AlexanderMars @ErickaSimone @GrapheneOS I concur. I've had good experiences with #GrapheneOS on Pixel devices for five years and just moved from a #System76 #OryxPro running Pop!_OS to a #FrameWork16 running #NixOS.
Though have had trouble with coverting the System76 laptop to NixOS due to fan drivers always running the fan at 100%, which is unacceptable for a server.
@AlexanderMars @ErickaSimone @GrapheneOS
I'm a second on this. I've been a GrapheneOS user for three years now. By far and away the best and most secure, private experience I've yet to have on a mobile device - and I've tried just about everything, including Linux phones.
I've gone Purism and System76 laptops running #NixOS though (no shade thrown on the Framework gear).
Hey #NixOS
Is there a more preferred secrets manager or method for not putting your nuclear codes into your config files? It's great if there's ten different ways but I'm wondering if there's a most-popular one.
I sorted out the cloudflare tunnel docker thing, but now the token is in the configuration.nix file. Now I'm installing Nextcloud, and it also instructs me to put the admin pw into the config file, and I'm starting to worry my server is gonna glow in the dark from the radioactive bad admin practices...
Maybe I'm over thinking this.
In #NixOS , I want to simply have a job once a day, but only run when a user (any user) is logged in and at the desktop (since part of this job sends a desktop notification)
I was trying to do this with a systemd timer, but that's proving to be super messy having the service wait until someone is logged in.
Is there a better way?
Getting my new desktop in a few days, I am playing with different distributions on my laptop right now to see what fits. I been on Fedora for a long time, and I do love #Fedora but I used to use #Arch might look at it again, but right now I am putting myself out there to try #openSUSE and #Debian again to see what those are like. I know there is a lot of people who might say #NixOS which I have looked at but seems like that could become a bit more complex than I am looking for as just a desktop operating system.
2025, the year I switch from wayland to Xorg.
Why? Because I bought a new screen.
Huh? Well, I don't know either.
Plasma 6 on wayland worked fine with my fullhd-screen. Yesterday, I powered the box down, switched to my new hi(gher)dpi screen, powered it on, got the bios post, boot messages, and a black screen instead of sddm. An hour later I found that sddms wayland support is experimental still, so I switched it to X, and got a black screen when my plasma-wayland session was to start. So, switched to plasma-x11 and everything is fine.
Other compositor (tested sway) are fine. 
Don't know if it's nixos or plasma, I'll probably try a live usb later.
So yeah, it's the year 2025 and I'm on X. Well, could be worse, could be the other X.
Replied to gobbe
#bevy #nixos #rustlang #kate
Here's the bevy rust nixos devshell that worked for me, if you're interested d:
```shell.nix
// stuff before buildinputs
buildInputs = [
cargo rustc rustfmt pre-commit rustPackages.clippy
udev alsa-lib vulkan-loader libudev-zero pkg-config
xorg.libX11 xorg.libXcursor xorg.libXi xorg.libXrandr # To use the x11 feature
libxkbcommon wayland # To use the wayland feature
];
//stuff after buildinputs
```
Replied to gobbe
#kate #rustlang #lsp #nixos
Solved it !
Added a bunch of packages to my nix devshell ( including clippy itself ), but I think adding libudev-zero fixed it.
Why ?
I had tried starting a code analysis from the "code analysis" tab in kate, with the "Clippy (Rust)" option. Got a really long error that in short said that it needed libudev so I added it, and that fixed it.
Cargo now works like expected and only builds what's changed (instead of all of the packages I've installed on top of rust) :P
I've been making supporting the #opensource projects I use a priority in 2025. #NixOS #hyprland #logseq (though that's as much a subscription as a donation these days)
There's so much great work being done by the community, but many of them need money to make it work, and make it worthwhile.