.gitea/workflows/build-artifacts.yaml

@@ -13,7 +13,7 @@ jobs:
 
       - name: Build flake
         run: |
-          /run/current-system/sw/bin/nix build --max-jobs 8 .#sparse-05-client
+          /run/current-system/sw/bin/nix build .#sparse-05-client
 
       - name: Upload resulting binary
         uses: actions/upload-artifact@v4

README.md

@@ -19,16 +19,10 @@ The most mature implementation of Sparse would be the Sparse version 0.5 bind sh
 
 ### Quick start:
 
-- Either download or build the client:
+- Install the Nix package manager on a Linux system: [https://nixos.org/download/]
-  - Download from releases:
+- Run `nix --experimental-features 'nix-command flakes' build .#sparse-05-client`
-    - `sudo wget https://gitea.riouxs.co/andrew.rioux/sparse/releases/download/v0.6.1/sparse-05-client -O /usr/local/bin/sparse-05-client`
+- Generate a Linux server with `result/bin/sparse-05-client generate -t linux service-name`
-    - `chmod +x /usr/local/bin/sparse-05-client`
-  - Build:
-    - Install the Nix package manager on a Linux system: [https://nixos.org/download/]
-    - Run `nix --experimental-features 'nix-command flakes' build .#sparse-05-client`
-    - Copy `result/bin/sparse-05-client` to somewhere in your `$PATH`
-- Generate a Linux server with `sparse-05-client generate -t linux service-name`
 - Copy to and run on a target system as root
-- Connect to it with `sparse-05-client connect service-name.scon SERVER_IP:54248`
+- Connect to it with `result/bin/sparse-05-client connect service-name.scon SERVER_IP:54248`
 - Set up a firewall to block all inbound connections with `iptables -P INPUT DROP`, `iptables -F INPUT`; sparse should still be able to connect and operate
 - Run `iptstate`, `auditbeat`, or `auditd` from another session to see that no IP or UDP traffic is being logged by the kernel