See the BlueBuild docs for quick setup instructions for setting up your own repository based on this template.
All images are built with a selection of common packages and flatpaks. ZRAM is pre-configured to use LZ4 and from 2 x RAM up to 32 GiB as Swap space, the Virtual Memory management subsystem settings have been configured for both an increased amount of and low latency swapping. The latency improvements come at a price of a higher likelyhood of page faults because readahead has been deactivated.
It is a flavor of Bazzite for ASUS Laptops with some NVIDIA GPU.
An opinionated descendant of Aurora for my usual desktop and tinkering workflows.
Bazzite Stable NVIDIA for desktop gaming.
Bazzite Deck Stable for my Steam Deck clone.
My netbook still exists and is dear to me and so it is running Sway, now.
The tailscaled.service is disabled on Aubertit, Buttgenbachit and Carbonatcyanotrichit.
The podman.service is enabled on Borealis, Buttgenbachit and Flaviramea.
- KeepassXC
- LibreOffice
- Mozilla Firefox
- Signal
- SynologyDrive
- Warehouse
- Discord
- OpenRGB
- AusweisApp2
- BoxBuddy
- Codium
- MediaWriter
- Obsidian
- Ptyxis
- Weasis
- byobu
- kitty
- neovim
- powertop
- powerstat
Let's have a look into some articles I've read over time. I did not do many measurements on my own, just rough observations while using my systems, especially the low memory (4 GiB) netbook I'm using for roughly seven years, and generally fare well with these settings. I'm choosing lz4 over zstd as higher IOPS are - for my use cases - seemingly more important than the compression gain over either lz4 or lzo-rle.
By default Fedora is using the systemd-zram-generator.
- Free vs. Available Memory in Linux; August 30, 2024 by Hayden James, in Blog Linux
- Linux Performance: Almost Always Add Swap Space – Part 2: ZRAM; September 25, 2023 by Hayden James, in Blog Linux
- Tuning ZRAM in Fedora for Better Performance and Get Rid of OOM Crashes; Tue, Dec 12, 2023
Warning
This is an experimental feature, try at your own discretion.
To rebase an existing atomic Fedora installation to the latest build:
- First rebase to the unsigned image, to get the proper signing keys and policies installed:
rpm-ostree rebase ostree-unverified-registry:ghcr.io/blue-build/template:latest - Reboot to complete the rebase:
systemctl reboot - Then rebase to the signed image, like so:
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/blue-build/template:latest - Reboot again to complete the installation
systemctl reboot
The latest tag will automatically point to the latest build. That build will still always use the Fedora version specified in recipe.yml, so you won't get accidentally updated to the next major version.
If build on Fedora Atomic, you can generate an offline ISO with the instructions available here. These ISOs cannot unfortunately be distributed on GitHub for free due to large sizes, so for public projects something else has to be used for hosting.
These images are signed with Sigstore's cosign. You can verify the signature by downloading the cosign.pub file from this repo and running the following command:
cosign verify --key cosign.pub ghcr.io/blue-build/template