public/alpine-packages
5
0
Fork 0
Code Issues Pull Requests Actions Packages Releases Activity

Update README package repository URL
All checks were successful
Build Alpine Packages / build-and-publish (push) Successful in 30m46s
Details

Browse Source
This commit is contained in:
Joachim Schlöffel
2026-06-09 10:51:04 +02:00
parent 50e8eaa62a
commit 2a965b05d5
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -6,7 +6,7 @@ This repository builds signed `x86_64` and `aarch64` APKs and publishes them to
the Gitea Alpine package registry under:
```text
https://code.factoring.digital/api/packages/fsp-ops/alpine/v3.23/seaweedfs-alpine
https://code.factoring.digital/api/packages/public/alpine/v3.23/alpine-packages
```
## Use In Production
@@ -16,25 +16,25 @@ https://code.factoring.digital/api/packages/fsp-ops/alpine/v3.23/seaweedfs-alpin
Install the registry signing key on each Alpine node:
```sh
curl -fsSLo /etc/apk/keys/fsp-ops-alpine.rsa.pub \
https://code.factoring.digital/api/packages/fsp-ops/alpine/key
curl -fsSLo /etc/apk/keys/public-alpine.rsa.pub \
https://code.factoring.digital/api/packages/public/alpine/key
```
Add the package repository:
```sh
printf '%s\n' \
'https://code.factoring.digital/api/packages/fsp-ops/alpine/v3.23/seaweedfs-alpine' \
'https://code.factoring.digital/api/packages/public/alpine/v3.23/alpine-packages' \
>> /etc/apk/repositories
apk update
```
If the registry is private, include a Gitea user and package token in the
If a forked or future registry is private, include a Gitea user and package token in the
repository URL:
```text
https://<user>:<token>@code.factoring.digital/api/packages/fsp-ops/alpine/v3.23/seaweedfs-alpine
https://<user>:<token>@code.factoring.digital/api/packages/public/alpine/v3.23/alpine-packages
```
### Install SeaweedFS Node Roles