-
Notifications
You must be signed in to change notification settings - Fork 263
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: added information on rolling alpine tokens
- Loading branch information
Showing
1 changed file
with
19 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
To generate new release keys, first start the alpine docker container: | ||
|
||
```bash | ||
docker run -it --rm -v $(pwd):/work/mise ghcr.io/jdx/mise:alpine | ||
``` | ||
|
||
And inside the container: | ||
|
||
```bash | ||
sudo su - packager | ||
abuild-keygen -a -n | ||
``` | ||
|
||
Then store them in Github secrets as `ALPINE_PRIV_KEY` and `ALPINE_PUB_KEY`. | ||
Note the name of the private key file, it will be something like `-5f2b2c4e.rsa`. | ||
Save that string as `ALPINE_KEY_ID` as another secret. | ||
|
||
Also, the `ALPINE_GITLAB_TOKEN` needs to be rolled as well, use the [alpine gitlab portal](https://gitlab.alpinelinux.org/-/user_settings/personal_access_tokens) | ||
to generate a new token and store it in Github secrets as `ALPINE_GITLAB_TOKEN`. |