| 7 Apr 2022 |
 @grahamc:nixos.org | But I don’t want to do all that work if it doesn’t look like a good approach | 11:48:38 |
 ajs124 | I'm not sure I'm qualified judge that, tbh | 11:53:21 |
| @grahamc:nixos.org | well, I merged & deployed it. We can revert it if we need to :P | 20:31:01 |
| @grahamc:nixos.org | ~unreleased software~ | 20:31:06 |
| 8 Apr 2022 |
|  bitmapper joined the room. | 01:04:03 |
| bitmapper | is there any way to make hydra inaccessible except when you are logged in? | 01:11:52 |
| bitmapper | like, so the projects aren't publicly visible | 05:07:08 |
| ajs124 | I think hidden jobsets work like that? But those are not very convenient.
Why can't you just put it behind basic auth? | 08:45:27 |
 hexa | or on a VPN | 11:47:44 |
|  tilpner joined the room. | 20:15:37 |
| tilpner | In reply to @bitmapper:amber.tel
like, so the projects aren't publicly visible I have private = true in my config, and it seems to return a 403 unless signed in for every page | 20:24:38 |
| tilpner | Hi ma27, which plugin did you write https://github.com/NixOS/hydra/pull/922 for? You mention e.g. the gitea status plugin, which (as you pointed out) requires a git input, and then to set gitea_status_repo to the name of that input. Is there some hidden flake input, or is that still incompatible with the flakes mode? | 20:29:06 |
 cransom | huh. i've had mine behind basic auth. perhaps i'm going to migrate it over to private. | 20:59:17 |
| tilpner | cransom: basic auth is simpler to get right, than expecting every application to implement their own access control. I'm not overly reliant on hydra's private mode, as it's only served on a private network anyway (or supposed to be, thus the precaution) | 21:01:13 |
| cransom | most of the pain of basic auth is that password managers (at least the ones i've got) aren't basic auth friendly. | 21:04:21 |
| cransom | tried it in dev now, seems ok. it's low stakes for me to roll it out anyway. | 21:06:10 |
| tilpner | yeah, that's fair :) | 21:06:32 |
 ma27 | In reply to @tilpner:tx0.co
I have private = true in my config, and it seems to return a 403 unless signed in for every page I implemented https://github.com/NixOS/hydra/pull/919 for private projects a while ago | 21:09:24 |
| ma27 | In reply to @tilpner:tx0.co
Hi ma27, which plugin did you write https://github.com/NixOS/hydra/pull/922 for? You mention e.g. the gitea status plugin, which (as you pointed out) requires a git input, and then to set gitea_status_repo to the name of that input. Is there some hidden flake input, or is that still incompatible with the flakes mode? no it isn't. I add a second git input, so each repo is cloned twice. Dirty, but it gets the job done for now. | 21:10:14 |
| tilpner | ohh! I assumed "Jobset Inputs don't take any effect for flakes" meant that any non-String inputs would just be ignored, I'll try adding a second input for now | 21:11:51 |
| ma27 | see for instance https://hydra.ist.nicht-so.sexy/jobset/nvim-nix/master#tabs-configuration and the inputs configured for that jobset in https://hydra.ist.nicht-so.sexy/eval/699#tabs-inputs. | 21:14:00 |
| tilpner | In reply to @ma27:nicht-so.sexy
see for instance https://hydra.ist.nicht-so.sexy/jobset/nvim-nix/master#tabs-configuration and the inputs configured for that jobset in https://hydra.ist.nicht-so.sexy/eval/699#tabs-inputs. thank you for the reference! I can't seem to make hydra report any status yet, but that could be a misconfigured gitea token/user account, or these evaluation errors... | 21:41:54 |
| 9 Apr 2022 |
| tilpner | Are there any workarounds for automatic updates in flake mode, or does everyone with that requirement still use legacy mode and flake-compat? | 13:04:24 |
 Artturin | In reply to @tilpner:tx0.co
Are there any workarounds for automatic updates in flake mode, or does everyone with that requirement still use legacy mode and flake-compat? automatic updates of what? | 13:10:55 |
 Rick (Mindavi) | NixOS, I assume | 13:24:49 |
| tilpner | In reply to @artturin:matrix.org
automatic updates of what? Automatic updates of flake inputs | 13:37:17 |
 Amanda (she/her) | I use a systemd timer on my homelab that does a regular clone, nix flake update commit and push | 13:38:31 |
| tilpner | * Automatic updates of flake inputs, e.g. the source code of an application, or even nixpkgs inputs for a nixosConfiguration flake | 13:40:38 |
| Amanda (she/her) | If your useing GitHub you can probably make GitHub actions do it | 13:42:00 |
| Amanda (she/her) | But I want to self host my stuff so it's just a systemd timer that updates the flake lock every Wednesday at midnight, then my hydra will build it all so in the morning I can see if it's okay to update | 13:43:16 |
