database-mysql/BiliBiliToolPro
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

pull file
Some checks failed
CodeQL / Analyze (csharp) (push) Has been cancelled
Details
Close Stale Issues / close_stale_issues (push) Has been cancelled
Details
repo-sync / repo-sync (push) Has been cancelled
Details
auto-deploy-tencent-scf / pre-check (push) Has been cancelled
Details
auto-deploy-tencent-scf / deploy serverless (push) Has been cancelled
Details

Browse Source
This commit is contained in:
database-mysql
2026-02-11 23:32:56 +08:00
commit e519cac94e
656 changed files with 45058 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
helm/bilibili-tool/Chart.yaml Normal file
View File

@@ -0,0 +1,24 @@
apiVersion: v2
name: bilibili-tool
description: A Helm chart for running bilibili tool in Kubernetes
# A chart can be either an 'application' or a 'library' chart.
#
# Application charts are a collection of templates that can be packaged into versioned archives
# to be deployed.
#
# Library charts provide useful utilities or functions for the chart developer. They're included as
# a dependency of application charts to inject those utilities and functions into the rendering
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
type: application
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 1.0.1
# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application. Versions are not expected to
# follow Semantic Versioning. They should reflect the version the application is using.
# It is recommended to use it with quotes.
appVersion: "1.0.1"