Skip to content
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.

Commit

Permalink
chore: move yafti's behavior explanation from recipe to readme
Browse files Browse the repository at this point in the history
  • Loading branch information
Arcitec authored and xynydev committed May 10, 2023
1 parent 946f3d8 commit f596f4c
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 11 deletions.
7 changes: 4 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,10 +66,11 @@ matrix:
### [yafti](https://github.com/ublue-os/yafti/)
`yafti` is the uBlue firstboot installer, and it's configuration can be found in `/etc/yafti.yml`. You can look at what's done in the config and modify it to your liking.
It includes an optional selection of Flatpaks to install out of the box. A new group will be added for the Flatpaks declared in `recipe.yml`, which will be enabled by default.
`yafti` is the uBlue "first boot" installer. It shows up the first time a user logs into uBlue. By default, the menu also shows up again anytime the image's yafti configuration differs from the user's last encounter, so feel free to expand or modify your custom image's yafti configuration over time. Your users will then see the yafti menu again after the OS update, and will be given a chance to install any new additions.

The files `/etc/profile.d/ublue-firstboot.sh` and `/etc/skel.d/.config/autostart/ublue-firstboot.desktop` set up `yafti` so that it starts on boot, so if you wish to retain that functionality those files shouldn't be touched.
Its configuration can be found in `/etc/yafti.yml` of the installed OS. It includes an optional selection of Flatpaks to install, along with a new group that's automatically added for all Flatpaks declared in `recipe.yml`. You can look at what's done in the config and modify it to your liking.

The files `/etc/profile.d/ublue-firstboot.sh` and `/etc/skel.d/.config/autostart/ublue-firstboot.desktop` set up `yafti` so that it starts on boot, which means that you shouldn't touch those files if you wish to retain that functionality.

## Installation

Expand Down
12 changes: 4 additions & 8 deletions recipe.yml
Original file line number Diff line number Diff line change
Expand Up @@ -59,14 +59,10 @@ rpm:
- firefox
- firefox-langpacks

# These Flatpaks will be suggested for install on user login, via the yafti
# "first boot" GUI. By default, the menu also shows up again anytime the image's
# yafti configuration differs from the user's last encounter, so feel free
# to expand the selection over time. Your users will then see the yafti menu
# again after OS update, and will be given a chance to install new additions.
# Everything below will be merged into the "etc/yafti.yml" config on build,
# in a category named "Custom". If you prefer, you can instead remove everything
# below and purely use "etc/yafti.yml" to have more control over settings.
# These Flatpaks will be suggested for install after user login, via the yafti
# "first boot" GUI. Everything below will be merged into the "etc/yafti.yml" config
# on build, in a category named "Custom". If you prefer, you can instead remove
# everything below and directly edit "etc/yafti.yml" to have more control.
# This is just an example selection.
flatpaks:
- org.mozilla.firefox
Expand Down

0 comments on commit f596f4c

Please sign in to comment.