Migrate Flood container publishing to Gitea Actions
Build and Push Custom Flood Image / build (push) Successful in 46s
Build and Push Custom Flood Image / build (push) Successful in 46s
This commit is contained in:
1 parent
4267ac56e4
commit
1c37ec4e96
3 files changed
+88
-52
No files matched your search
@@ -1,2 +1,19 @@
|
||||
# docker-flood-client
|
||||
Flood Client only
|
||||
|
||||
Flood client image. Source: https://git.k2patel.in/k2patel/docker-flood-client
|
||||
|
||||
Public access is read-only; account registration on this server is disabled.
|
||||
Report issues at https://github.com/k2patel/docker-flood-client/issues.
|
||||
For contributions, open an issue with a link to your branch or patch on another
|
||||
Git provider. Changes are reviewed and applied by the maintainer on Gitea.
|
||||
|
||||
Gitea Actions publishes `docker.io/k2patel/floodui:latest` on pushes to `main`
|
||||
and manual runs. The default Flood release is `v4.16.2`; manual runs can select
|
||||
another release with `flood_version`. Builds use the custom `Dockerfile.client`.
|
||||
|
||||
Set Actions secrets `DOCKER_USERNAME` and `DOCKER_TOKEN` with Docker Hub write
|
||||
access to `k2patel/floodui`. Builds run remotely on the Kubernetes runner for
|
||||
`linux/amd64`, pushing directly to Docker Hub. Images are not loaded into the
|
||||
runner image store, and the temporary builder and cache are removed afterward.
|
||||
No image archives or build records are uploaded to Gitea, and no local container
|
||||
builds are required.
|
||||
Reference in new issue
Block a user