https://github.com/alyraffauf/slateblue
Developer-centric atomic desktop image based on Fedora Silverblue.
https://github.com/alyraffauf/slateblue
atomic bluebuild fedora fedora-silverblue gnome immutable ostree red-hat rpm-ostree ublue-custom-image
Last synced: about 2 months ago
JSON representation
Developer-centric atomic desktop image based on Fedora Silverblue.
- Host: GitHub
- URL: https://github.com/alyraffauf/slateblue
- Owner: alyraffauf
- License: apache-2.0
- Created: 2024-02-13T17:17:40.000Z (about 1 year ago)
- Default Branch: main
- Last Pushed: 2024-12-16T07:18:34.000Z (4 months ago)
- Last Synced: 2025-01-18T06:42:31.493Z (3 months ago)
- Topics: atomic, bluebuild, fedora, fedora-silverblue, gnome, immutable, ostree, red-hat, rpm-ostree, ublue-custom-image
- Language: JavaScript
- Homepage:
- Size: 72.8 MB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: .github/CODEOWNERS
Awesome Lists containing this project
README
# slateblue
See the [BlueBuild docs](https://blue-build.org/how-to/setup/) for quick setup instructions for setting up your own repository based on this template.
After setup, it is recommended you update this README to describe your custom image.
## Installation
> **Warning**
> [This is an experimental feature](https://www.fedoraproject.org/wiki/Changes/OstreeNativeContainerStable) and should not be used in production, try it in a VM for a while!
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/alyraffauf/slateblue: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/alyraffauf/slateblue: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
This template includes a simple Github Action to build and release an ISO of your image.
To run the action, simply edit the `boot_menu.yml` by changing all the references to startingpoint to your repository. This should trigger the action automatically.
The Action uses [isogenerator](https://github.com/ublue-os/isogenerator) and works in a similar manner to the official Universal Blue ISO. If you have any issues, you should first check [the documentation page on installation](https://universal-blue.org/installation/). The ISO is a netinstaller and should always pull the latest version of your image.
Note that this release-iso action is not a replacement for a full-blown release automation like [release-please](https://github.com/googleapis/release-please).