particle-os-modules/modules/bling
2024-07-26 16:02:32 +03:00
..
flatpaksync refactor: move bling files to bling module 2024-01-24 18:05:22 +02:00
installers [1password] Remove 1Password-KeyringHelper 2024-03-19 20:44:46 -07:00
50-laptop.conf fix(bling, laptop): QOL Fixes 2024-02-09 00:03:07 -03:00
bling.sh refactor: move bling copr download, switch to ublue staging copr 2024-02-21 17:59:22 +02:00
bling.tsp feat: add typespec schemas for modules (#233) 2024-07-09 16:25:31 +00:00
dconf-update.service refactor: move bling files to bling module 2024-01-24 18:05:22 +02:00
module.yml chore: remove raw github URLs from module.ymls (unneeded after recent refactor) 2024-07-26 16:02:32 +03:00
README.md docs: Improve documentation of relocatable schemas (#177) 2024-03-26 07:12:01 +00: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

flatpaksync (unmaintained)

The flatpaksync submodule can be used to synchronize a list of user Flatpaks with a git repository.

Once the submodule is activated, you should create the file $HOME/.config/flatpaksync/env that sets the GIT_REPO variable to the git URL of your repository. This repository can be empty, or a previous flatpaksync installation. The repository is automatically cloned into /tmp/sync for the synchronization.

# ~/.config/flatpaksync/env
GIT_REPO=<YOUR_REPO>

To initialize your Flatpaks from flatpaksync, simply run the flatpakcheckout command to perform the installation and start the synchronization.

It is important to note that this submodule will NOT enable Flathub. If your applications come from there, you will need to enable Flathub before running it.

If you have configured the repository in the $HOME/.config/flatpaksync/env file but already have the Flatpaks installed, simply create the $HOME/.config/flatpaks.user.installed file to inform the script that the installation is done and start the synchronization.

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.

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