moe-os/README.md

28 lines
1.1 KiB
Markdown
Raw Normal View History

2024-06-19 20:45:11 +02:00
# moe-os   [![build-ublue](https://github.com/moe1369/moe-os/actions/workflows/build.yml/badge.svg)](https://github.com/moe1369/moe-os/actions/workflows/build.yml)
2024-06-19 18:56:48 +02:00
2024-06-20 07:20:25 +02:00
Custom Fedora Image made with [BlueBuild](https://blue-build.org).
For personal use based on [ublue-os Kinoite main Variant](https://github.com/ublue-os/main/)
2024-06-19 18:56:48 +02:00
## Installation
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:
```
2024-06-19 20:45:11 +02:00
rpm-ostree rebase ostree-unverified-registry:ghcr.io/moe1369/moe-os:latest
2024-06-19 18:56:48 +02:00
```
- Reboot to complete the rebase:
```
systemctl reboot
```
- Then rebase to the signed image, like so:
```
2024-06-19 20:45:11 +02:00
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/moe1369/moe-os:latest
2024-06-19 18:56:48 +02:00
```
- 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.