Skip to content

Latest commit

 

History

History
134 lines (87 loc) · 5.03 KB

README.md

File metadata and controls

134 lines (87 loc) · 5.03 KB

OmegaSquad82/BlueBuilds   bluebuild Dependabot Updates

See the BlueBuild docs for quick setup instructions for setting up your own repository based on this template.

Images

All images are built with a selection of common packages and flatpaks. ZRAM is pre-configured to use system default compression (likely LZ4) and from 2xRAM up to 32 GiB as Swap space and Virtual Memory settings have been configured for both 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.

Aubertit

It is a flavor of Bazzite for ASUS Laptops with some NVIDIA GPU.

Borealis

An opinionated descendant of Aurora for my usual desktop and tinkering workflows.

Buttgenbachit

Bazzite Stable NVIDIA for desktop gaming.

Carbonatcyanotrichit

Bazzite Deck Stable for my Steam Deck clone.

Flaviramea

My netbook still exists and is dear to me and so it is running Sway, now.

Customizations

Bazzite

Both goverlay and mangohud packages are installed on top and the tailscaled.service is disabled.

Podman

The podman.service is enabled on Borealis, Buttgenbachit and Flaviramea.

Flatpaks

All images

  • KeepassXC
  • LibreOffice
  • Mozilla Firefox
  • Signal
  • SynologyDrive
  • Warehouse

Bazzite images

  • Discord
  • OpenRGB

Select images

  • AusweisApp2
  • BoxBuddy
  • Codium
  • MediaWriter
  • Obsidian
  • Weasis

Packages

  • byobu
  • kitty
  • neovim
  • powertop
  • powerstat

swap on zram

Let's have a look into some articles I've read over time. I did not do any 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, now. By default Fedora is using the systemd-zram-generator.

Blogs

Documentation

Github

Wikis

Installation

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.

ISO

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.

Verification

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