Sender | Message | Time |
---|---|---|
27 May 2025 | ||
14:42:36 | ||
15:45:38 | ||
19:35:54 | ||
If I have a flake that specifies more than one system, and I want to share a string (eg ssh key, ip address, etc) between configs for multiple systems, is the best thing to create a shared module with something like options.foo = { sharedString = lib.mkOption { ... }; }; , and then refer to config.foo.sharedString ? I keep second guessing this because I'm specifying what is in my case a constant as a configurable option. | 19:43:06 | |
an option is useful if you are going to override the value when you call the module
And you import the keys in your config : | 20:56:10 | |
* an option is useful if you are going to override the value when you call the module
And you import the keys in your config : | 20:57:42 | |
28 May 2025 | ||
03:02:01 | ||
29 May 2025 | ||
12:29:23 | ||
12:33:14 | ||
21:19:00 | ||
30 May 2025 | ||
00:39:16 | ||
00:39:51 | ||
12:14:32 | ||
19:53:25 | ||
19:54:41 | ||
I just upgraded my server to 25.05 and there I have some containers, one for matrix-synapse, one for xandikos (a webdav server) and one for a nginx proxy which proxies matrix-synapse and xandikos. now since the update the nginx container fails to start, the log is full with "A start job is running for Renew ACME certificate for..." when I stop the acme-setup.service on the nginx container before the container fails due to timeout everything seems fine so far... Is this a known issue? What can I do to fix this? | 23:59:09 | |
31 May 2025 | ||
I forgot to mention, when I remove the vhost for matrix but keep the one for xandikos, everything works fine as expected. | 00:00:30 | |
if anyone is curious what is going on here, I was running a VM with 1GB of RAM and no swap and it seems like it was running out of memory nixos-rebuild was just dying without error .. adding a swapfile fixed it | 10:48:55 | |
* if anyone is curious what is going on here, I was running a VM with 1GB of RAM and no swap and it seems like it was running out of memory nixos-rebuild was just dying without error .. adding a swapfile fixed it I am not sure if better error message is even possible in this scenario ... | 10:49:30 | |
Yeah | 10:49:32 | |
It's not really possible | 10:49:36 | |
But you should see an OOM kill in dmesg | 10:49:40 | |
A nixpkgs eval needs ~3GB of RAM | 10:49:44 | |
13:23:40 | ||
17:10:57 | ||
Not sure if this is possible with DO but my own recipe for quite some time had been to basically boot whichever nix included thing and then incrementally (possibly after zero steps, depending if you kexec etc) copying parts of a nix store from an another machine with many GBs of RAM to that lower spec VM of mine. | 17:30:26 | |
If you decide you never need to eval on the target machine itself you can go with quite a low RAM | 17:31:10 | |
In any other case I personally recommend > 4 Gb due the eval, as K900 mentioned | 17:32:05 | |
20:52:01 | ||
21:00:11 |