Add Gitea Alpine registry workflow

README.md

@@ -1,6 +1,6 @@
 # SeaweedFS Alpine Package
 
-Local Alpine packaging for SeaweedFS `4.31`. The workflow runs Alpine tooling
+Local Alpine 3.23 packaging for SeaweedFS `4.31`. The workflow runs Alpine tooling
 inside Docker and writes signed packages under `packages/local/<arch>/`.
 
 ## Commands
@@ -17,6 +17,8 @@ mise run apk:packages
 mise run apk:smoke
 mise run apk:test-shell
 mise run apk:publish-check
+mise run apk:publish-gitea
+mise run gitea-workflow-build
 mise run apk:shell
 mise run apk:clean
 ```
@@ -50,6 +52,12 @@ The package repackages upstream release tarballs, so builds use
 `ALPINE_BUILD_PLATFORM=linux/amd64` by default. Signing keys and distfiles are
 cached in `.cache/abuild/` and `.cache/apk-distfiles/`.
 
+The Gitea workflow publishes to the Alpine package registry branch `v3.23`.
+Override `ALPINE_VERSION` and `ALPINE_REGISTRY_BRANCH` if you intentionally
+build for another Alpine branch, including `edge`.
+Use `mise run gitea-workflow-build` for a local `pull_request` workflow check
+through `act`; the publish step is skipped for that event.
+
 ## Test And Publish
 
 ```sh
@@ -116,6 +124,32 @@ rc-service seaweedfs.master start
 If the repo key is missing on a target system, copy `.cache/abuild/*.rsa.pub`
 into `/etc/apk/keys/` before `apk update`.
 
+## Gitea Registry
+
+The Gitea workflow reads these repository variables and secrets:
+
+```text
+Variables: INSTANCE_URL, PACKAGE_OWNER, PACKAGE_NAME
+Secrets:   PACKAGE_USER, PACKAGE_TOKEN
+```
+
+It uploads each built `*.apk` with HTTP `PUT` to:
+
+```text
+${INSTANCE_URL}/api/packages/${PACKAGE_OWNER}/alpine/v3.23/${PACKAGE_NAME}
+```
+
+For local publishing, run:
+
+```sh
+INSTANCE_URL=https://code.factoring.digital \
+PACKAGE_OWNER=fspdigital \
+PACKAGE_NAME=seaweedfs-alpine \
+PACKAGE_USER=... \
+PACKAGE_TOKEN=... \
+mise run apk:publish-gitea
+```
+
 ## Alpine Package Dos And Don'ts
 
 Do: