particle-os/particle-os-modules
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore: replace URLs with ublue-os/bling

Browse source
This commit is contained in:
xynydev 2024-02-21 16:39:34 +02:00
parent 1d50642f88
commit c6aea9234c
11 changed files with 35 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

13
README.md
View file

@ -1,21 +1,23 @@
# bling
[![build-ublue](https://github.com/ublue-os/bling/actions/workflows/build.yml/badge.svg)](https://github.com/ublue-os/bling/actions/workflows/build.yml)
[![build-ublue](https://github.com/blue-build/modules/actions/workflows/build.yml/badge.svg)](https://github.com/blue-build/modules/actions/workflows/build.yml)
This repository containes modules to use in recipe.yml. See list of modules in [./modules](./modules/)
## Usage
You can add this to your Containerfile to copy the modules from this image over:
```dockerfile
COPY --from=ghcr.io/ublue-os/bling:latest /modules /tmp/modules/
COPY --from=ghcr.io/blue-build/modules:latest /modules /tmp/modules/
```
## Verification
These images are signed with sisgstore's [cosign](https://docs.sigstore.dev/cosign/overview/). You can verify the signature by downloading the `cosign.pub` key from this repo and running the following command:
```sh
cosign verify --key cosign.pub ghcr.io/ublue-os/bling
cosign verify --key cosign.pub ghcr.io/blue-build/modules
```
## See what is in this image
@ -25,7 +27,7 @@ cosign verify --key cosign.pub ghcr.io/ublue-os/bling
NOTE: This makes it so you need to extract everything from the base image!
```sh
podman save ghcr.io/ublue-os/bling:latest -o bling.tar
podman save ghcr.io/blue-build/modules:latest -o bling.tar
tar xf bling.tar && rm bling.tar
tar xf *.tar
```
@ -35,6 +37,7 @@ This should extract the image in a way that you can see everything in it!
### Using [Dive](https://github.com/wagoodman/dive)
This method allows you to inspect the image through a TUI
```sh
dive ghcr.io/ublue-os/bling:latest
dive ghcr.io/blue-build/modules:latest
```

22
modules.json
View file

@ -1,13 +1,13 @@
[
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/akmods/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/bling/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/default-flatpaks/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/files/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/fonts/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/gschema-overrides/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/rpm-ostree/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/script/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/signing/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/systemd/module.yml",
"https://raw.githubusercontent.com/ublue-os/bling/main/modules/yafti/module.yml"
"https://raw.githubusercontent.com/blue-build/modules/main/modules/akmods/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/bling/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/default-flatpaks/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/files/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/fonts/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/gschema-overrides/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/rpm-ostree/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/script/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/signing/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/systemd/module.yml",
"https://raw.githubusercontent.com/blue-build/modules/main/modules/yafti/module.yml"
]

2
modules/akmods/module.yml
View file

@ -1,6 +1,6 @@
name: akmods
shortdesc: The akmods module is a tool used for managing and installing kernel modules built by Universal Blue.
readme: https://raw.githubusercontent.com/ublue-os/bling/main/modules/akmods/README.md
readme: https://raw.githubusercontent.com/blue-build/modules/main/modules/akmods/README.md
example: |
type: akmods
install:

2
modules/bling/module.yml
View file

@ -1,6 +1,6 @@
name: bling
shortdesc: The bling module can be used to pull in small "bling" into your image.
readme: https://raw.githubusercontent.com/ublue-os/bling/main/modules/bling/README.md
readme: https://raw.githubusercontent.com/blue-build/modules/main/modules/bling/README.md
example: |
type: bling
install:

2
modules/default-flatpaks/module.yml
View file

@ -1,6 +1,6 @@
name: default-flatpaks
shortdesc: The default-flatpaks module can be used to install or uninstall flatpaks from a configurable remote on every boot.
readme: https://raw.githubusercontent.com/ublue-os/bling/main/modules/default-flatpaks/README.md
readme: https://raw.githubusercontent.com/blue-build/modules/main/modules/default-flatpaks/README.md
example: |
modules: # configured multiple times to highlight how options are overridden
- type: default-flatpaks

2
modules/files/README.md
View file

@ -3,5 +3,5 @@
The `files` module simplifies the process of copying files to the image during the build time. These files are sourced from the `config/files` directory, which is located at `/tmp/config/files` inside the image.
:::note
If you want to place any files in `/etc/`, you should place them in `/usr/etc/` instead, which will be used to generate `/etc/` on a booted system. That is the proper directory for "system" configuration templates on atomic Fedora distros, whereas `/etc/` is meant for manual overrides and editing by the machine's admin AFTER installation! See issue https://github.com/ublue-os/startingpoint/issues/28.
If you want to place any files in `/etc/`, you should place them in `/usr/etc/` instead, which will be used to generate `/etc/` on a booted system. That is the proper directory for "system" configuration templates on atomic Fedora distros, whereas `/etc/` is meant for manual overrides and editing by the machine's admin AFTER installation! See issue https://github.com/blue-build/legacy-template/issues/28.
:::

2
modules/files/module.yml
View file

@ -1,6 +1,6 @@
name: files
shortdesc: The files module simplifies the process of copying files to the image during the build time.
readme: https://raw.githubusercontent.com/ublue-os/bling/main/modules/files/README.md
readme: https://raw.githubusercontent.com/blue-build/modules/main/modules/files/README.md
example: |
type: files
files:

2
modules/gschema-overrides/module.yml
View file

@ -1,6 +1,6 @@
name: gschema-overrides
shortdesc: The `gschema-overrides` module can be used for including system-setting overrides for GTK-based desktop environments.
readme: https://raw.githubusercontent.com/ublue-os/bling/main/modules/gschema-overrides/README.md
readme: https://raw.githubusercontent.com/blue-build/modules/main/modules/gschema-overrides/README.md
example: |
type: gschema-overrides
include:

2
modules/script/module.yml
View file

@ -1,6 +1,6 @@
name: script
shortdesc: The script module can be used to run arbitrary scripts at image build time.
readme: https://raw.githubusercontent.com/ublue-os/bling/main/modules/script/README.md
readme: https://raw.githubusercontent.com/blue-build/modules/main/modules/script/README.md
example: |
type: script
scripts:

2
modules/systemd/module.yml
View file

@ -1,6 +1,6 @@
name: systemd
shortdesc: The systemd module streamlines the management of systemd units during image building.
readme: https://raw.githubusercontent.com/ublue-os/bling/main/modules/systemd/README.md
readme: https://raw.githubusercontent.com/blue-build/modules/main/modules/systemd/README.md
example: |
type: systemd
system:

2
modules/yafti/README.md
View file

@ -4,4 +4,4 @@ The [`yafti`](https://github.com/ublue-os/yafti) module can be used to install [
Optionally, a list of Flatpak names and IDs can be included under `custom-flatpaks:`. These will be enabled by default under their own section on the Flatpak installation screen of `yafti`.
A default version of the `yafti` configuration file, `yafti.yml`, is supplied by this module. To make your own, create the file at `/usr/share/ublue-os/firstboot/yafti.yml`. The default version of the file can be found [here](https://github.com/ublue-os/bling/blob/main/modules/yafti/yafti.yml).
A default version of the `yafti` configuration file, `yafti.yml`, is supplied by this module. To make your own, create the file at `/usr/share/ublue-os/firstboot/yafti.yml`. The default version of the file can be found [here](https://github.com/blue-build/modules/blob/main/modules/yafti/yafti.yml).