Search Results

The Lix project endeavours to not deadname people, because we believe in human decency. However, some of our software has other ideas. This page documents the workarounds to manually fix profile updates that don't get conducted because various software is bust...

nix uses libstdc++'s std::regex. it uses whatever version of libstdc++ the host system has. which it invokes in both std::regex_replace std::regex_match modes. nix occasionally uses the flags std::regex::extended and std::regex::icase which determine the avail...

This page documents the dreams of the Lix team. These are features which we have generally not roadmapped yet, and which may not have complete and thoroughly thought-through plans, and which we would like to think about more completely before implementing. We ...

The Lix infrastructure is maintained with Nix code at https://git.lix.systems/lix-project/web-services. That repository is the source of truth for what's serving where, but we attempt to reflect that here as well for ease of reference. This page is the source ...

This guide is primarily about CppNix->Lix commit ports and was written when we were doing a lot of those before 2.90. It also applies to Lix->Lix ports, though, those are much easier, often just taking clicking "cherry pick" in the gerrit UI. Don't forget, usi...

Lix has one source of truth for authentication: Keycloak (identity.lix.systems). Most services are bound to Keycloak for authentication via OAuth2, although it supports SAML as well. GitHub vs Local accounts GitHub accounts are used at Lix for two reasons: Ea...

The Lix system is constituted of two broad parts, the evaluator and the store daemon. The two pieces may run on the same machine or on different machines. For example, in a remote build setup like https://hydra.nixos.org, one node is running several evaluators...

Our buildbot instance has a habit of breaking due to excess load. Restarting the worker If the worker (primary, handling nix evaluations) explodes, it can be restarted. ssh root@buildbot.lix.systems 'systemctl restart buildbot-worker.service' Re-trying spuriou...

Operational Conventions Code Review Self Stamping and Merging On our Gerrit, core members have permissions to +2 any arbitrary CL, because sometimes we should be able to get something in quickly, and talk about it afterwards. In almost every case, the author o...

This document is extremely a draft. It needs some editing and discussion before it can be made into a useful thing. It's been simply copy pasted out of the pad in its current form. See also FIXME: piegames langver ideas musings puck: honestly, having languag...

Why? Why self-host all your own infrastructure? We tried not to, at the very beginning of the project. We agreed that Github-style code review wasn't really fit for our kind of project, and wanted to use Gerrit for code review. We started setting up Gerrithub ...

Here, for now (public edit link): https://pad.lix.systems/lix-docs-planning

Moved to https://lix.systems/community-standards/

Agenda Prohibited items: Nix foundation politics, for everyone's safety Core Agenda: Figure out an initial governance model we can use to bootstrap governance later Figure out how to do a soft release Figure out anything that needs to be done before this re...

To obliterate history from the Git repo means removing it from three different sources: Gerrit, Forgejo, and GitHub. A tool has been written, called gerrit-rewrite-branch, to rewrite Gerrit history completely, including the meta on past CLs. To use it, build i...

Moved to https://lix.systems/community-standards/