26caeaf488
* add direnv support * elm format * use flake-utils * remove unused parts of the code * only use one workflow to import things * Build flake-info in separate job * DEBUG * Revert "DEBUG" This reverts commit 6c335e6bd2ba450f1891efe70dfd9bb95f300b31. * RUST_LOG is a runtime thing |
||
|---|---|---|
| .github | ||
| flake-info | ||
| flakes | ||
| src | ||
| tests | ||
| .envrc | ||
| .gitignore | ||
| default.nix | ||
| elm-srcs.nix | ||
| elm.json | ||
| flake.lock | ||
| flake.nix | ||
| netlify.toml | ||
| overlay.nix | ||
| package.json | ||
| README.md | ||
| registry.dat | ||
| VERSION | ||
| versions.dat | ||
| webpack.config.js | ||
| yarn.lock | ||
search.nixos.org
This repository contains the scripts and the web application for
search.nixos.org.
How this project came to be
Initial idea was to replace NixOS packages and options search which was fetching one JSON file which contained all packages (or options). This approach is good for its simple setup, but started to show its problems when packages number was getting bigger and bigger. I'm sure we could optimize it further, but ideas what all could we do if there would be some database in the back were to tempting not to try.
For backend we are using Elasticsearch instance which is kindly sponsored by bonsai.io. On the frontend we are using Elm.
How search works?
The use case we want to solve is that a visitor want to see if a package exists or to look up certain package's details.
A user wants to converge to a single result if possible. The more characters are added to a search query the more narrow is search is and we should show less results.
Very important is also ranking of search results. This will bring more relevant search results to the top, since a lot of times it is hard to produce search query that will output only one result item.
A less important, but providing better user experience. are suggestions for writing better search query. Suggesting feature should guide user to write better queries which in turn will produce better results.
Development
To start developing open a terminal and run:
$ nix-shell --run "yarn dev"
You can point your browser to http://localhost:3000 and start developing.
Any changes to source files (./src) will trigger a hot reload of an
application.
Deploying
- On each commit to
mainbranch a GitHub Action is triggered. - GitHub Action then builds production version of the web application using
yarn prodcommand. - The built web application (in
./dist) is then deployed to Netlify. - GitHub Action can also be triggered via Pull Request, which if Pull Request was created from a non-forked repo's branch, will provide a preview url in a comment.
Adding flakes
To add your own flakes to the search index edit ./flakes/manual.toml.
Possible types are github, gitlab, and git (which is the fallback for any kind of git repository but requires to set a revision key manually as of now).
To test whether your flake is compatible with nix flake-info you can try running flake-info against it
$ nix run github:nixos/nixos-search#flake-info -- flake <your flake handle>