| 9 Apr 2026 |
 monokles | If it is just monitoring for a home setup without the need for metrics, you could also just pipe journald entries of interest to something by writing a small systemd service yourself. For example, I push ssh login events on my systems to private e2ee matrix rooms.
| 10:36:35 |
|  James (setkeh) Griffis joined the room. | 10:44:52 |
 phaer | I just checked because that seemed to be rather high: alloy on my hosts eats between 40 and 65M of RAM. Granted, none of those is suuuper busy with log generation, but the journal of a private rasperry pi shouldn't be either.
Maybe it's specific rules or so? I can at least tell you it does not NEED to use that much RAM if you are otherwise happy with one of them | 15:11:54 |
|  Matthew Rappard joined the room. | 17:51:39 |
| Matthew Rappard | Feel free to loudly tell me it's a bad.
But has anyone got NixOS working on a Google Cloud Workstations
https://cloud.google.com/workstations | 17:52:19 |
 blades | In reply to @mrappard:matrix.org
Feel free to loudly tell me it's a bad.
But has anyone got NixOS working on a Google Cloud Workstations
https://cloud.google.com/workstations Not nixos, but our internal equivalent uses a lot of the same tooling and it was trivial to install nix (via determinate installer) and devenv into the the workspaces.
(I would have installed nixos, but the infra team in charge begged me not to add more distros that they’d have to test.) | 18:44:41 |
| 15 Mar 2024 |
|  spacesbot - keeps a log of public NixOS channels joined the room. | 04:06:36 |
| spacesbot - keeps a log of public NixOS channels | 05:00:13 |
| 18 Mar 2024 |
|  darkwater4213 joined the room. | 00:40:59 |
|  steveej joined the room. | 09:45:48 |
|  Infinidoge joined the room. | 18:50:06 |
| 19 Mar 2024 |
|  NixOS Moderation Botchanged room power levels. | 00:29:56 |
|  Steve Mayer joined the room. | 22:09:47 |
| 21 Mar 2024 |
| NixOS Moderation Botchanged room power levels. | 18:02:53 |
| 22 Mar 2024 |
|  michael@a5ap.net joined the room. | 14:18:46 |
| 23 Mar 2024 |
|  Federico Damián Schonborn joined the room. | 00:37:30 |
|  Charles ⚡️ joined the room. | 03:53:09 |
|  xenos76 joined the room. | 14:22:52 |
|  abyxcos joined the room. | 17:36:08 |
| 24 Mar 2024 |
|  skorpy 🏳️⚧️ joined the room. | 09:36:25 |
 raitobezarius | https://www.ivanomalavolta.com/files/papers/ICSOC_2023.pdf | 15:00:38 |
|  conr joined the room. | 19:36:46 |
| conr | what will the /etc/crypttab look like to mount them? | 19:37:07 |
 ElvishJerricco | conr: man crypttab describes the syntax | 19:37:31 |
| ElvishJerricco | and "mount" isn't the right term; it just unlocks the luks devices | 19:37:51 |
| conr | just one liners with line breaks? | 19:38:26 |
| ElvishJerricco | yep | 19:38:41 |
| ElvishJerricco | it's like /etc/fstab but for encrypted devices instead of for file systems | 19:38:54 |
| conr | ElvishJerricco: I created the pool already but do i need to destroy and, encrpyt the raw disks, then do the zpool create ... with the luks devices? | 19:52:15 |
| conr | * ElvishJerricco: I created the zpool already but do i need to destroy and, encrpyt the raw disks, then do the zpool create ... with the luks devices? | 19:53:29 |
