| 15 Jun 2024 |
 Todd Thompson | ok, will comment out for now | 08:50:33 |
 K900 | The only way to restart it properly is to wsl --shutdown externallyn | 08:50:54 |
| K900 | * The only way to restart it properly is to
wsl --shutdown externallynl | 08:51:00 |
| K900 | * The only way to restart it properly is to
wsl --shutdown externally | 08:51:04 |
| K900 | Because that will also clear the state tracking on the Windows side | 08:51:20 |
| K900 | And the "system" distro | 08:51:34 |
| Todd Thompson | everything seems to be working now, thanks | 08:55:01 |
| Todd Thompson | my goal is to use nixos-wsl for local development and then nixos or ubuntu+nix-shell for VPS for prototype/staging. is the "nixos" way to do things to always use shell envs for each app/service or should I globally install some devops tools as well | 08:59:30 |
| Todd Thompson | I'd like to follow the ethos of nixos as much as possible but not sure about the 3 different use cases | 09:00:47 |
| K900 | Generally yes, do one shell per project | 09:21:01 |
| Todd Thompson | In reply to @k900:0upti.me
Generally yes, do one shell per project thanks | 09:30:40 |
| Todd Thompson | I'm following https://zero-to-nix.com/ hope it's a good starting place | 09:31:39 |
 nzbr (they/it) | In reply to@k900:0upti.me
nzbr (they/it) can you do the thing? I had been gone for the last week, sorry. I'll see if there's anything missing before that | 16:23:10 |
| nzbr (they/it) | If I haven't missed anything urgent, we can probably have a new release once this one is merged: https://github.com/nix-community/NixOS-WSL/pull/496 | 17:36:28 |
| 16 Jun 2024 |
| K900 | In reply to @nzbr:nzbr.de
If I haven't missed anything urgent, we can probably have a new release once this one is merged: https://github.com/nix-community/NixOS-WSL/pull/496 Does that actually happen? | 05:36:05 |
| K900 | (and how?) | 05:36:07 |
 andreas_dev | I'm not sure if that's due to a crash, but I have had it happen that a failed logger initialization causes NixOS WSL to break, as in you can't enter the shell (but luckily you can with the recovery shell) | 07:43:39 |
| andreas_dev | In reply to @nzbr:nzbr.de
the copying happens in an activation script, so it should happen every time the distro boots or you switch to a new generation. Therefore, if you have a recent-enough version of the nixos-wsl modules the launchers should be copied from your user profile as well. You can check if they are present in /usr/share/applications. I don't know with what logic wsl will re-scan those directories though, or if there is any way of triggering a scan manually Only the NixOS manual and fish shell appears in there | 09:05:05 |
| andreas_dev | 
Download 1000052272.jpg | 09:39:11 |
| andreas_dev | I wanted to test a theory, however this error occurred: https://pastebin.com/dxNjuJnZ
This is my hardware-configuration in the image above (pastebin cloudflare blocked me so I couldn't make another one | 09:39:28 |
| andreas_dev | Apparently the nixos-rebuild did work, and my theory has been proven thus far: adding programs to the user in configuration.nix works and shows in the menu, but when performing this through home-manager, it won't be copied to /usr/share/applications and show in the menu. Should I file a bug report for this? | 09:40:49 |
| K900 | It's not really something we can fix | 10:26:34 |
| K900 | Unless | 10:26:36 |
| K900 | Unless we do something really cursed | 10:26:42 |
| andreas_dev | In reply to @k900:0upti.me
Unless we do something really cursed Now I'm intrigued.. | 10:29:03 |
| K900 | We can copy the shortcuts from a systemd user service | 10:29:21 |
| K900 | Instead of the activation script | 10:29:28 |
| K900 | Then it'll inherit the user's XDG_DATA_DIRS | 10:29:35 |
| K900 | And we can chmod /usr/share/applications to your user | 10:30:05 |
| K900 | So it actually works | 10:30:09 |
