| 10 Apr 2022 |
 @blaggacao:matrix.org | I think the next improvement to this PR would be to make the evaluator configurable, so that it doesn't need to be patched into the binary. | 00:38:12 |
| @blaggacao:matrix.org | That way people can modify the colmena interface at will and make it work for their code / project structure. | 00:38:52 |
| @blaggacao:matrix.org | Instead of doing complicated transforms to match the expected interface. | 00:39:24 |
 @jhillyerd:matrix.org | In reply to @schnecfk:ruhr-uni-bochum.de
So keys are only uploaded if you're using colmena, but not with the built flakes Thanks. I guess none of my services would start for local testing, so that's not really an option. 😕 I think I'll try agenix, that seems reasonable for homelab. | 00:40:59 |
| @blaggacao:matrix.org | * https://github.com/zhaofengli/colmena/pull/73 i wanted to quickly ping, to see if this is mergeable stuff. I think it's a neat idea to spin this further so that projecta can declare their local evaluator (which is great for lowering the magic) while still using upstream options and modules. | 00:41:00 |
| @jhillyerd:matrix.org | Then again, I guess the host key would change for each VM... so maybe not. | 00:41:27 |
| 11 Apr 2022 |
 Zhaofeng Li | In reply to @blaggacao:matrix.org
https://github.com/zhaofengli/colmena/pull/73 i wanted to quickly ping, to see if this is mergeable stuff. I think it's a neat idea to spin this further so that projecta can declare their local evaluator (which is great for lowering the magic) while still using upstream options and modules. Sorry about the wait, and thing looks reasonable in the PR. I wanted to push 0.3 out (which has been stuck for quite a while) before merging, but got sidetracked by other stuff IRL. I'll hopefully get around to it later this week or next week. | 18:08:27 |
| @blaggacao:matrix.org | Oh great to hear! Yeah, I'm happy to get a little more involved with the codebase in the coming days / weeks. Planning on maybeMigrate 😂 | 23:24:16 |
| 12 Apr 2022 |
|  @linus:schreibt.jetzt joined the room. | 18:47:42 |
| 18 Apr 2022 |
 aanderse | any way to specify multiple colmena outputs in a flake? basically i want a repo that houses n "hives" and tagging isn't enough to keep them separate | 20:34:28 |
| aanderse | maybe something like outputs = { ... }: { colmena-hive-1 = { ... }; colmena-hive-2 = { ... }; } then pass a flag tocolmena to tell it which one to process? | 20:36:20 |
| aanderse | or am i just thinking tags aren't my solution when really they are? | 20:36:53 |
 Buckley | Well, I guess that depends why you feel tags aren’t sufficient | 20:37:17 |
| Buckley | I think you can combine multiple tags to filter output down more, like @deployment1,@webservers will pick only the webservers which are also deployment1, but double check me there | 20:38:09 |
| Buckley | Then multiple deployments… | 20:38:26 |
