mirror of
https://github.com/optim-enterprises-bv/secureblue.git
synced 2025-11-07 05:47:53 +00:00
docs: update readme
This commit is contained in:
@@ -77,6 +77,7 @@ If you're forking this repo you should [read the docs](https://docs.github.com/e
|
|||||||
- Call it `SIGNING_SECRET` and then paste the contents of `cosign.key` into the field and save it. Be careful to make sure it's the .key file and not the .pub file. It should look like this:
|
- Call it `SIGNING_SECRET` and then paste the contents of `cosign.key` into the field and save it. Be careful to make sure it's the .key file and not the .pub file. It should look like this:
|
||||||

|

|
||||||
- Copy the `cosign.pub` key into the root of your repository, replacing the key you got from here.
|
- Copy the `cosign.pub` key into the root of your repository, replacing the key you got from here.
|
||||||
|
- Copy the instructions from the verification section of this readme and make adjustments to your container url. This part is important, users must have a method of verifying the image. The linux desktop must not lag behind in cloud when it comes to supply chain security, so we're starting right from the start! (Seriously don't skip this part)
|
||||||
1. Start making modifications to your Containerfile!
|
1. Start making modifications to your Containerfile!
|
||||||
- Change a few things and keep an eye on your Actions and Packages section of your repo, you'll generate a new image one every merge and additionally every day.
|
- Change a few things and keep an eye on your Actions and Packages section of your repo, you'll generate a new image one every merge and additionally every day.
|
||||||
- Follow the instructions at the top of this repo but this time with the `ghcr.io/yourusername/beagles` url and then you'll be good to go!
|
- Follow the instructions at the top of this repo but this time with the `ghcr.io/yourusername/beagles` url and then you'll be good to go!
|
||||||
|
|||||||
Reference in New Issue
Block a user