particle-os-modules/modules/bling
2025-07-20 17:40:58 +02:00
..
installers chore(bling): There's no need to fetch ublue repo for ublue-update (#429) 2025-07-20 17:19:47 +02:00
bling.sh chore: Remove usage of yq in favor of jq (#369) 2024-12-02 19:02:13 +00:00
bling.tsp fix: Separate models required for separate schema files 2025-01-31 18:28:33 -05:00
dconf-update.service refactor: move bling files to bling module 2024-01-24 18:05:22 +02:00
module.yml feat(bling): Install tainted repos also in rpmfusion submodule 2024-12-08 16:35:50 +01:00
README.md docs(bling): Add note about ublue-update being deprecated (#430) 2025-07-20 17:40:58 +02:00

bling

The bling module can be used to pull in small "bling" into your image. Bling is stuff that doesn't necessitate being configured at build time, in the form of configuration files or program installers.

The bling to pull in is declared under install:, and the code for installing them is all in simple named scripts under the installers/ directory. The basic code for the bling module is very similar to the code of the script module.

Submodule documentation

dconf-update-service

The dconf-update-service submodule creates a systemd unit to automatically update changes you make to dconf in your custom image.

For an example of a dconf keyfile, see the dconf custom defaults documentation.

Take a note that this documentation is for local-users, not for custom image maintainers. But it serves as a good example of what dconf file looks like.
Ignore the advice about creating the user profile, as it's already present & just place dconfs in /etc/dconf/db/distro.d/, not in local.d folder (Thinking like a distribution mindset).

Unlike the gschema-overrides module, dconf keyfiles are not checked at compile time for errors.

ublue-update

This was the default system & applications updater for Universal Blue images.

However, it's deprecated & Universal Blue migrated to uupd:
https://github.com/ublue-os/uupd

Use it with a caution, knowing it's an unmaintained program.