Search Results

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

Everyone in the Lix community is expected to abide by the Lix Community Standards.

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...

This is an interim set of Lix Community Standards, to be reviewed and revised further when the governance process is further along. These standards are in force and will be enforced until that time. The following are principles and do not in any way limit the ...

Since Matrix is haunted sometimes, here is a list of rooms in the public Lix space: Public space #space:lix.systems #community-team:lix.systems, for moderation concerns #announcements:lix.systems, for announcements relating to the Lix beta #discuss:lix.s...

See hacking.md in the Lix repo for the main documentation. Extra tips can go here.

In an ideal world, all permissions are managed directly in Keycloak and propagated down to downstream systems automatically. We mostly live in that world. We would also like more parts of profiles to propagate from Keycloak into downstream systems (see changin...

A brief overview of our code infrastructure for those not in the Lix project: Forgejo https://git.lix.systems for issue tracking for Lix and other projects, as well as for project boards. It also provides a read-only git mirror of Lix, forks for WIP code in ...

The buildbot box was returning "no free space" to basically any btrfs operation including collecting garbage. Yet df -h stated that it had disk around. Damn it!! https://ohthehugemanatee.org/blog/2019/02/11/btrfs-out-of-space-emergency-response/ The box has an...

Goal: install lix on a riscv64-linux system The target is a DevTerm R-01, so it's an AllWinner D1 RISC-V processor @ 1GHz, with 1GB of memory and 32GB of microSD. We can't run the Lix installer without building it, because there's no canned build for it. So le...

The Lix repository contains multiple releases in parallel. The branches work as follows: main. This contains major tags (except for 2.90 because of an early branch-off. We might fix that manually?), and is for the next major version of the software. This is ...

Release names are the names of frozen desserts. There's a list on Wikipedia of frozen desserts, but of course, others can be added. The purpose of release names is that they are cute, and they are not necessarily picked for any reason. Used release names: 2.9...

See How do permissions work? for implementation details. tldr; Go to the admin console (no trailing slash) Go to Groups -> YourGroupHere -> Members Add/Remove members as needed Note: most permissions only update after logging out and back into the appropriat...

Introduction We use garage, an open-source server compatible with Amazon's S3 API, hosted on our own infrastructure. Currently we store both documentation and binaries there; it may be used for other things down the line. Configuring a client You probably want...