readme - remove mention of experimental flag (#30)

This commit is contained in:
Jorge O. Castro
2023-01-28 14:42:18 -05:00
committed by GitHub
parent 52290611ed
commit b20fb47baf

View File

@@ -8,11 +8,11 @@ A base image with a (mostly) stock Fedora Silverblue. Help us make a sweet base
Warning: This is an experimental feature and should not be used in production, try it in a VM for a while, you have been warned!
sudo rpm-ostree rebase --experimental ostree-unverified-registry:ghcr.io/ublue-os/base:latest
sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/base:latest
We build date tags as well, so if you want to rebase to a particular day's release:
sudo rpm-ostree rebase --experimental ostree-unverified-registry:ghcr.io/ublue-os/base:20221217
sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/base:20221217
The `latest` tag will automatically point to the latest build.
@@ -59,4 +59,4 @@ These images are signed with sisgstore's [cosign](https://docs.sigstore.dev/cosi
cosign verify --key cosign.pub ghcr.io/ublue-os/base
If you're forking this repo you should [read the docs](https://docs.github.com/en/actions/security-guides/encrypted-secrets) on keeping secrets in github. You need to [generate a new keypair](https://docs.sigstore.dev/cosign/overview/) with cosign. The public key can be in your public repo (your users need it to check the signatures), and you can paste the private key in Settings -> Secrets -> Actions.
If you're forking this repo you should [read the docs](https://docs.github.com/en/actions/security-guides/encrypted-secrets) on keeping secrets in github. You need to [generate a new keypair](https://docs.sigstore.dev/cosign/overview/) with cosign. The public key can be in your public repo (your users need it to check the signatures), and you can paste the private key in Settings -> Secrets -> Actions.