| 7 Jul 2021 |
 samueldr | (I did state two days ago I couldn't make it) :) | 20:08:32 |
 bpiv400 | Does anyone know who the admins of the Discourse are? | 20:25:33 |
 jonringer | ryantm, zimbatim | 20:27:29 |
| bpiv400 | ty | 20:27:44 |
 ryantm | https://discourse.nixos.org/about | 20:35:25 |
| 12 Jul 2021 |
 andi- | search.nixos.org has slowed down dramatically. Searching in the options for things like "nginx" takes >20s. | 14:19:45 |
| andi- | cc garbas | 14:19:52 |
 matthewcroughan - nix.zone | Is there ways people could host instances of this? | 14:20:23 |
| matthewcroughan - nix.zone | * Is there ways people could host instances of this, to take the load off? | 14:20:41 |
| matthewcroughan - nix.zone | I would host one for example. | 14:20:51 |
| andi- | The ES backend is hosted by some company. | 14:20:58 |
| matthewcroughan - nix.zone | Seems to be the case with the Discourse too. | 14:28:37 |
| matthewcroughan - nix.zone | Not that we shouldn't be relying on companies, we should in some capacity. But this might be one of those things that makes sense to federate. | 14:28:52 |
| andi- | IMO we can implement this entirely without a search in the backend. At least for the current usages that is possible. I've once implemented a hacky WIP at https://s.rammhold.de/nixos-search/ for just the NixOS module search | 14:31:26 |
| matthewcroughan - nix.zone | Wow that's fast. | 14:31:47 |
| matthewcroughan - nix.zone | huh, I wonder if this is in the LSP? | 14:32:06 |
| matthewcroughan - nix.zone | I don't think it is, but this could seriously enhance the existing lsp. | 14:32:32 |
 niksnut | That's what we used to do right? (Read the entire options.json / packages.json into the client.) Problem is that it doesn't scale very well. | 15:15:21 |
| andi- | In reply to @niksnut:matrix.org
That's what we used to do right? (Read the entire options.json / packages.json into the client.) Problem is that it doesn't scale very well. That isn't what my approach does. I only have ship a limited search index at first and as you type lazy-load more detailed data. | 15:16:38 |
| andi- | In reply to @niksnut:matrix.org
That's what we used to do right? (Read the entire options.json / packages.json into the client.) Problem is that it doesn't scale very well. * That isn't what my approach does. I only ship a limited search index at first and as you type lazy-load more detailed data. | 15:16:48 |
| andi- | That page is just a POC of the idea. It could be more efficient or match better but I didn't spent more time on it. | 15:17:52 |
| matthewcroughan - nix.zone | Yeah I noticed that my enter key wasn't the thing triggering the search. | 15:23:47 |
| matthewcroughan - nix.zone | And it is lazy loaded, as it should be, it's brilliant. | 15:23:56 |
| matthewcroughan - nix.zone | Have you got the sources for how this was done? I have never implemented anything like that before and wonder how hard it could be. | 15:24:20 |
| andi- | In reply to @matthewcroughan:defenestrate.it
Have you got the sources for how this was done? I have never implemented anything like that before and wonder how hard it could be. Yeah, it is mostly just using lunr and hacking around it to make it useful for that POC https://github.com/andir/nixos.dev-option-search/blob/master/create-index.js | 15:28:35 |
| 20 Jul 2021 |
|  sumner left the room. | 21:43:02 |
| 21 Jul 2021 |
| samueldr | another person also had a similar PoC with the package search | 18:39:51 |
| samueldr | (shared when we were already committed to going with ES) | 18:40:03 |
| samueldr | not sure how/where it differs | 18:40:11 |
| samueldr | I've been using the options search a lot these past few days and... not been pleased with the irrelevance of the "relevant" results :( | 18:40:42 |
