chore: sync local project changes
This commit is contained in:
Shen Wei
@@ -1,35 +1,35 @@
|
||||
---
|
||||
title: "Amazon Web Services (AWS)"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- Cloud
|
||||
- Hybrid-Cloud
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Amazon Web Services (AWS)
|
||||
|
||||
Amazon Web Services (AWS) is the world's most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally.
|
||||
|
||||
## Aliases
|
||||
- AWS
|
||||
- Amazon Web Services
|
||||
|
||||
## Key Partnerships
|
||||
- **VMware Cloud on AWS (VMC on AWS)**: AWS partnered with VMware to run VMware workloads natively on AWS infrastructure. The underlying hardware consists of i3.metal and i3en.metal bare metal servers, organized into clusters within availability zones and regions.
|
||||
|
||||
## Infrastructure for VMC on AWS
|
||||
- **i3.metal**: Bare metal server instance used for VMware Cloud on AWS SDDC deployment
|
||||
- **i3en.metal**: Enhanced bare metal instance with larger storage capacity
|
||||
- **Clusters**: Organized within availability zones and regions globally
|
||||
- **Stretched Clusters**: Available across availability zones for increased resilience
|
||||
|
||||
## Connections
|
||||
- [[VMware-Cloud-on-AWS]] ← powered_by ← [[AWS]]
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]] ← source ← [[AWS]]
|
||||
- [[VMware]] ← partners ← [[AWS]]
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]]
|
||||
---
|
||||
title: "Amazon Web Services (AWS)"
|
||||
type: entity
|
||||
tags:
|
||||
- AWS
|
||||
- Cloud
|
||||
- Hybrid-Cloud
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
last_updated: 2026-04-25
|
||||
---
|
||||
|
||||
## Amazon Web Services (AWS)
|
||||
|
||||
Amazon Web Services (AWS) is the world's most comprehensive and broadly adopted cloud platform, offering over 200 fully featured services from data centers globally.
|
||||
|
||||
## Aliases
|
||||
- AWS
|
||||
- Amazon Web Services
|
||||
|
||||
## Key Partnerships
|
||||
- **VMware Cloud on AWS (VMC on AWS)**: AWS partnered with VMware to run VMware workloads natively on AWS infrastructure. The underlying hardware consists of i3.metal and i3en.metal bare metal servers, organized into clusters within availability zones and regions.
|
||||
|
||||
## Infrastructure for VMC on AWS
|
||||
- **i3.metal**: Bare metal server instance used for VMware Cloud on AWS SDDC deployment
|
||||
- **i3en.metal**: Enhanced bare metal instance with larger storage capacity
|
||||
- **Clusters**: Organized within availability zones and regions globally
|
||||
- **Stretched Clusters**: Available across availability zones for increased resilience
|
||||
|
||||
## Connections
|
||||
- [[VMware-Cloud-on-AWS]] ← powered_by ← [[AWS]]
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]] ← source ← [[AWS]]
|
||||
- [[VMware]] ← partners ← [[AWS]]
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-43-vmware-cloud-on-aws]]
|
||||
|
||||
@@ -1,34 +1,34 @@
|
||||
---
|
||||
title: "AdsPower"
|
||||
type: entity
|
||||
tags: [fingerprint-browser, multi-account, browser-automation]
|
||||
last_updated: 2025-12-31
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- AdsPower 指纹浏览器
|
||||
- adspower
|
||||
|
||||
## Overview
|
||||
AdsPower 是一款专为企业用户设计的多账号指纹浏览器，通过模拟不同设备指纹、网络环境实现浏览器环境隔离，广泛用于跨境电商、社媒营销、账号矩阵运营等场景。
|
||||
|
||||
## Key Features
|
||||
- **指纹隔离**：模拟不同操作系统（Windows、macOS、Linux）、浏览器版本（Chrome、Firefox）、屏幕分辨率、时区、语言等参数
|
||||
- **账号矩阵管理**：批量创建和管理多个独立浏览器环境，每个环境配置独立代理IP
|
||||
- **支持谷歌授权登录**：可直接导入 Google 授权配置文件
|
||||
- **免费额度**：普通用户可免费使用 5 个浏览器环境
|
||||
|
||||
## Claude Pro Registration Use Case
|
||||
在 Claude Pro 注册流程中，AdsPower 用于：
|
||||
1. 创建独立浏览器环境，模拟美国 Windows + Chrome 131 环境
|
||||
2. 为每个环境配置独立 SOCKS5 代理IP
|
||||
3. 隔离不同账号的浏览器指纹，防止关联封号
|
||||
4. 支持导入已有 Google 账号直接登录 Claude
|
||||
|
||||
## Related
|
||||
- [[指纹浏览器]]
|
||||
- [[SOCKS5代理]]
|
||||
- [[IP纯净度]]
|
||||
|
||||
## 来源
|
||||
- [[如何用指纹浏览器安全注册并订阅claude-pro会员全攻略]]
|
||||
---
|
||||
title: "AdsPower"
|
||||
type: entity
|
||||
tags: [fingerprint-browser, multi-account, browser-automation]
|
||||
last_updated: 2025-12-31
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- AdsPower 指纹浏览器
|
||||
- adspower
|
||||
|
||||
## Overview
|
||||
AdsPower 是一款专为企业用户设计的多账号指纹浏览器，通过模拟不同设备指纹、网络环境实现浏览器环境隔离，广泛用于跨境电商、社媒营销、账号矩阵运营等场景。
|
||||
|
||||
## Key Features
|
||||
- **指纹隔离**：模拟不同操作系统（Windows、macOS、Linux）、浏览器版本（Chrome、Firefox）、屏幕分辨率、时区、语言等参数
|
||||
- **账号矩阵管理**：批量创建和管理多个独立浏览器环境，每个环境配置独立代理IP
|
||||
- **支持谷歌授权登录**：可直接导入 Google 授权配置文件
|
||||
- **免费额度**：普通用户可免费使用 5 个浏览器环境
|
||||
|
||||
## Claude Pro Registration Use Case
|
||||
在 Claude Pro 注册流程中，AdsPower 用于：
|
||||
1. 创建独立浏览器环境，模拟美国 Windows + Chrome 131 环境
|
||||
2. 为每个环境配置独立 SOCKS5 代理IP
|
||||
3. 隔离不同账号的浏览器指纹，防止关联封号
|
||||
4. 支持导入已有 Google 账号直接登录 Claude
|
||||
|
||||
## Related
|
||||
- [[指纹浏览器]]
|
||||
- [[SOCKS5代理]]
|
||||
- [[IP纯净度]]
|
||||
|
||||
## 来源
|
||||
- [[如何用指纹浏览器安全注册并订阅claude-pro会员全攻略]]
|
||||
|
||||
@@ -1,52 +1,52 @@
|
||||
---
|
||||
title: "Alertmanager"
|
||||
type: entity
|
||||
tags: [monitoring, alerting, prometheus, devops]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Alertmanager — Prometheus 告警分发组件
|
||||
|
||||
**官方网址：** https://prometheus.io/docs/alerting/latest/alertmanager/
|
||||
|
||||
**类型：** 开源项目 / 告警分发系统
|
||||
|
||||
**别名：**
|
||||
- prometheus-alertmanager
|
||||
- Alertmanager
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Alertmanager 是 Prometheus 生态中的告警分发组件，负责接收 Prometheus Server 发送的告警，进行抑制（inhibition）、分组（grouping）处理后路由到邮件、Slack、PagerDuty、webhook 等通知渠道。
|
||||
|
||||
**核心功能：**
|
||||
- **抑制（Inhibition）：** 当某条告警触发时，自动抑制相关联的其他告警
|
||||
- **分组（Grouping）：** 将相似告警合并为一条通知，减少告警风暴
|
||||
- **静默（Silence）：** 临时屏蔽特定告警
|
||||
- **路由（Routing）：** 基于标签匹配将告警路由到不同接收人
|
||||
|
||||
**配置格式：** YAML 格式的 `config.yml`
|
||||
|
||||
**典型部署：**
|
||||
- Docker: `prom/alertmanager:latest`
|
||||
- 端口：`9093`
|
||||
- Prometheus 配置中通过 `alerting.alertmanagers` 指定 targets
|
||||
|
||||
**支持的通知渠道：**
|
||||
- Email
|
||||
- Slack
|
||||
- PagerDuty
|
||||
- OpsGenie
|
||||
- WeChat
|
||||
- Telegram
|
||||
- Webhook（通用 HTTP）
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
---
|
||||
title: "Alertmanager"
|
||||
type: entity
|
||||
tags: [monitoring, alerting, prometheus, devops]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Alertmanager — Prometheus 告警分发组件
|
||||
|
||||
**官方网址：** https://prometheus.io/docs/alerting/latest/alertmanager/
|
||||
|
||||
**类型：** 开源项目 / 告警分发系统
|
||||
|
||||
**别名：**
|
||||
- prometheus-alertmanager
|
||||
- Alertmanager
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Alertmanager 是 Prometheus 生态中的告警分发组件，负责接收 Prometheus Server 发送的告警，进行抑制（inhibition）、分组（grouping）处理后路由到邮件、Slack、PagerDuty、webhook 等通知渠道。
|
||||
|
||||
**核心功能：**
|
||||
- **抑制（Inhibition）：** 当某条告警触发时，自动抑制相关联的其他告警
|
||||
- **分组（Grouping）：** 将相似告警合并为一条通知，减少告警风暴
|
||||
- **静默（Silence）：** 临时屏蔽特定告警
|
||||
- **路由（Routing）：** 基于标签匹配将告警路由到不同接收人
|
||||
|
||||
**配置格式：** YAML 格式的 `config.yml`
|
||||
|
||||
**典型部署：**
|
||||
- Docker: `prom/alertmanager:latest`
|
||||
- 端口：`9093`
|
||||
- Prometheus 配置中通过 `alerting.alertmanagers` 指定 targets
|
||||
|
||||
**支持的通知渠道：**
|
||||
- Email
|
||||
- Slack
|
||||
- PagerDuty
|
||||
- OpsGenie
|
||||
- WeChat
|
||||
- Telegram
|
||||
- Webhook（通用 HTTP）
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
@@ -1,20 +1,20 @@
|
||||
---
|
||||
title: "Alist"
|
||||
type: entity
|
||||
tags: []
|
||||
last_updated: 2026-05-30
|
||||
---
|
||||
|
||||
## Alist
|
||||
|
||||
开源网盘聚合工具（WebDAV/File listing program），支持将多个云存储（阿里云盘、百度网盘、Google Drive、OneDrive、S3 等）统一挂载为本地文件系统访问。
|
||||
|
||||
## Aliases
|
||||
- AList
|
||||
- aList
|
||||
|
||||
## Overview
|
||||
Alist 通过 Web 界面聚合多个网盘/云存储服务，提供统一的文件浏览和下载入口。用户无需在各平台间切换，通过 Alist 即可访问所有挂载的存储。支持 Docker 部署，镜像名为 `xiaoyaliu/alist`。
|
||||
|
||||
## Key References
|
||||
- [[如何传输Docker images 并且在另一个Docker安装]] — 在 Synology NAS 上通过 `docker load` 导入 xiaoyaliu/alist 镜像的示例操作
|
||||
---
|
||||
title: "Alist"
|
||||
type: entity
|
||||
tags: []
|
||||
last_updated: 2026-05-30
|
||||
---
|
||||
|
||||
## Alist
|
||||
|
||||
开源网盘聚合工具（WebDAV/File listing program），支持将多个云存储（阿里云盘、百度网盘、Google Drive、OneDrive、S3 等）统一挂载为本地文件系统访问。
|
||||
|
||||
## Aliases
|
||||
- AList
|
||||
- aList
|
||||
|
||||
## Overview
|
||||
Alist 通过 Web 界面聚合多个网盘/云存储服务，提供统一的文件浏览和下载入口。用户无需在各平台间切换，通过 Alist 即可访问所有挂载的存储。支持 Docker 部署，镜像名为 `xiaoyaliu/alist`。
|
||||
|
||||
## Key References
|
||||
- [[如何传输Docker images 并且在另一个Docker安装]] — 在 Synology NAS 上通过 `docker load` 导入 xiaoyaliu/alist 镜像的示例操作
|
||||
|
||||
@@ -1,28 +1,28 @@
|
||||
---
|
||||
title: "Anthropic"
|
||||
type: entity
|
||||
tags: ["llm-provider", "anthropic"]
|
||||
sources: ["engineering-autonomous-optimization-architect"]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- Anthropic
|
||||
- Anthropic PBC
|
||||
|
||||
## Definition
|
||||
Anthropic 是主要的 LLM Provider，提供 Claude 系列模型（Claude Opus、Claude Sonnet、Claude Haiku 等）。在 [[AutonomousOptimizationArchitect]] 系统中作为高精度基准模型，其输出常被用作 [[LLMasJudge]] 评估其他模型时的参照标准。
|
||||
|
||||
## Role in LLM Routing
|
||||
- Claude Opus 常作为高精度基准——如果其他模型要替代 Claude，必须达到其 98%+ 精度
|
||||
- Claude Sonnet/Haiku 提供性价比选项，供 [[AutonomousOptimizationArchitect]] 按任务难度分配
|
||||
- Anthropic API 不可用时触发 [[CircuitBreaker]] 切换至 [[OpenAI]] 或 [[GoogleGemini]]
|
||||
|
||||
## Key Properties
|
||||
- **Token 成本**：$3-15 / 1M tokens
|
||||
- **延迟**：低至中等
|
||||
- **常见用途**：复杂推理、长文本分析、安全敏感任务
|
||||
|
||||
## Connections
|
||||
- [[OpenAI]] — 同为 LLM Provider，共同参与 [[SemanticRouting]]
|
||||
- [[GoogleGemini]] — 在成本优化场景中与 Gemini Flash 形成对比
|
||||
---
|
||||
title: "Anthropic"
|
||||
type: entity
|
||||
tags: ["llm-provider", "anthropic"]
|
||||
sources: ["engineering-autonomous-optimization-architect"]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- Anthropic
|
||||
- Anthropic PBC
|
||||
|
||||
## Definition
|
||||
Anthropic 是主要的 LLM Provider，提供 Claude 系列模型（Claude Opus、Claude Sonnet、Claude Haiku 等）。在 [[AutonomousOptimizationArchitect]] 系统中作为高精度基准模型，其输出常被用作 [[LLMasJudge]] 评估其他模型时的参照标准。
|
||||
|
||||
## Role in LLM Routing
|
||||
- Claude Opus 常作为高精度基准——如果其他模型要替代 Claude，必须达到其 98%+ 精度
|
||||
- Claude Sonnet/Haiku 提供性价比选项，供 [[AutonomousOptimizationArchitect]] 按任务难度分配
|
||||
- Anthropic API 不可用时触发 [[CircuitBreaker]] 切换至 [[OpenAI]] 或 [[GoogleGemini]]
|
||||
|
||||
## Key Properties
|
||||
- **Token 成本**：$3-15 / 1M tokens
|
||||
- **延迟**：低至中等
|
||||
- **常见用途**：复杂推理、长文本分析、安全敏感任务
|
||||
|
||||
## Connections
|
||||
- [[OpenAI]] — 同为 LLM Provider，共同参与 [[SemanticRouting]]
|
||||
- [[GoogleGemini]] — 在成本优化场景中与 Gemini Flash 形成对比
|
||||
|
||||
@@ -1,42 +1,42 @@
|
||||
---
|
||||
title: Azure (Microsoft Azure)
|
||||
type: entity
|
||||
tags: [Cloud, Provider, Public-Cloud]
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
---
|
||||
|
||||
# Azure (Microsoft Azure)
|
||||
|
||||
**Microsoft Azure** is a cloud computing platform operated by Microsoft, providing a broad range of services for application and workload hosting.
|
||||
|
||||
## Overview
|
||||
|
||||
Azure is one of the three major public cloud providers, particularly strong in enterprise environments with Microsoft ecosystem integration.
|
||||
|
||||
## Key Services Referenced
|
||||
|
||||
| Category | Services |
|
||||
|----------|----------|
|
||||
| Compute | Virtual Machines, Azure Functions |
|
||||
| Storage | Blob Storage, Azure Files |
|
||||
| Database | Azure SQL, Cosmos DB |
|
||||
| AI/ML | Azure AI, Azure OpenAI Service |
|
||||
| Analytics | Synapse, Databricks |
|
||||
| Enterprise | Active Directory, Microsoft 365 integration |
|
||||
|
||||
## Multi-Cloud Context
|
||||
|
||||
Azure is commonly used alongside AWS and Google Cloud in multi-cloud strategies:
|
||||
- **Enterprise workloads** — Strong Windows Server and SQL Server integration
|
||||
- **AI services** — Azure OpenAI Service for enterprise AI applications
|
||||
- **Hybrid cloud** — Deep integration with on-premises Windows environments
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Multi-Cloud-Strategy]] — Azure as one of multiple providers
|
||||
- [[Cloud-Native]] — Building on Azure-native services
|
||||
- [[FinOps]] — Managing Azure costs
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]]
|
||||
---
|
||||
title: Azure (Microsoft Azure)
|
||||
type: entity
|
||||
tags: [Cloud, Provider, Public-Cloud]
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
---
|
||||
|
||||
# Azure (Microsoft Azure)
|
||||
|
||||
**Microsoft Azure** is a cloud computing platform operated by Microsoft, providing a broad range of services for application and workload hosting.
|
||||
|
||||
## Overview
|
||||
|
||||
Azure is one of the three major public cloud providers, particularly strong in enterprise environments with Microsoft ecosystem integration.
|
||||
|
||||
## Key Services Referenced
|
||||
|
||||
| Category | Services |
|
||||
|----------|----------|
|
||||
| Compute | Virtual Machines, Azure Functions |
|
||||
| Storage | Blob Storage, Azure Files |
|
||||
| Database | Azure SQL, Cosmos DB |
|
||||
| AI/ML | Azure AI, Azure OpenAI Service |
|
||||
| Analytics | Synapse, Databricks |
|
||||
| Enterprise | Active Directory, Microsoft 365 integration |
|
||||
|
||||
## Multi-Cloud Context
|
||||
|
||||
Azure is commonly used alongside AWS and Google Cloud in multi-cloud strategies:
|
||||
- **Enterprise workloads** — Strong Windows Server and SQL Server integration
|
||||
- **AI services** — Azure OpenAI Service for enterprise AI applications
|
||||
- **Hybrid cloud** — Deep integration with on-premises Windows environments
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Multi-Cloud-Strategy]] — Azure as one of multiple providers
|
||||
- [[Cloud-Native]] — Building on Azure-native services
|
||||
- [[FinOps]] — Managing Azure costs
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]]
|
||||
|
||||
@@ -1,53 +1,53 @@
|
||||
---
|
||||
title: "Blackbox Exporter"
|
||||
type: entity
|
||||
tags: [monitoring, prometheus, blackbox, probe, devops]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Blackbox Exporter — Prometheus 黑盒探测 exporter
|
||||
|
||||
**官方网址：** https://prometheus.io/docs/guides/node-exporter/
|
||||
|
||||
**类型：** 开源项目 / Prometheus Exporter
|
||||
|
||||
**别名：**
|
||||
- blackbox_exporter
|
||||
- prometheus blackbox
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Blackbox Exporter 是 Prometheus 官方提供的黑盒探测 exporter，通过 HTTP、HTTPS、DNS、TCP、ICMP 等协议探测目标端点的可用性、响应时间和 TLS 证书状态，支持细粒度的服务层监控。
|
||||
|
||||
**支持模块：**
|
||||
- `http_2xx` — HTTP/HTTPS 可用性探测
|
||||
- `https_2xx` — 仅 HTTPS 探测
|
||||
- `dns` — DNS 解析探测
|
||||
- `tcp` — TCP 端口探测
|
||||
- `icmp` — ICMP ping 探测
|
||||
|
||||
**采集指标示例：**
|
||||
- `probe_success` — 探测是否成功（0/1）
|
||||
- `probe_duration_seconds` — 探测耗时（秒）
|
||||
- `probe_ssl_earliest_cert_expiry` — TLS 证书到期时间戳
|
||||
- `probe_http_status_code` — HTTP 响应码
|
||||
- `probe_dns_lookup_duration_seconds` — DNS 解析耗时
|
||||
|
||||
**典型部署：**
|
||||
- Docker: `prom/blackbox-exporter:latest`
|
||||
- 端口：`9115`
|
||||
- Prometheus 配置需使用 `metrics_path: /probe` 和 `params: module: [http_2xx]`
|
||||
|
||||
**关键告警规则示例：**
|
||||
- 站点不可达: `probe_success == 0`（持续 2 分钟）
|
||||
- TLS 证书到期: `probe_ssl_earliest_cert_expiry - time() < 86400 * 14`（剩余 < 14 天）
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
---
|
||||
title: "Blackbox Exporter"
|
||||
type: entity
|
||||
tags: [monitoring, prometheus, blackbox, probe, devops]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Blackbox Exporter — Prometheus 黑盒探测 exporter
|
||||
|
||||
**官方网址：** https://prometheus.io/docs/guides/node-exporter/
|
||||
|
||||
**类型：** 开源项目 / Prometheus Exporter
|
||||
|
||||
**别名：**
|
||||
- blackbox_exporter
|
||||
- prometheus blackbox
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Blackbox Exporter 是 Prometheus 官方提供的黑盒探测 exporter，通过 HTTP、HTTPS、DNS、TCP、ICMP 等协议探测目标端点的可用性、响应时间和 TLS 证书状态，支持细粒度的服务层监控。
|
||||
|
||||
**支持模块：**
|
||||
- `http_2xx` — HTTP/HTTPS 可用性探测
|
||||
- `https_2xx` — 仅 HTTPS 探测
|
||||
- `dns` — DNS 解析探测
|
||||
- `tcp` — TCP 端口探测
|
||||
- `icmp` — ICMP ping 探测
|
||||
|
||||
**采集指标示例：**
|
||||
- `probe_success` — 探测是否成功（0/1）
|
||||
- `probe_duration_seconds` — 探测耗时（秒）
|
||||
- `probe_ssl_earliest_cert_expiry` — TLS 证书到期时间戳
|
||||
- `probe_http_status_code` — HTTP 响应码
|
||||
- `probe_dns_lookup_duration_seconds` — DNS 解析耗时
|
||||
|
||||
**典型部署：**
|
||||
- Docker: `prom/blackbox-exporter:latest`
|
||||
- 端口：`9115`
|
||||
- Prometheus 配置需使用 `metrics_path: /probe` 和 `params: module: [http_2xx]`
|
||||
|
||||
**关键告警规则示例：**
|
||||
- 站点不可达: `probe_success == 0`（持续 2 分钟）
|
||||
- TLS 证书到期: `probe_ssl_earliest_cert_expiry - time() < 86400 * 14`（剩余 < 14 天）
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
@@ -1,65 +1,65 @@
|
||||
---
|
||||
title: "Clonezilla"
|
||||
tags: [backup, opensource, disk-imaging, dr]
|
||||
date: 2026-04-28
|
||||
---
|
||||
|
||||
# Clonezilla (再生龙)
|
||||
|
||||
## Aliases
|
||||
- Clonezilla
|
||||
- 再生龙
|
||||
|
||||
## Definition
|
||||
Clonezilla 是一款开源的磁盘镜像/克隆工具，类似于 Norton Ghost，提供完整的系统级备份与还原功能。支持将整个磁盘或单个分区备份为镜像文件，存储到本地磁盘、NFS、SMB、SFTP 等多种目标位置。
|
||||
|
||||
## Core Capabilities
|
||||
- **savedisk**: 将整个磁盘备份为镜像文件
|
||||
- **saveparts**: 仅备份指定分区
|
||||
- **restoredisk**: 从镜像还原整个磁盘
|
||||
- **restoreparts**: 从镜像还原指定分区
|
||||
- **device-image 模式**: 将磁盘映射为镜像文件存储（区别于直接磁盘对磁盘克隆）
|
||||
|
||||
## Key Features
|
||||
| 特性 | 说明 |
|
||||
|------|------|
|
||||
| 备份介质 | 本地磁盘、外置硬盘、NFS、SMB、SFTP、SSH |
|
||||
| 压缩选项 | -z1p (高压缩率), -z2p, -z3p, -z4p |
|
||||
| 文件系统支持 | ext2/3/4, NTFS, FAT, HFS+, XFS, Btrfs 等 |
|
||||
| 分区表支持 | MBR 和 GPT |
|
||||
| 模式 | Beginner（初学者）/ Expert（专家） |
|
||||
| 启动介质 | Live CD, Live USB, PXE 网络启动 |
|
||||
|
||||
## Backup Workflow
|
||||
```
|
||||
1. 制作 Clonezilla 启动 U 盘 (Rufus ISO 模式)
|
||||
2. 从 U 盘启动源机器，进入 Clonezilla Live
|
||||
3. 选择 device-image 模式
|
||||
4. 挂载 NAS/外置硬盘作为备份目标
|
||||
5. 选择 savedisk → 选择源磁盘 → 配置参数
|
||||
6. 等待镜像生成
|
||||
```
|
||||
|
||||
## Restore Workflow
|
||||
```
|
||||
1. 从 U 盘启动目标机器（或原机器）
|
||||
2. 进入 Clonezilla，选择 device-image 模式
|
||||
3. 挂载存储镜像的 NAS/外置硬盘
|
||||
4. 选择 restoredisk → 选择镜像文件 → 选择目标磁盘
|
||||
5. 确认覆盖 → 等待还原完成 → 系统即刻复活
|
||||
```
|
||||
|
||||
## Related Concepts
|
||||
- [[全盘镜像备份]] — Clonezilla 实现的备份方法
|
||||
- [[NFS网络备份]] — Clonezilla 推荐的网络存储方案
|
||||
- [[裸机恢复]] — Clonezilla 支持的核心场景
|
||||
- [[增量备份]] — Clonezilla 镜像备份 vs rsync 增量备份（互补方案）
|
||||
|
||||
## Related Sources
|
||||
- [[clonezilla对ubuntu-server进行全盘镜像备份]]
|
||||
- [[ubuntu服务器通过rsync实现日常增量备份]] — rsync 增量备份与 Clonezilla 全盘镜像形成双层保护体系
|
||||
|
||||
## Related Entities
|
||||
- [[Rufus]] — U 盘启动盘制作工具
|
||||
- [[Synology-NAS]] — 备份镜像存储目标
|
||||
- [[HP ZBook]] — 源笔记本设备
|
||||
---
|
||||
title: "Clonezilla"
|
||||
tags: [backup, opensource, disk-imaging, dr]
|
||||
date: 2026-04-28
|
||||
---
|
||||
|
||||
# Clonezilla (再生龙)
|
||||
|
||||
## Aliases
|
||||
- Clonezilla
|
||||
- 再生龙
|
||||
|
||||
## Definition
|
||||
Clonezilla 是一款开源的磁盘镜像/克隆工具，类似于 Norton Ghost，提供完整的系统级备份与还原功能。支持将整个磁盘或单个分区备份为镜像文件，存储到本地磁盘、NFS、SMB、SFTP 等多种目标位置。
|
||||
|
||||
## Core Capabilities
|
||||
- **savedisk**: 将整个磁盘备份为镜像文件
|
||||
- **saveparts**: 仅备份指定分区
|
||||
- **restoredisk**: 从镜像还原整个磁盘
|
||||
- **restoreparts**: 从镜像还原指定分区
|
||||
- **device-image 模式**: 将磁盘映射为镜像文件存储（区别于直接磁盘对磁盘克隆）
|
||||
|
||||
## Key Features
|
||||
| 特性 | 说明 |
|
||||
|------|------|
|
||||
| 备份介质 | 本地磁盘、外置硬盘、NFS、SMB、SFTP、SSH |
|
||||
| 压缩选项 | -z1p (高压缩率), -z2p, -z3p, -z4p |
|
||||
| 文件系统支持 | ext2/3/4, NTFS, FAT, HFS+, XFS, Btrfs 等 |
|
||||
| 分区表支持 | MBR 和 GPT |
|
||||
| 模式 | Beginner（初学者）/ Expert（专家） |
|
||||
| 启动介质 | Live CD, Live USB, PXE 网络启动 |
|
||||
|
||||
## Backup Workflow
|
||||
```
|
||||
1. 制作 Clonezilla 启动 U 盘 (Rufus ISO 模式)
|
||||
2. 从 U 盘启动源机器，进入 Clonezilla Live
|
||||
3. 选择 device-image 模式
|
||||
4. 挂载 NAS/外置硬盘作为备份目标
|
||||
5. 选择 savedisk → 选择源磁盘 → 配置参数
|
||||
6. 等待镜像生成
|
||||
```
|
||||
|
||||
## Restore Workflow
|
||||
```
|
||||
1. 从 U 盘启动目标机器（或原机器）
|
||||
2. 进入 Clonezilla，选择 device-image 模式
|
||||
3. 挂载存储镜像的 NAS/外置硬盘
|
||||
4. 选择 restoredisk → 选择镜像文件 → 选择目标磁盘
|
||||
5. 确认覆盖 → 等待还原完成 → 系统即刻复活
|
||||
```
|
||||
|
||||
## Related Concepts
|
||||
- [[全盘镜像备份]] — Clonezilla 实现的备份方法
|
||||
- [[NFS网络备份]] — Clonezilla 推荐的网络存储方案
|
||||
- [[裸机恢复]] — Clonezilla 支持的核心场景
|
||||
- [[增量备份]] — Clonezilla 镜像备份 vs rsync 增量备份（互补方案）
|
||||
|
||||
## Related Sources
|
||||
- [[clonezilla对ubuntu-server进行全盘镜像备份]]
|
||||
- [[ubuntu服务器通过rsync实现日常增量备份]] — rsync 增量备份与 Clonezilla 全盘镜像形成双层保护体系
|
||||
|
||||
## Related Entities
|
||||
- [[Rufus]] — U 盘启动盘制作工具
|
||||
- [[Synology-NAS]] — 备份镜像存储目标
|
||||
- [[HP ZBook]] — 源笔记本设备
|
||||
|
||||
@@ -1,61 +1,61 @@
|
||||
# DevOps Maturity Model
|
||||
|
||||
## Source
|
||||
- [[sources/cloud-devop-maturity-guideline.md]]
|
||||
- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]]
|
||||
|
||||
## Summary
|
||||
|
||||
A framework for evaluating an organization's progress in adopting DevOps practices, typically ranging from ad-hoc processes to highly optimized and automated environments. The model defines **five maturity stages**:
|
||||
|
||||
| Stage | Name | Key Characteristics |
|
||||
|-------|------|---------------------|
|
||||
| Phase 1 | Initial/Ad-Hoc | Siloed teams, waterfall approach, manual infrastructure, reactive monitoring, security only at release |
|
||||
| Phase 2 | DevOps in Pockets | Small cross-functional teams, Agile introduction, version control, superficial automation, unit/integration testing |
|
||||
| Phase 3 | Automated and Defined | Standardized processes, most infrastructure automated, security integrated into development process |
|
||||
| Phase 4 | Highly Optimized | CI pipeline, immutable infrastructure, MVP and tech debt management, continuous security monitoring |
|
||||
| Phase 5 | Fully Mature | Self-sufficient full-stack teams, multiple daily deployments, zero human intervention in pipeline |
|
||||
|
||||
## Key Focus Areas
|
||||
|
||||
1. **Culture and Strategy** — Teamwork, transparency, customer-centric mindset
|
||||
2. **Automation** — AutoDevOps for continuous delivery and deployment
|
||||
3. **Structure and Process** — Standardized, small-batch, transparent processes
|
||||
4. **Collaboration and Sharing** — Cohesive teams leveraging diverse skill sets
|
||||
5. **Technology** — Tool selection aligned with team needs
|
||||
|
||||
## Quality Criteria
|
||||
|
||||
- Assessment criteria (standards for evaluating maturity)
|
||||
- Five maturity levels
|
||||
- Core DevOps practices (release management, CI/CD, IaC, security)
|
||||
- Relevant metrics (deployment frequency, MTTR, change failure rate)
|
||||
- Cultural guides
|
||||
- Tools and technologies
|
||||
- Roles and responsibilities
|
||||
|
||||
## Business Benefits
|
||||
|
||||
- Quicker adjustment to market changes
|
||||
- Capability to seize new opportunities
|
||||
- Better scalability via IaC
|
||||
- Enhanced operational performance
|
||||
- Faster delivery times
|
||||
- Improved quality via continuous monitoring and feedback
|
||||
|
||||
## Security Integration (DevSecOps)
|
||||
|
||||
The model emphasizes merging development, operations, and security into a unified process. Security progression: ad-hoc compliance scans → separate security team → security in design/architecture discussions → security updates in product workflow → preventing non-compliant code from production.
|
||||
|
||||
## Related Concepts
|
||||
- [[concepts/DevOps-Maturity]]
|
||||
- [[concepts/DORA-Metrics]]
|
||||
- [[concepts/DevSecOps]]
|
||||
- [[concepts/CI-CD-Pipeline]]
|
||||
- [[concepts/Infrastructure-as-Code]]
|
||||
- [[concepts/Continuous-Deployment]]
|
||||
|
||||
## Ingested
|
||||
- Date: 2026-04-21 (initial)
|
||||
- Date: 2026-04-24 (updated with Phase 1-5 details)
|
||||
- Date: 2026-04-26 (补充 DevOps 成熟度衡量指标、业务收益、安全集成的详细内容)
|
||||
# DevOps Maturity Model
|
||||
|
||||
## Source
|
||||
- [[sources/cloud-devop-maturity-guideline.md]]
|
||||
- [[sources/devops-maturity-model-from-traditional-it-to-advanced-devops.md]]
|
||||
|
||||
## Summary
|
||||
|
||||
A framework for evaluating an organization's progress in adopting DevOps practices, typically ranging from ad-hoc processes to highly optimized and automated environments. The model defines **five maturity stages**:
|
||||
|
||||
| Stage | Name | Key Characteristics |
|
||||
|-------|------|---------------------|
|
||||
| Phase 1 | Initial/Ad-Hoc | Siloed teams, waterfall approach, manual infrastructure, reactive monitoring, security only at release |
|
||||
| Phase 2 | DevOps in Pockets | Small cross-functional teams, Agile introduction, version control, superficial automation, unit/integration testing |
|
||||
| Phase 3 | Automated and Defined | Standardized processes, most infrastructure automated, security integrated into development process |
|
||||
| Phase 4 | Highly Optimized | CI pipeline, immutable infrastructure, MVP and tech debt management, continuous security monitoring |
|
||||
| Phase 5 | Fully Mature | Self-sufficient full-stack teams, multiple daily deployments, zero human intervention in pipeline |
|
||||
|
||||
## Key Focus Areas
|
||||
|
||||
1. **Culture and Strategy** — Teamwork, transparency, customer-centric mindset
|
||||
2. **Automation** — AutoDevOps for continuous delivery and deployment
|
||||
3. **Structure and Process** — Standardized, small-batch, transparent processes
|
||||
4. **Collaboration and Sharing** — Cohesive teams leveraging diverse skill sets
|
||||
5. **Technology** — Tool selection aligned with team needs
|
||||
|
||||
## Quality Criteria
|
||||
|
||||
- Assessment criteria (standards for evaluating maturity)
|
||||
- Five maturity levels
|
||||
- Core DevOps practices (release management, CI/CD, IaC, security)
|
||||
- Relevant metrics (deployment frequency, MTTR, change failure rate)
|
||||
- Cultural guides
|
||||
- Tools and technologies
|
||||
- Roles and responsibilities
|
||||
|
||||
## Business Benefits
|
||||
|
||||
- Quicker adjustment to market changes
|
||||
- Capability to seize new opportunities
|
||||
- Better scalability via IaC
|
||||
- Enhanced operational performance
|
||||
- Faster delivery times
|
||||
- Improved quality via continuous monitoring and feedback
|
||||
|
||||
## Security Integration (DevSecOps)
|
||||
|
||||
The model emphasizes merging development, operations, and security into a unified process. Security progression: ad-hoc compliance scans → separate security team → security in design/architecture discussions → security updates in product workflow → preventing non-compliant code from production.
|
||||
|
||||
## Related Concepts
|
||||
- [[concepts/DevOps-Maturity]]
|
||||
- [[concepts/DORA-Metrics]]
|
||||
- [[concepts/DevSecOps]]
|
||||
- [[concepts/CI-CD-Pipeline]]
|
||||
- [[concepts/Infrastructure-as-Code]]
|
||||
- [[concepts/Continuous-Deployment]]
|
||||
|
||||
## Ingested
|
||||
- Date: 2026-04-21 (initial)
|
||||
- Date: 2026-04-24 (updated with Phase 1-5 details)
|
||||
- Date: 2026-04-26 (补充 DevOps 成熟度衡量指标、业务收益、安全集成的详细内容)
|
||||
|
||||
@@ -1,31 +1,31 @@
|
||||
---
|
||||
title: "Docker"
|
||||
type: entity
|
||||
tags: []
|
||||
last_updated: 2026-05-30
|
||||
---
|
||||
|
||||
## Docker
|
||||
|
||||
开源容器化平台（Containerization Platform），用于打包、分发和运行应用程序及其依赖。
|
||||
|
||||
## Aliases
|
||||
- Docker Engine
|
||||
- Docker Desktop
|
||||
|
||||
## Overview
|
||||
Docker 通过容器（Container）将应用程序及其运行时环境打包为独立镜像，支持跨平台一致部署。核心组件包括：
|
||||
- **Dockerfile**：定义镜像构建步骤
|
||||
- **docker pull/push**：从 Registry 拉取/推送镜像
|
||||
- **docker save/load**：镜像离线打包（tar）与导入
|
||||
- **docker run**：基于镜像启动容器
|
||||
- **docker compose**：多容器编排
|
||||
|
||||
## Key References
|
||||
- [[如何在Ubuntu Server安装 Docker & Docker Compose]] — Docker + Docker Compose 安装
|
||||
- [[如何传输Docker images 并且在另一个Docker安装]] — 镜像离线迁移（save/load）
|
||||
- [[用Docker安装Portainer]] — 容器管理面板
|
||||
- [[用Docker安装Jellyfin]] — 媒体服务器
|
||||
- [[用Docker安装Homarr]] — 个人导航仪表盘
|
||||
- [[用Docker安装Apache Superset]] — BI 可视化平台
|
||||
- [[如何删除旧的废弃的 Docker Container + Volume]] — 容器清理
|
||||
---
|
||||
title: "Docker"
|
||||
type: entity
|
||||
tags: []
|
||||
last_updated: 2026-05-30
|
||||
---
|
||||
|
||||
## Docker
|
||||
|
||||
开源容器化平台（Containerization Platform），用于打包、分发和运行应用程序及其依赖。
|
||||
|
||||
## Aliases
|
||||
- Docker Engine
|
||||
- Docker Desktop
|
||||
|
||||
## Overview
|
||||
Docker 通过容器（Container）将应用程序及其运行时环境打包为独立镜像，支持跨平台一致部署。核心组件包括：
|
||||
- **Dockerfile**：定义镜像构建步骤
|
||||
- **docker pull/push**：从 Registry 拉取/推送镜像
|
||||
- **docker save/load**：镜像离线打包（tar）与导入
|
||||
- **docker run**：基于镜像启动容器
|
||||
- **docker compose**：多容器编排
|
||||
|
||||
## Key References
|
||||
- [[如何在Ubuntu Server安装 Docker & Docker Compose]] — Docker + Docker Compose 安装
|
||||
- [[如何传输Docker images 并且在另一个Docker安装]] — 镜像离线迁移（save/load）
|
||||
- [[用Docker安装Portainer]] — 容器管理面板
|
||||
- [[用Docker安装Jellyfin]] — 媒体服务器
|
||||
- [[用Docker安装Homarr]] — 个人导航仪表盘
|
||||
- [[用Docker安装Apache Superset]] — BI 可视化平台
|
||||
- [[如何删除旧的废弃的 Docker Container + Volume]] — 容器清理
|
||||
|
||||
@@ -1,43 +1,43 @@
|
||||
---
|
||||
title: Google Cloud Platform (GCP)
|
||||
type: entity
|
||||
tags: [Cloud, Provider, Public-Cloud]
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
---
|
||||
|
||||
# Google Cloud Platform (GCP)
|
||||
|
||||
**Google Cloud Platform (GCP)** is Google's cloud computing platform, providing infrastructure and application services with strengths in AI/ML, data analytics, and container technologies.
|
||||
|
||||
## Overview
|
||||
|
||||
GCP is one of the three major public cloud providers, particularly known for Kubernetes (originated at Google), data analytics, and machine learning capabilities.
|
||||
|
||||
## Key Services Referenced
|
||||
|
||||
| Category | Services |
|
||||
|----------|----------|
|
||||
| Compute | Compute Engine, Cloud Functions, GKE |
|
||||
| Storage | Cloud Storage, Filestore |
|
||||
| Database | Cloud SQL, BigQuery, Firestore, Spanner |
|
||||
| AI/ML | Vertex AI, TensorFlow, Gemini |
|
||||
| Analytics | BigQuery, Dataflow, Looker |
|
||||
| Networking | VPC, Cloud CDN, Cloud Load Balancing |
|
||||
|
||||
## Multi-Cloud Context
|
||||
|
||||
GCP is commonly used alongside AWS and Azure in multi-cloud strategies:
|
||||
- **Machine Learning** — Often preferred for ML/AI workloads (Vertex AI, TensorFlow)
|
||||
- **Data Analytics** — BigQuery for data warehousing and analytics
|
||||
- **Container-native** — GKE (Google Kubernetes Engine) for container orchestration
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Multi-Cloud-Strategy]] — GCP as one of multiple providers
|
||||
- [[Cloud-Native]] — Building on GCP-native services
|
||||
- [[Kubernetes]] — GKE as managed Kubernetes
|
||||
- [[FinOps]] — Managing GCP costs
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]]
|
||||
---
|
||||
title: Google Cloud Platform (GCP)
|
||||
type: entity
|
||||
tags: [Cloud, Provider, Public-Cloud]
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
---
|
||||
|
||||
# Google Cloud Platform (GCP)
|
||||
|
||||
**Google Cloud Platform (GCP)** is Google's cloud computing platform, providing infrastructure and application services with strengths in AI/ML, data analytics, and container technologies.
|
||||
|
||||
## Overview
|
||||
|
||||
GCP is one of the three major public cloud providers, particularly known for Kubernetes (originated at Google), data analytics, and machine learning capabilities.
|
||||
|
||||
## Key Services Referenced
|
||||
|
||||
| Category | Services |
|
||||
|----------|----------|
|
||||
| Compute | Compute Engine, Cloud Functions, GKE |
|
||||
| Storage | Cloud Storage, Filestore |
|
||||
| Database | Cloud SQL, BigQuery, Firestore, Spanner |
|
||||
| AI/ML | Vertex AI, TensorFlow, Gemini |
|
||||
| Analytics | BigQuery, Dataflow, Looker |
|
||||
| Networking | VPC, Cloud CDN, Cloud Load Balancing |
|
||||
|
||||
## Multi-Cloud Context
|
||||
|
||||
GCP is commonly used alongside AWS and Azure in multi-cloud strategies:
|
||||
- **Machine Learning** — Often preferred for ML/AI workloads (Vertex AI, TensorFlow)
|
||||
- **Data Analytics** — BigQuery for data warehousing and analytics
|
||||
- **Container-native** — GKE (Google Kubernetes Engine) for container orchestration
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Multi-Cloud-Strategy]] — GCP as one of multiple providers
|
||||
- [[Cloud-Native]] — Building on GCP-native services
|
||||
- [[Kubernetes]] — GKE as managed Kubernetes
|
||||
- [[FinOps]] — Managing GCP costs
|
||||
|
||||
## Sources
|
||||
|
||||
- [[sources/how-can-a-multi-cloud-strategy-transform-your-business-roi.md]]
|
||||
|
||||
@@ -1,30 +1,30 @@
|
||||
---
|
||||
title: "GoogleGemini"
|
||||
type: entity
|
||||
tags: ["llm-provider", "google", "gemini"]
|
||||
sources: ["engineering-autonomous-optimization-architect"]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- Gemini
|
||||
- Google Gemini
|
||||
- Gemini Flash
|
||||
- Gemini Pro
|
||||
|
||||
## Definition
|
||||
Google Gemini 是 Google 的 LLM 系列模型，涵盖从高性价比到高性能的多种版本。在 [[AutonomousOptimizationArchitect]] 系统中，Gemini Flash 因其极高的性价比（成本约为 Claude Opus 的 1/10）而被列为重要的路由目标。
|
||||
|
||||
## Role in LLM Routing
|
||||
- **Gemini Flash**：低成本高速度模型，如果精度达到基准的 98% 且成本远低于竞品，[[AutonomousOptimizationArchitect]] 会将流量自动路由至 Gemini
|
||||
- **Gemini Pro**：中端定位，提供能力与成本的平衡
|
||||
- 与 [[OpenAI]] 和 [[Anthropic]] 共同构成三足鼎立的 Provider 生态
|
||||
|
||||
## Key Properties
|
||||
- **Token 成本**：$0.075-0.5 / 1M tokens（Gemini Flash 极低）
|
||||
- **延迟**：低（Gemini Flash）
|
||||
- **优势**：极高的性价比，特别适合大规模、低成本推理
|
||||
|
||||
## Connections
|
||||
- [[OpenAI]] — 同为 LLM Provider
|
||||
- [[Anthropic]] — 高精度基准 Provider
|
||||
---
|
||||
title: "GoogleGemini"
|
||||
type: entity
|
||||
tags: ["llm-provider", "google", "gemini"]
|
||||
sources: ["engineering-autonomous-optimization-architect"]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- Gemini
|
||||
- Google Gemini
|
||||
- Gemini Flash
|
||||
- Gemini Pro
|
||||
|
||||
## Definition
|
||||
Google Gemini 是 Google 的 LLM 系列模型，涵盖从高性价比到高性能的多种版本。在 [[AutonomousOptimizationArchitect]] 系统中，Gemini Flash 因其极高的性价比（成本约为 Claude Opus 的 1/10）而被列为重要的路由目标。
|
||||
|
||||
## Role in LLM Routing
|
||||
- **Gemini Flash**：低成本高速度模型，如果精度达到基准的 98% 且成本远低于竞品，[[AutonomousOptimizationArchitect]] 会将流量自动路由至 Gemini
|
||||
- **Gemini Pro**：中端定位，提供能力与成本的平衡
|
||||
- 与 [[OpenAI]] 和 [[Anthropic]] 共同构成三足鼎立的 Provider 生态
|
||||
|
||||
## Key Properties
|
||||
- **Token 成本**：$0.075-0.5 / 1M tokens（Gemini Flash 极低）
|
||||
- **延迟**：低（Gemini Flash）
|
||||
- **优势**：极高的性价比，特别适合大规模、低成本推理
|
||||
|
||||
## Connections
|
||||
- [[OpenAI]] — 同为 LLM Provider
|
||||
- [[Anthropic]] — 高精度基准 Provider
|
||||
|
||||
@@ -1,47 +1,47 @@
|
||||
---
|
||||
title: "Grafana"
|
||||
type: entity
|
||||
tags: [visualization, monitoring, dashboards, observability]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Grafana — 可视化与告警平台
|
||||
|
||||
**官方网址：** https://grafana.com/
|
||||
|
||||
**类型：** 开源项目 / 可视化平台
|
||||
|
||||
**别名：**
|
||||
- Grafana OSS
|
||||
- Grafana Labs
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Grafana 是开源的可视化和告警平台，支持从 Prometheus、VictoriaMetrics、Loki、InfluxDB、Elasticsearch 等多种数据源查询和展示时序数据，提供丰富的 Dashboard 模板和灵活的告警配置。
|
||||
|
||||
**核心特性：**
|
||||
- 多数据源支持（Prometheus、Elasticsearch、Loki、InfluxDB 等）
|
||||
- Dashboard 即代码（JSON 导出 + Git 管理）
|
||||
- 告警规则配置（支持邮件/Slack/PagerDuty 等通知渠道）
|
||||
- 用户权限管理
|
||||
- 插件生态
|
||||
|
||||
**典型部署端口：** `3000`（默认 admin/admin）
|
||||
|
||||
**常用 Dashboard ID：**
|
||||
- Node Exporter Full: `1860`
|
||||
- cAdvisor Container Metrics: `14282`
|
||||
- Blackbox Exporter Probe: `7587`
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
- [[ctp-topic-60-monitor-aws-using-hyperscale-observability-with-grafana]]
|
||||
- [[ctp-topic-42-grafana-observability-dashboard]]
|
||||
- [[public-cloud-learning-sessions-observability-with-opentelemetry]]
|
||||
---
|
||||
title: "Grafana"
|
||||
type: entity
|
||||
tags: [visualization, monitoring, dashboards, observability]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Grafana — 可视化与告警平台
|
||||
|
||||
**官方网址：** https://grafana.com/
|
||||
|
||||
**类型：** 开源项目 / 可视化平台
|
||||
|
||||
**别名：**
|
||||
- Grafana OSS
|
||||
- Grafana Labs
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Grafana 是开源的可视化和告警平台，支持从 Prometheus、VictoriaMetrics、Loki、InfluxDB、Elasticsearch 等多种数据源查询和展示时序数据，提供丰富的 Dashboard 模板和灵活的告警配置。
|
||||
|
||||
**核心特性：**
|
||||
- 多数据源支持（Prometheus、Elasticsearch、Loki、InfluxDB 等）
|
||||
- Dashboard 即代码（JSON 导出 + Git 管理）
|
||||
- 告警规则配置（支持邮件/Slack/PagerDuty 等通知渠道）
|
||||
- 用户权限管理
|
||||
- 插件生态
|
||||
|
||||
**典型部署端口：** `3000`（默认 admin/admin）
|
||||
|
||||
**常用 Dashboard ID：**
|
||||
- Node Exporter Full: `1860`
|
||||
- cAdvisor Container Metrics: `14282`
|
||||
- Blackbox Exporter Probe: `7587`
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
- [[ctp-topic-60-monitor-aws-using-hyperscale-observability-with-grafana]]
|
||||
- [[ctp-topic-42-grafana-observability-dashboard]]
|
||||
- [[public-cloud-learning-sessions-observability-with-opentelemetry]]
|
||||
|
||||
@@ -1,60 +1,60 @@
|
||||
---
|
||||
title: "HashiCorp"
|
||||
type: entity
|
||||
tags:
|
||||
- devops
|
||||
- iac
|
||||
- infrastructure
|
||||
- tools
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
created: 2026-04-26
|
||||
---
|
||||
|
||||
# HashiCorp
|
||||
|
||||
## Definition
|
||||
|
||||
HashiCorp 是全球领先的**云基础设施自动化**软件公司，总部位于旧金山，创立于 2012 年。HashiCorp 提供一套完整的基础设施生命周期管理工具，覆盖配置管理、机密管理、服务网格和网络自动化等领域。
|
||||
|
||||
## Core Products
|
||||
|
||||
| 产品 | 用途 | 类别 |
|
||||
|------|------|------|
|
||||
| **Terraform** | 云厂商无关的基础设施即代码 | IaC |
|
||||
| **Vault** | 机密管理与加密即服务 | 安全 |
|
||||
| **Nomad** | 容器和工作负载调度器 | 编排 |
|
||||
| **Consul** | 服务网格与服务发现 | 网络 |
|
||||
| **Packer** | 机器镜像构建自动化 | 镜像 |
|
||||
| **Vagrant** | 开发环境管理 | 开发环境 |
|
||||
|
||||
## Terraform
|
||||
|
||||
HashiCorp 最知名的产品。Terraform 是用 Golang 编写的云无关 IaC 工具，通过声明式 HCL（HashiCorp Configuration Language）管理跨多云和混合云环境的基础设施资源。
|
||||
|
||||
**关键特性：**
|
||||
- 云厂商无关（AWS/Azure/GCP/On-prem）
|
||||
- `terraform plan` 预览变更
|
||||
- 状态文件管理实际资源与期望状态的绑定
|
||||
- 丰富的 Provider 生态系统和 Module 市场
|
||||
|
||||
**来源**: [[ctp-topic-48-terraform-vs-terragrunt]]
|
||||
|
||||
## Business Model
|
||||
|
||||
- **开源**：所有产品的开源版本
|
||||
- **Enterprise**：企业级功能（SSO、RBAC、审计日志、Sentinel 策略）
|
||||
- **HCP（HashiCorp Cloud Platform）**：SaaS 托管版本
|
||||
|
||||
## Related Entities
|
||||
|
||||
- [[Terraform]] — HashiCorp 出品的核心 IaC 产品
|
||||
- [[Terragrunt]] — 第三方 Terraform 封装工具（贯彻 DRY 原则）
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Infrastructure-as-Code]] — HashiCorp 产品的核心方法论
|
||||
- [[Multi-Cloud Strategy]] — Terraform 云无关定位的战略价值
|
||||
|
||||
## Related Sources
|
||||
|
||||
- [[ctp-topic-48-terraform-vs-terragrunt]]
|
||||
---
|
||||
title: "HashiCorp"
|
||||
type: entity
|
||||
tags:
|
||||
- devops
|
||||
- iac
|
||||
- infrastructure
|
||||
- tools
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
created: 2026-04-26
|
||||
---
|
||||
|
||||
# HashiCorp
|
||||
|
||||
## Definition
|
||||
|
||||
HashiCorp 是全球领先的**云基础设施自动化**软件公司，总部位于旧金山，创立于 2012 年。HashiCorp 提供一套完整的基础设施生命周期管理工具，覆盖配置管理、机密管理、服务网格和网络自动化等领域。
|
||||
|
||||
## Core Products
|
||||
|
||||
| 产品 | 用途 | 类别 |
|
||||
|------|------|------|
|
||||
| **Terraform** | 云厂商无关的基础设施即代码 | IaC |
|
||||
| **Vault** | 机密管理与加密即服务 | 安全 |
|
||||
| **Nomad** | 容器和工作负载调度器 | 编排 |
|
||||
| **Consul** | 服务网格与服务发现 | 网络 |
|
||||
| **Packer** | 机器镜像构建自动化 | 镜像 |
|
||||
| **Vagrant** | 开发环境管理 | 开发环境 |
|
||||
|
||||
## Terraform
|
||||
|
||||
HashiCorp 最知名的产品。Terraform 是用 Golang 编写的云无关 IaC 工具，通过声明式 HCL（HashiCorp Configuration Language）管理跨多云和混合云环境的基础设施资源。
|
||||
|
||||
**关键特性：**
|
||||
- 云厂商无关（AWS/Azure/GCP/On-prem）
|
||||
- `terraform plan` 预览变更
|
||||
- 状态文件管理实际资源与期望状态的绑定
|
||||
- 丰富的 Provider 生态系统和 Module 市场
|
||||
|
||||
**来源**: [[ctp-topic-48-terraform-vs-terragrunt]]
|
||||
|
||||
## Business Model
|
||||
|
||||
- **开源**：所有产品的开源版本
|
||||
- **Enterprise**：企业级功能（SSO、RBAC、审计日志、Sentinel 策略）
|
||||
- **HCP（HashiCorp Cloud Platform）**：SaaS 托管版本
|
||||
|
||||
## Related Entities
|
||||
|
||||
- [[Terraform]] — HashiCorp 出品的核心 IaC 产品
|
||||
- [[Terragrunt]] — 第三方 Terraform 封装工具（贯彻 DRY 原则）
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Infrastructure-as-Code]] — HashiCorp 产品的核心方法论
|
||||
- [[Multi-Cloud Strategy]] — Terraform 云无关定位的战略价值
|
||||
|
||||
## Related Sources
|
||||
|
||||
- [[ctp-topic-48-terraform-vs-terragrunt]]
|
||||
|
||||
@@ -1,77 +1,77 @@
|
||||
---
|
||||
title: "Jellyfin"
|
||||
type: entity
|
||||
tags: [video, media-server, self-hosted, open-source, docker]
|
||||
date: 2026-04-14
|
||||
sources: [用docker安装jellyfin, 用docker中安装navidrome]
|
||||
---
|
||||
|
||||
# Jellyfin
|
||||
|
||||
开源视频媒体服务器，提供网页端流媒体播放、管理界面和转码能力。
|
||||
|
||||
## Aliases
|
||||
- Jellyfin Media Server
|
||||
- Jellyfin Server
|
||||
|
||||
## Type
|
||||
开源自托管视频流媒体服务器（Emby 分支）
|
||||
|
||||
## Core Functionality
|
||||
- 视频播放与管理，支持电影、电视剧、体育节目等多种媒体类型
|
||||
- 硬件加速视频转码（Intel QuickSync / NVIDIA GPU / VA-API / AMD VCE）
|
||||
- 元数据刮削（TMDB/TheTVDB 等）
|
||||
- 多用户支持与播放进度追踪
|
||||
- DLNA / Chromecast / Apple TV / Roku 等设备投射
|
||||
- Web UI + 官方客户端（Android / iOS / TV 版）
|
||||
|
||||
## Key Images
|
||||
| 镜像 | 维护者 | 特点 |
|
||||
|------|--------|------|
|
||||
| linuxserver/jellyfin | LinuxServer.io | 官方稳定版 |
|
||||
| nyanmisaka/jellyfin | 社区维护 | 预装优化 FFmpeg，硬件转码开箱即用 |
|
||||
|
||||
## Docker 配置关键参数（nyanmisaka 镜像）
|
||||
```yaml
|
||||
services:
|
||||
jellyfin:
|
||||
image: nyanmisaka/jellyfin:latest
|
||||
user: "1026:100" # 群晖 UID:GID
|
||||
ports:
|
||||
- 8096:8096/tcp # Web UI
|
||||
- 7359:7359/udp # 自动发现
|
||||
volumes:
|
||||
- /volume1/docker/jellyfin/config:/config
|
||||
- /volume1/docker/jellyfin/cache:/cache
|
||||
- /volume2/movie:/media
|
||||
- "/volume1/TV shows:/media2"
|
||||
- /volume1/docker/jellyfin/fonts:/usr/local/share/fonts/custom:ro
|
||||
environment:
|
||||
- JELLYFIN_PublishedServerUrl=http://jellyfin.ishenwei.online
|
||||
- TZ=Asia/Shanghai
|
||||
devices:
|
||||
- /dev/dri:/dev/dri # Intel QuickSync 硬件转码
|
||||
restart: unless-stopped
|
||||
extra_hosts:
|
||||
- 'host.docker.internal:host-gateway'
|
||||
```
|
||||
|
||||
## Hardware Transcoding
|
||||
- **Intel QuickSync**：通过 `/dev/dri` 设备直通，nyanmisaka 镜像预装支持
|
||||
- **NVIDIA GPU**：需 nvidia-container-toolkit
|
||||
- **软件转码**：ffmpeg fallback，适合低功耗设备
|
||||
|
||||
## 性能考量
|
||||
- 媒体转码建议内存 2-4GB
|
||||
- 群晖 NAS 上优先使用 QuickSync / VA-API 硬件转码以降低 CPU 占用
|
||||
- cache 目录建议 SSD 以提升元数据和缩略图读写性能
|
||||
|
||||
## Connections
|
||||
- [[Transmission]] ← 下载端 → [[Jellyfin]]（播放端）— "下载→整理→播放" 家庭媒体工作流
|
||||
- [[Navidrome]] ← 对标竞品 → [[Jellyfin]] — Navidrome 服务音乐，Jellyfin 服务视频
|
||||
- [[群晖 NAS]] ← 宿主机 → [[Jellyfin]] — NAS 提供存储和 Docker 运行环境
|
||||
- [[nyanmisaka/jellyfin]] ← 优化镜像 → [[Jellyfin]] — 预装硬件转码支持的社区镜像
|
||||
- [[LinuxServer.io]] ← 官方镜像 → [[Jellyfin]] — 稳定版官方镜像维护组织
|
||||
|
||||
## Sources
|
||||
- [[用docker安装jellyfin]] — 在群晖 NAS 上部署 Jellyfin 的完整 Docker Compose 配置
|
||||
---
|
||||
title: "Jellyfin"
|
||||
type: entity
|
||||
tags: [video, media-server, self-hosted, open-source, docker]
|
||||
date: 2026-04-14
|
||||
sources: [用docker安装jellyfin, 用docker中安装navidrome]
|
||||
---
|
||||
|
||||
# Jellyfin
|
||||
|
||||
开源视频媒体服务器，提供网页端流媒体播放、管理界面和转码能力。
|
||||
|
||||
## Aliases
|
||||
- Jellyfin Media Server
|
||||
- Jellyfin Server
|
||||
|
||||
## Type
|
||||
开源自托管视频流媒体服务器（Emby 分支）
|
||||
|
||||
## Core Functionality
|
||||
- 视频播放与管理，支持电影、电视剧、体育节目等多种媒体类型
|
||||
- 硬件加速视频转码（Intel QuickSync / NVIDIA GPU / VA-API / AMD VCE）
|
||||
- 元数据刮削（TMDB/TheTVDB 等）
|
||||
- 多用户支持与播放进度追踪
|
||||
- DLNA / Chromecast / Apple TV / Roku 等设备投射
|
||||
- Web UI + 官方客户端（Android / iOS / TV 版）
|
||||
|
||||
## Key Images
|
||||
| 镜像 | 维护者 | 特点 |
|
||||
|------|--------|------|
|
||||
| linuxserver/jellyfin | LinuxServer.io | 官方稳定版 |
|
||||
| nyanmisaka/jellyfin | 社区维护 | 预装优化 FFmpeg，硬件转码开箱即用 |
|
||||
|
||||
## Docker 配置关键参数（nyanmisaka 镜像）
|
||||
```yaml
|
||||
services:
|
||||
jellyfin:
|
||||
image: nyanmisaka/jellyfin:latest
|
||||
user: "1026:100" # 群晖 UID:GID
|
||||
ports:
|
||||
- 8096:8096/tcp # Web UI
|
||||
- 7359:7359/udp # 自动发现
|
||||
volumes:
|
||||
- /volume1/docker/jellyfin/config:/config
|
||||
- /volume1/docker/jellyfin/cache:/cache
|
||||
- /volume2/movie:/media
|
||||
- "/volume1/TV shows:/media2"
|
||||
- /volume1/docker/jellyfin/fonts:/usr/local/share/fonts/custom:ro
|
||||
environment:
|
||||
- JELLYFIN_PublishedServerUrl=http://jellyfin.ishenwei.online
|
||||
- TZ=Asia/Shanghai
|
||||
devices:
|
||||
- /dev/dri:/dev/dri # Intel QuickSync 硬件转码
|
||||
restart: unless-stopped
|
||||
extra_hosts:
|
||||
- 'host.docker.internal:host-gateway'
|
||||
```
|
||||
|
||||
## Hardware Transcoding
|
||||
- **Intel QuickSync**：通过 `/dev/dri` 设备直通，nyanmisaka 镜像预装支持
|
||||
- **NVIDIA GPU**：需 nvidia-container-toolkit
|
||||
- **软件转码**：ffmpeg fallback，适合低功耗设备
|
||||
|
||||
## 性能考量
|
||||
- 媒体转码建议内存 2-4GB
|
||||
- 群晖 NAS 上优先使用 QuickSync / VA-API 硬件转码以降低 CPU 占用
|
||||
- cache 目录建议 SSD 以提升元数据和缩略图读写性能
|
||||
|
||||
## Connections
|
||||
- [[Transmission]] ← 下载端 → [[Jellyfin]]（播放端）— "下载→整理→播放" 家庭媒体工作流
|
||||
- [[Navidrome]] ← 对标竞品 → [[Jellyfin]] — Navidrome 服务音乐，Jellyfin 服务视频
|
||||
- [[群晖 NAS]] ← 宿主机 → [[Jellyfin]] — NAS 提供存储和 Docker 运行环境
|
||||
- [[nyanmisaka/jellyfin]] ← 优化镜像 → [[Jellyfin]] — 预装硬件转码支持的社区镜像
|
||||
- [[LinuxServer.io]] ← 官方镜像 → [[Jellyfin]] — 稳定版官方镜像维护组织
|
||||
|
||||
## Sources
|
||||
- [[用docker安装jellyfin]] — 在群晖 NAS 上部署 Jellyfin 的完整 Docker Compose 配置
|
||||
|
||||
@@ -1,114 +1,114 @@
|
||||
---
|
||||
title: "Kubernetes"
|
||||
type: entity
|
||||
tags:
|
||||
- cloud
|
||||
- container
|
||||
- orchestration
|
||||
- devops
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
created: 2026-04-25
|
||||
---
|
||||
|
||||
# Kubernetes
|
||||
|
||||
## Definition
|
||||
|
||||
Kubernetes (K8s) 是 Google 开源的**容器编排平台**，用于自动化容器化应用的部署、扩缩容和管理。是云原生 (Cloud-Native) 架构的核心基础设施，也是 Agentic AI 自主修复 (Self-Healing) 的主要目标环境。
|
||||
|
||||
## Aliases
|
||||
|
||||
- K8s
|
||||
- Kubernetes
|
||||
- Container Orchestration Platform
|
||||
|
||||
## Major Cloud Implementations
|
||||
|
||||
| Provider | Service | Description |
|
||||
|----------|---------|-------------|
|
||||
| AWS | EKS (Elastic Kubernetes Service) | 托管 Kubernetes on AWS |
|
||||
| GCP | GKE (Google Kubernetes Engine) | 托管 Kubernetes on GCP |
|
||||
| Azure | AKS (Azure Kubernetes Service) | 托管 Kubernetes on Azure |
|
||||
|
||||
## Kubernetes Self-Healing Capabilities
|
||||
|
||||
Kubernetes 原生提供基础 Self-Healing 能力：
|
||||
|
||||
```yaml
|
||||
# Kubernetes Self-Healing 原生机制
|
||||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
spec:
|
||||
replicas: 3
|
||||
strategy:
|
||||
type: RollingUpdate
|
||||
template:
|
||||
spec:
|
||||
terminationGracePeriodSeconds: 30
|
||||
# 内置机制:
|
||||
# - 自动重启失败的容器
|
||||
# - 替换不健康的 Pod
|
||||
# - 滚动更新确保服务可用
|
||||
```
|
||||
|
||||
Agentic AI 在原生能力基础上提供**更高级的自我修复**：
|
||||
|
||||
| 能力 | Kubernetes 原生 | Agentic AI Enhanced |
|
||||
|------|---------------|-------------------|
|
||||
| Pod 重启 | ✅ 自动重启崩溃容器 | ✅ 智能分析根因 + 预防性重启 |
|
||||
| 扩缩容 | ✅ HPA 基于指标 | ✅ 预测性扩缩容 |
|
||||
| 节点恢复 | ✅ 节点故障迁移 | ✅ 主动健康检查 + 预防性迁移 |
|
||||
| 配置修复 | ❌ 需人工介入 | ✅ AI 自动修正 ConfigMap/Secret |
|
||||
|
||||
## Agentic AI Monitoring Targets
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ Agentic AI for Kubernetes │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ 监控层 │
|
||||
│ ├── Pod Metrics (CPU/Memory/Network) │
|
||||
│ ├── Workload Health (Deployment/ReplicaSet) │
|
||||
│ ├── Node Status (Ready/Condition) │
|
||||
│ └── Cluster Components (etcd, API Server) │
|
||||
│ │
|
||||
│ 决策层 │
|
||||
│ ├── Anomaly Detection (AI) │
|
||||
│ ├── Root Cause Analysis (AI) │
|
||||
│ └── Action Planning (AI) │
|
||||
│ │
|
||||
│ 执行层 │
|
||||
│ ├── kubectl API (restart/migrate/scale) │
|
||||
│ ├── HPA Override (AI-driven scaling) │
|
||||
│ └── Config Updates (AI-driven fixes) │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
## Example
|
||||
|
||||
> An AI agent monitoring AWS EKS clusters detects high CPU usage due to a rogue pod:
|
||||
> - Pod `payment-service-v2-abc123` CPU usage: 95%
|
||||
> - AI correlates with recent deployment timestamp
|
||||
> - AI identifies: Memory leak in new version
|
||||
> - AI Actions:
|
||||
> 1. Scale deployment to 3 replicas (distribute load)
|
||||
> 2. Create rollback ticket
|
||||
> 3. Notify team via Slack
|
||||
> 4. Auto-rollback after approval
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Self-Healing Systems]] — Kubernetes 是 Self-Healing 的主要载体
|
||||
- [[Cloud-Native]] — Kubernetes 是 Cloud-Native 的核心
|
||||
- [[Deployment Automation]] — Kubernetes 部署的自动化
|
||||
- [[Container Lifecycle Hardening]] — 容器安全加固
|
||||
|
||||
## Related Entities
|
||||
|
||||
- [[Agentic AI]] — Kubernetes 是 Agentic AI 的管理对象
|
||||
- EKS, GKE, AKS — 具体云服务商实现
|
||||
|
||||
## Related Sources
|
||||
|
||||
- [[how-agentic-ai-can-help-for-cloud-devops]]
|
||||
- [[ctp-topic-70-eks-deployment-using-iac]]
|
||||
---
|
||||
title: "Kubernetes"
|
||||
type: entity
|
||||
tags:
|
||||
- cloud
|
||||
- container
|
||||
- orchestration
|
||||
- devops
|
||||
sources: [cloud-operating-model-key-strategies-and-best-practices]
|
||||
created: 2026-04-25
|
||||
---
|
||||
|
||||
# Kubernetes
|
||||
|
||||
## Definition
|
||||
|
||||
Kubernetes (K8s) 是 Google 开源的**容器编排平台**，用于自动化容器化应用的部署、扩缩容和管理。是云原生 (Cloud-Native) 架构的核心基础设施，也是 Agentic AI 自主修复 (Self-Healing) 的主要目标环境。
|
||||
|
||||
## Aliases
|
||||
|
||||
- K8s
|
||||
- Kubernetes
|
||||
- Container Orchestration Platform
|
||||
|
||||
## Major Cloud Implementations
|
||||
|
||||
| Provider | Service | Description |
|
||||
|----------|---------|-------------|
|
||||
| AWS | EKS (Elastic Kubernetes Service) | 托管 Kubernetes on AWS |
|
||||
| GCP | GKE (Google Kubernetes Engine) | 托管 Kubernetes on GCP |
|
||||
| Azure | AKS (Azure Kubernetes Service) | 托管 Kubernetes on Azure |
|
||||
|
||||
## Kubernetes Self-Healing Capabilities
|
||||
|
||||
Kubernetes 原生提供基础 Self-Healing 能力：
|
||||
|
||||
```yaml
|
||||
# Kubernetes Self-Healing 原生机制
|
||||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
spec:
|
||||
replicas: 3
|
||||
strategy:
|
||||
type: RollingUpdate
|
||||
template:
|
||||
spec:
|
||||
terminationGracePeriodSeconds: 30
|
||||
# 内置机制:
|
||||
# - 自动重启失败的容器
|
||||
# - 替换不健康的 Pod
|
||||
# - 滚动更新确保服务可用
|
||||
```
|
||||
|
||||
Agentic AI 在原生能力基础上提供**更高级的自我修复**：
|
||||
|
||||
| 能力 | Kubernetes 原生 | Agentic AI Enhanced |
|
||||
|------|---------------|-------------------|
|
||||
| Pod 重启 | ✅ 自动重启崩溃容器 | ✅ 智能分析根因 + 预防性重启 |
|
||||
| 扩缩容 | ✅ HPA 基于指标 | ✅ 预测性扩缩容 |
|
||||
| 节点恢复 | ✅ 节点故障迁移 | ✅ 主动健康检查 + 预防性迁移 |
|
||||
| 配置修复 | ❌ 需人工介入 | ✅ AI 自动修正 ConfigMap/Secret |
|
||||
|
||||
## Agentic AI Monitoring Targets
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ Agentic AI for Kubernetes │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ 监控层 │
|
||||
│ ├── Pod Metrics (CPU/Memory/Network) │
|
||||
│ ├── Workload Health (Deployment/ReplicaSet) │
|
||||
│ ├── Node Status (Ready/Condition) │
|
||||
│ └── Cluster Components (etcd, API Server) │
|
||||
│ │
|
||||
│ 决策层 │
|
||||
│ ├── Anomaly Detection (AI) │
|
||||
│ ├── Root Cause Analysis (AI) │
|
||||
│ └── Action Planning (AI) │
|
||||
│ │
|
||||
│ 执行层 │
|
||||
│ ├── kubectl API (restart/migrate/scale) │
|
||||
│ ├── HPA Override (AI-driven scaling) │
|
||||
│ └── Config Updates (AI-driven fixes) │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
## Example
|
||||
|
||||
> An AI agent monitoring AWS EKS clusters detects high CPU usage due to a rogue pod:
|
||||
> - Pod `payment-service-v2-abc123` CPU usage: 95%
|
||||
> - AI correlates with recent deployment timestamp
|
||||
> - AI identifies: Memory leak in new version
|
||||
> - AI Actions:
|
||||
> 1. Scale deployment to 3 replicas (distribute load)
|
||||
> 2. Create rollback ticket
|
||||
> 3. Notify team via Slack
|
||||
> 4. Auto-rollback after approval
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Self-Healing Systems]] — Kubernetes 是 Self-Healing 的主要载体
|
||||
- [[Cloud-Native]] — Kubernetes 是 Cloud-Native 的核心
|
||||
- [[Deployment Automation]] — Kubernetes 部署的自动化
|
||||
- [[Container Lifecycle Hardening]] — 容器安全加固
|
||||
|
||||
## Related Entities
|
||||
|
||||
- [[Agentic AI]] — Kubernetes 是 Agentic AI 的管理对象
|
||||
- EKS, GKE, AKS — 具体云服务商实现
|
||||
|
||||
## Related Sources
|
||||
|
||||
- [[how-agentic-ai-can-help-for-cloud-devops]]
|
||||
- [[ctp-topic-70-eks-deployment-using-iac]]
|
||||
|
||||
@@ -1,35 +1,35 @@
|
||||
# MerlinClash插件
|
||||
|
||||
## Aliases
|
||||
- MerlinClash
|
||||
- 小猫咪插件
|
||||
- Merlin-Clash
|
||||
- MC
|
||||
|
||||
## Basic Info
|
||||
- **Type**: 梅林固件科学上网插件（第三方）
|
||||
- **Platform**: 梅林固件（ASUSWRT-Merlin）
|
||||
- **Engine**: Clash 核心
|
||||
- **Language**: 中文社区维护
|
||||
|
||||
## Description
|
||||
MerlinClash（又称"小猫咪插件"）是基于 Clash 核心的梅林固件科学上网插件，支持策略组分流、节点自动延迟测试和故障转移。相比同类插件（如科学上网插件 GitHub 版），功能更全面，是梅林固件上推荐使用的科学上网解决方案。
|
||||
|
||||
## Key Features
|
||||
- 策略组分流（按应用/地区/目标自动路由）
|
||||
- 节点自动延迟测试（定时 ping 测速）
|
||||
- 故障转移（主节点不可用时自动切换备用节点）
|
||||
- 订阅地址自动更新（定时抓取机场订阅）
|
||||
- 守护进程（保证插件持续稳定运行）
|
||||
- 支持 SSR/V2Ray/Trojan 等多协议
|
||||
|
||||
## Known Limitations
|
||||
- 与其他科学上网插件不可同时运行（二选一）
|
||||
- 需要足够 JFFS 分区空间（建议 Full 版本，内存充足时）
|
||||
|
||||
## Related
|
||||
- [[梅林固件]] — 插件运行平台
|
||||
- [[网件RAX50]] — 典型支持路由器
|
||||
- [[策略组分流]] — 插件核心功能
|
||||
- [[故障转移]] — 配套可靠性机制
|
||||
- [[订阅机制]] — 节点配置来源
|
||||
# MerlinClash插件
|
||||
|
||||
## Aliases
|
||||
- MerlinClash
|
||||
- 小猫咪插件
|
||||
- Merlin-Clash
|
||||
- MC
|
||||
|
||||
## Basic Info
|
||||
- **Type**: 梅林固件科学上网插件（第三方）
|
||||
- **Platform**: 梅林固件（ASUSWRT-Merlin）
|
||||
- **Engine**: Clash 核心
|
||||
- **Language**: 中文社区维护
|
||||
|
||||
## Description
|
||||
MerlinClash（又称"小猫咪插件"）是基于 Clash 核心的梅林固件科学上网插件，支持策略组分流、节点自动延迟测试和故障转移。相比同类插件（如科学上网插件 GitHub 版），功能更全面，是梅林固件上推荐使用的科学上网解决方案。
|
||||
|
||||
## Key Features
|
||||
- 策略组分流（按应用/地区/目标自动路由）
|
||||
- 节点自动延迟测试（定时 ping 测速）
|
||||
- 故障转移（主节点不可用时自动切换备用节点）
|
||||
- 订阅地址自动更新（定时抓取机场订阅）
|
||||
- 守护进程（保证插件持续稳定运行）
|
||||
- 支持 SSR/V2Ray/Trojan 等多协议
|
||||
|
||||
## Known Limitations
|
||||
- 与其他科学上网插件不可同时运行（二选一）
|
||||
- 需要足够 JFFS 分区空间（建议 Full 版本，内存充足时）
|
||||
|
||||
## Related
|
||||
- [[梅林固件]] — 插件运行平台
|
||||
- [[网件RAX50]] — 典型支持路由器
|
||||
- [[策略组分流]] — 插件核心功能
|
||||
- [[故障转移]] — 配套可靠性机制
|
||||
- [[订阅机制]] — 节点配置来源
|
||||
|
||||
@@ -1,60 +1,60 @@
|
||||
---
|
||||
title: "Navidrome"
|
||||
type: entity
|
||||
aliases: []
|
||||
tags: [music, media-server, self-hosted, open-source]
|
||||
sources: [用docker中安装navidrome]
|
||||
---
|
||||
|
||||
# Navidrome
|
||||
|
||||
## Basic Info
|
||||
- **Type**: Entity / Product / Open-source Project
|
||||
- **Description**: 开源音乐流媒体服务器，支持 Subsonic API 协议，可通过网页端或移动客户端访问个人音乐库
|
||||
- **Author**: Deluan
|
||||
- **Repository**: github.com/navidrome/navidrome
|
||||
- **License**: GPL v3
|
||||
|
||||
## Aliases
|
||||
- Navidrome
|
||||
- deluan/navidrome（Docker 镜像名）
|
||||
|
||||
## Key Capabilities
|
||||
1. **Subsonic API 兼容** — 与 Subsonic 协议兼容的客户端均可使用（Jellyfin/Subsonic 客户端通用）
|
||||
2. **网页播放器** — 内置响应式 Web UI，支持播放列表、专辑浏览、搜索
|
||||
3. **移动端支持** — 支持 DSub、Substreamer、Avanté 等 Subsonic 客户端
|
||||
4. **转码支持** — 按客户端网络情况自动转码为合适码率，节省带宽
|
||||
5. **元数据扫描** — 自动从音乐文件中读取 ID3 标签、封面信息
|
||||
6. **轻量部署** — 单 Docker 容器运行，最低 512MB 内存即可运行
|
||||
|
||||
## Configuration Highlights (Docker Compose)
|
||||
```yaml
|
||||
image: deluan/navidrome:latest
|
||||
user: "1026:100" # 以非 root 用户运行
|
||||
ports:
|
||||
- "4533:4533"
|
||||
volumes:
|
||||
- /volume1/music:/music:ro # 只读挂载音乐目录
|
||||
- /volume1/docker/navidrome/data:/data # 数据目录
|
||||
environment:
|
||||
- ND_LOGLEVEL=info
|
||||
- ND_ENABLETRANSCODINGCONFIG=true # 启用转码配置 UI
|
||||
- ND_AUTOTRANSCODEDOWNLOAD=true # 启用自动转码下载
|
||||
- ND_TRANSCODINGCACHESIZE=200MB # 转码缓存上限 200MB
|
||||
```
|
||||
|
||||
## Key Design Decisions
|
||||
- **只读音乐挂载（`:ro`）** — 防止容器误操作修改原始音乐文件
|
||||
- **非 root 用户运行** — 提升容器安全性，UID/GID 与宿主机用户对应
|
||||
- **转码缓存限制** — 200MB 上限防止磁盘空间被缓存占满
|
||||
- **端口 4533** — Navidrome 默认端口，局域网访问地址：`http://<host>:4533`
|
||||
|
||||
## Related Entities
|
||||
- [[Jellyfin]] — 视频媒体服务器，架构类似但服务视频内容
|
||||
- [[群晖 NAS]] — Navidrome 常见部署环境，音乐文件的存储位置
|
||||
- [[Docker-Image]] — Navidrome 的部署方式
|
||||
- [[Docker Compose]] — Navidrome 的配置管理方式
|
||||
- [[Deluan/Navidrome]] — 官方 Docker 镜像发布者
|
||||
|
||||
## Source
|
||||
- [[用docker中安装navidrome]] — Navidrome Docker 部署实战笔记
|
||||
---
|
||||
title: "Navidrome"
|
||||
type: entity
|
||||
aliases: []
|
||||
tags: [music, media-server, self-hosted, open-source]
|
||||
sources: [用docker中安装navidrome]
|
||||
---
|
||||
|
||||
# Navidrome
|
||||
|
||||
## Basic Info
|
||||
- **Type**: Entity / Product / Open-source Project
|
||||
- **Description**: 开源音乐流媒体服务器，支持 Subsonic API 协议，可通过网页端或移动客户端访问个人音乐库
|
||||
- **Author**: Deluan
|
||||
- **Repository**: github.com/navidrome/navidrome
|
||||
- **License**: GPL v3
|
||||
|
||||
## Aliases
|
||||
- Navidrome
|
||||
- deluan/navidrome（Docker 镜像名）
|
||||
|
||||
## Key Capabilities
|
||||
1. **Subsonic API 兼容** — 与 Subsonic 协议兼容的客户端均可使用（Jellyfin/Subsonic 客户端通用）
|
||||
2. **网页播放器** — 内置响应式 Web UI，支持播放列表、专辑浏览、搜索
|
||||
3. **移动端支持** — 支持 DSub、Substreamer、Avanté 等 Subsonic 客户端
|
||||
4. **转码支持** — 按客户端网络情况自动转码为合适码率，节省带宽
|
||||
5. **元数据扫描** — 自动从音乐文件中读取 ID3 标签、封面信息
|
||||
6. **轻量部署** — 单 Docker 容器运行，最低 512MB 内存即可运行
|
||||
|
||||
## Configuration Highlights (Docker Compose)
|
||||
```yaml
|
||||
image: deluan/navidrome:latest
|
||||
user: "1026:100" # 以非 root 用户运行
|
||||
ports:
|
||||
- "4533:4533"
|
||||
volumes:
|
||||
- /volume1/music:/music:ro # 只读挂载音乐目录
|
||||
- /volume1/docker/navidrome/data:/data # 数据目录
|
||||
environment:
|
||||
- ND_LOGLEVEL=info
|
||||
- ND_ENABLETRANSCODINGCONFIG=true # 启用转码配置 UI
|
||||
- ND_AUTOTRANSCODEDOWNLOAD=true # 启用自动转码下载
|
||||
- ND_TRANSCODINGCACHESIZE=200MB # 转码缓存上限 200MB
|
||||
```
|
||||
|
||||
## Key Design Decisions
|
||||
- **只读音乐挂载（`:ro`）** — 防止容器误操作修改原始音乐文件
|
||||
- **非 root 用户运行** — 提升容器安全性，UID/GID 与宿主机用户对应
|
||||
- **转码缓存限制** — 200MB 上限防止磁盘空间被缓存占满
|
||||
- **端口 4533** — Navidrome 默认端口，局域网访问地址：`http://<host>:4533`
|
||||
|
||||
## Related Entities
|
||||
- [[Jellyfin]] — 视频媒体服务器，架构类似但服务视频内容
|
||||
- [[群晖 NAS]] — Navidrome 常见部署环境，音乐文件的存储位置
|
||||
- [[Docker-Image]] — Navidrome 的部署方式
|
||||
- [[Docker Compose]] — Navidrome 的配置管理方式
|
||||
- [[Deluan/Navidrome]] — 官方 Docker 镜像发布者
|
||||
|
||||
## Source
|
||||
- [[用docker中安装navidrome]] — Navidrome Docker 部署实战笔记
|
||||
|
||||
@@ -1,47 +1,47 @@
|
||||
---
|
||||
title: "Node Exporter"
|
||||
type: entity
|
||||
tags: [monitoring, exporter, prometheus, devops]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Node Exporter — Prometheus 主机指标采集器
|
||||
|
||||
**官方网址：** https://prometheus.io/docs/guides/node-exporter/
|
||||
|
||||
**类型：** 开源项目 / Prometheus Exporter
|
||||
|
||||
**别名：**
|
||||
- prometheus-node-exporter
|
||||
- node_exporter
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Node Exporter 是 Prometheus 官方提供的 exporter，用于采集主机（服务器/NAS/树莓派等）的硬件和操作系统指标。以 DaemonSet 或独立进程方式运行，采集 CPU、内存、磁盘、网络、文件系统等数据。
|
||||
|
||||
**采集指标示例：**
|
||||
- `node_cpu_seconds_total` — CPU 使用时间
|
||||
- `node_memory_MemAvailable_bytes` — 可用内存
|
||||
- `node_memory_MemTotal_bytes` — 总内存
|
||||
- `node_filesystem_avail_bytes` — 文件系统可用空间
|
||||
- `node_network_receive_bytes_total` — 网络接收字节
|
||||
- `node_load1` / `node_load5` / `node_load15` — 系统负载
|
||||
|
||||
**典型部署：**
|
||||
- Docker: `prom/node-exporter:latest`，需 `network_mode: host` + volume 挂载 `/proc`、`/sys`、`/`
|
||||
- 端口：`9100`
|
||||
|
||||
**关键告警规则示例：**
|
||||
- 磁盘剩余 < 10%: `node_filesystem_avail_bytes / node_filesystem_size_bytes < 0.10`
|
||||
- CPU 使用率 > 85%: `avg(rate(node_cpu_seconds_total{mode="user"}[2m])) * 100 > 85`
|
||||
- 内存可用 < 15%: `node_memory_MemAvailable_bytes / node_memory_MemTotal_bytes < 0.15`
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
---
|
||||
title: "Node Exporter"
|
||||
type: entity
|
||||
tags: [monitoring, exporter, prometheus, devops]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Node Exporter — Prometheus 主机指标采集器
|
||||
|
||||
**官方网址：** https://prometheus.io/docs/guides/node-exporter/
|
||||
|
||||
**类型：** 开源项目 / Prometheus Exporter
|
||||
|
||||
**别名：**
|
||||
- prometheus-node-exporter
|
||||
- node_exporter
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Node Exporter 是 Prometheus 官方提供的 exporter，用于采集主机（服务器/NAS/树莓派等）的硬件和操作系统指标。以 DaemonSet 或独立进程方式运行，采集 CPU、内存、磁盘、网络、文件系统等数据。
|
||||
|
||||
**采集指标示例：**
|
||||
- `node_cpu_seconds_total` — CPU 使用时间
|
||||
- `node_memory_MemAvailable_bytes` — 可用内存
|
||||
- `node_memory_MemTotal_bytes` — 总内存
|
||||
- `node_filesystem_avail_bytes` — 文件系统可用空间
|
||||
- `node_network_receive_bytes_total` — 网络接收字节
|
||||
- `node_load1` / `node_load5` / `node_load15` — 系统负载
|
||||
|
||||
**典型部署：**
|
||||
- Docker: `prom/node-exporter:latest`，需 `network_mode: host` + volume 挂载 `/proc`、`/sys`、`/`
|
||||
- 端口：`9100`
|
||||
|
||||
**关键告警规则示例：**
|
||||
- 磁盘剩余 < 10%: `node_filesystem_avail_bytes / node_filesystem_size_bytes < 0.10`
|
||||
- CPU 使用率 > 85%: `avg(rate(node_cpu_seconds_total{mode="user"}[2m])) * 100 > 85`
|
||||
- 内存可用 < 15%: `node_memory_MemAvailable_bytes / node_memory_MemTotal_bytes < 0.15`
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
@@ -1,47 +1,47 @@
|
||||
---
|
||||
title: "OWASP"
|
||||
type: entity
|
||||
tags: [security, web-security, standards, devsecops]
|
||||
sources: ["what-is-devsecops-best-practices-benefits-and-tools"]
|
||||
last_updated: 2025-12-19
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
OWASP（Open Web Application Security Project，开放式 Web 应用安全项目）是一个开源的社区驱动的非营利组织，专注于提高软件安全性。OWASP 是全球应用安全领域最具影响力的社区之一，其工具、标准和技术文档被广泛应用于 [[DevSecOps]] 实践中。
|
||||
|
||||
## Key Deliverables
|
||||
|
||||
### OWASP Top Ten
|
||||
最知名的 OWASP 项目，列出 Web 应用最关键的 10 大安全风险，是 [[DevSecOps]] 安全测试的核心参考标准：
|
||||
1. Broken Access Control（访问控制失效）
|
||||
2. Cryptographic Failures（加密失败）
|
||||
3. Injection（注入攻击）
|
||||
4. Insecure Design（不安全设计）
|
||||
5. Security Misconfiguration（安全配置错误）
|
||||
6. Vulnerable and Outdated Components（易受攻击和过时的组件）
|
||||
7. Identification and Authentication Failures（识别和身份验证失败）
|
||||
8. Software and Data Integrity Failures（软件和数据完整性失败）
|
||||
9. Security Logging and Monitoring Failures（安全日志和监控失败）
|
||||
10. Server-Side Request Forgery（服务器端请求伪造）
|
||||
|
||||
### Other Key Projects
|
||||
- **OWASP ZAP**：开源 Web 应用安全扫描器（[[DAST]] 工具）
|
||||
- **OWASP ASVS**：应用安全验证标准
|
||||
- **OWASP SAMM**：软件保证成熟度模型
|
||||
- **OWASP Dependency-Check**：SCA 工具（[[SCA]]）
|
||||
|
||||
## Role in DevSecOps
|
||||
|
||||
在 [[DevSecOps]] 中，OWASP 提供：
|
||||
- [[DAST]] 测试的漏洞分类标准
|
||||
- [[SAST]] 工具的规则开发参考
|
||||
- 安全编码标准和最佳实践
|
||||
- 开源安全测试工具
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[DevSecOps]] — OWASP 是 DevSecOps 工具链的核心参考
|
||||
- [[DAST]] — OWASP ZAP 是主流 DAST 工具
|
||||
- [[SAST]] — OWASP 提供安全编码标准
|
||||
- [[OWASP Top Ten]] — Web 应用安全风险的权威列表
|
||||
---
|
||||
title: "OWASP"
|
||||
type: entity
|
||||
tags: [security, web-security, standards, devsecops]
|
||||
sources: ["what-is-devsecops-best-practices-benefits-and-tools"]
|
||||
last_updated: 2025-12-19
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
OWASP（Open Web Application Security Project，开放式 Web 应用安全项目）是一个开源的社区驱动的非营利组织，专注于提高软件安全性。OWASP 是全球应用安全领域最具影响力的社区之一，其工具、标准和技术文档被广泛应用于 [[DevSecOps]] 实践中。
|
||||
|
||||
## Key Deliverables
|
||||
|
||||
### OWASP Top Ten
|
||||
最知名的 OWASP 项目，列出 Web 应用最关键的 10 大安全风险，是 [[DevSecOps]] 安全测试的核心参考标准：
|
||||
1. Broken Access Control（访问控制失效）
|
||||
2. Cryptographic Failures（加密失败）
|
||||
3. Injection（注入攻击）
|
||||
4. Insecure Design（不安全设计）
|
||||
5. Security Misconfiguration（安全配置错误）
|
||||
6. Vulnerable and Outdated Components（易受攻击和过时的组件）
|
||||
7. Identification and Authentication Failures（识别和身份验证失败）
|
||||
8. Software and Data Integrity Failures（软件和数据完整性失败）
|
||||
9. Security Logging and Monitoring Failures（安全日志和监控失败）
|
||||
10. Server-Side Request Forgery（服务器端请求伪造）
|
||||
|
||||
### Other Key Projects
|
||||
- **OWASP ZAP**：开源 Web 应用安全扫描器（[[DAST]] 工具）
|
||||
- **OWASP ASVS**：应用安全验证标准
|
||||
- **OWASP SAMM**：软件保证成熟度模型
|
||||
- **OWASP Dependency-Check**：SCA 工具（[[SCA]]）
|
||||
|
||||
## Role in DevSecOps
|
||||
|
||||
在 [[DevSecOps]] 中，OWASP 提供：
|
||||
- [[DAST]] 测试的漏洞分类标准
|
||||
- [[SAST]] 工具的规则开发参考
|
||||
- 安全编码标准和最佳实践
|
||||
- 开源安全测试工具
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[DevSecOps]] — OWASP 是 DevSecOps 工具链的核心参考
|
||||
- [[DAST]] — OWASP ZAP 是主流 DAST 工具
|
||||
- [[SAST]] — OWASP 提供安全编码标准
|
||||
- [[OWASP Top Ten]] — Web 应用安全风险的权威列表
|
||||
|
||||
@@ -1,27 +1,27 @@
|
||||
---
|
||||
title: "OpenAI"
|
||||
type: entity
|
||||
tags: ["llm-provider", "openai"]
|
||||
sources: ["engineering-autonomous-optimization-architect"]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- OpenAI
|
||||
- OpenAI Inc.
|
||||
|
||||
## Definition
|
||||
OpenAI 是主要的 LLM Provider 之一，提供 GPT 系列模型（GPT-4、GPT-4o、GPT-3.5 Turbo 等）。在 [[AutonomousOptimizationArchitect]] 系统中作为主要候选 Provider 之一参与性能排名和流量路由竞争。
|
||||
|
||||
## Role in LLM Routing
|
||||
- 提供多种规模的模型供 [[AutonomousOptimizationArchitect]] 按任务类型分配
|
||||
- 模型历史性能（token 延迟、幻觉率、成本）被 [[AutonomousOptimizationArchitect]] 持续追踪并纳入 Provider 排名
|
||||
|
||||
## Key Properties
|
||||
- **Token 成本**：$2.5-15 / 1M tokens（因模型而异）
|
||||
- **延迟**：中等至高（取决于模型规模）
|
||||
- **常见用途**：代码生成、复杂推理、长文档处理
|
||||
|
||||
## Connections
|
||||
- [[Anthropic]] — 同为 LLM Provider，竞争关系，共同参与 [[SemanticRouting]]
|
||||
- [[GoogleGemini]] — 同为 LLM Provider，在性价比上与 Gemini Flash 形成竞争
|
||||
---
|
||||
title: "OpenAI"
|
||||
type: entity
|
||||
tags: ["llm-provider", "openai"]
|
||||
sources: ["engineering-autonomous-optimization-architect"]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- OpenAI
|
||||
- OpenAI Inc.
|
||||
|
||||
## Definition
|
||||
OpenAI 是主要的 LLM Provider 之一，提供 GPT 系列模型（GPT-4、GPT-4o、GPT-3.5 Turbo 等）。在 [[AutonomousOptimizationArchitect]] 系统中作为主要候选 Provider 之一参与性能排名和流量路由竞争。
|
||||
|
||||
## Role in LLM Routing
|
||||
- 提供多种规模的模型供 [[AutonomousOptimizationArchitect]] 按任务类型分配
|
||||
- 模型历史性能（token 延迟、幻觉率、成本）被 [[AutonomousOptimizationArchitect]] 持续追踪并纳入 Provider 排名
|
||||
|
||||
## Key Properties
|
||||
- **Token 成本**：$2.5-15 / 1M tokens（因模型而异）
|
||||
- **延迟**：中等至高（取决于模型规模）
|
||||
- **常见用途**：代码生成、复杂推理、长文档处理
|
||||
|
||||
## Connections
|
||||
- [[Anthropic]] — 同为 LLM Provider，竞争关系，共同参与 [[SemanticRouting]]
|
||||
- [[GoogleGemini]] — 同为 LLM Provider，在性价比上与 Gemini Flash 形成竞争
|
||||
|
||||
@@ -1,40 +1,40 @@
|
||||
---
|
||||
title: "PingMe"
|
||||
type: entity
|
||||
tags: [sms-verification, phone-number, claude]
|
||||
last_updated: 2025-12-31
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- PingMe 接码平台
|
||||
|
||||
## Overview
|
||||
PingMe 是一款新兴的短信接码（SMS Verification）平台，提供全球多个国家和地区的临时/长期手机号码，用于接收验证码。与传统一次性号码不同，PingMe 支持订阅制长期号码，稳定性更高。
|
||||
|
||||
## Key Features
|
||||
- **支持中文界面**：界面友好，中文操作体验
|
||||
- **多平台支持**：提供 App（iOS/Android）和网页端
|
||||
- **美国号码可用**：支持获取美国（+1）手机号，用于 Claude 注册
|
||||
- **订阅制号码**：可获取长期有效号码，避免一次性号码被封
|
||||
- **低门槛充值**：最低充值 2 美元
|
||||
|
||||
## Claude Registration Use Case
|
||||
Claude 注册需要美国手机号接收短信验证码：
|
||||
1. 注册 PingMe 账号（支持手机号注册）
|
||||
2. 充值至少 2 美元
|
||||
3. 选择美国区 Claude 验证码服务
|
||||
4. 获取美国长期号码（如 +1 914-577-5122）
|
||||
5. 在 Claude 注册页面填入号码，PingMe 实时接收验证码
|
||||
|
||||
## Why Not Disposable Numbers
|
||||
- 一次性号码存在时间限制，验证码过期后无法重新获取
|
||||
- 平台可能识别并拒绝一次性号码段
|
||||
- 订阅制长期号码更稳定，不易被 Claude 判定为异常
|
||||
|
||||
## Related
|
||||
- [[接码平台]]
|
||||
- [[指纹浏览器]]
|
||||
- [[IP纯净度]]
|
||||
|
||||
## 来源
|
||||
- [[如何用指纹浏览器安全注册并订阅claude-pro会员全攻略]]
|
||||
---
|
||||
title: "PingMe"
|
||||
type: entity
|
||||
tags: [sms-verification, phone-number, claude]
|
||||
last_updated: 2025-12-31
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- PingMe 接码平台
|
||||
|
||||
## Overview
|
||||
PingMe 是一款新兴的短信接码（SMS Verification）平台，提供全球多个国家和地区的临时/长期手机号码，用于接收验证码。与传统一次性号码不同，PingMe 支持订阅制长期号码，稳定性更高。
|
||||
|
||||
## Key Features
|
||||
- **支持中文界面**：界面友好，中文操作体验
|
||||
- **多平台支持**：提供 App（iOS/Android）和网页端
|
||||
- **美国号码可用**：支持获取美国（+1）手机号，用于 Claude 注册
|
||||
- **订阅制号码**：可获取长期有效号码，避免一次性号码被封
|
||||
- **低门槛充值**：最低充值 2 美元
|
||||
|
||||
## Claude Registration Use Case
|
||||
Claude 注册需要美国手机号接收短信验证码：
|
||||
1. 注册 PingMe 账号（支持手机号注册）
|
||||
2. 充值至少 2 美元
|
||||
3. 选择美国区 Claude 验证码服务
|
||||
4. 获取美国长期号码（如 +1 914-577-5122）
|
||||
5. 在 Claude 注册页面填入号码，PingMe 实时接收验证码
|
||||
|
||||
## Why Not Disposable Numbers
|
||||
- 一次性号码存在时间限制，验证码过期后无法重新获取
|
||||
- 平台可能识别并拒绝一次性号码段
|
||||
- 订阅制长期号码更稳定，不易被 Claude 判定为异常
|
||||
|
||||
## Related
|
||||
- [[接码平台]]
|
||||
- [[指纹浏览器]]
|
||||
- [[IP纯净度]]
|
||||
|
||||
## 来源
|
||||
- [[如何用指纹浏览器安全注册并订阅claude-pro会员全攻略]]
|
||||
|
||||
@@ -1,44 +1,44 @@
|
||||
---
|
||||
title: "Prometheus"
|
||||
type: entity
|
||||
tags: [monitoring, time-series, devops, observability]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Prometheus — 开源监控系统与时序数据库
|
||||
|
||||
**官方网址：** https://prometheus.io/
|
||||
|
||||
**类型：** 开源项目 / 监控系统
|
||||
|
||||
**别名：**
|
||||
- prom
|
||||
- Prometheus TSDB
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Prometheus 是由 SoundCloud 开发的开源监控系统，现由 CNCF 托管。采用**拉取（pull）模式**从配置的 targets 收集指标，存储为时间序列数据，支持强大的 PromQL 查询语言和灵活的告警规则引擎。
|
||||
|
||||
**核心特性：**
|
||||
- 多维数据模型（metric + labels）
|
||||
- PromQL 强大查询能力
|
||||
- 拉取模式优于推送（网络可控、无侵入）
|
||||
- HTTP API（易于集成）
|
||||
- Alertmanager 集成
|
||||
|
||||
**典型部署端口：** `9090`（Web UI + API）
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
- [[家庭网络环境概览_2026-04-03]]
|
||||
- [[ctp-topic-8-implementation-of-cloud-monitoring-using-micro-focus-operations-brid]]
|
||||
- [[ctp-topic-60-monitor-aws-using-hyperscale-observability-with-grafana]]
|
||||
- [[ctp-topic-67-cloud-native-observability-using-opentelemetry]]
|
||||
- [[public-cloud-learning-sessions-observability-with-opentelemetry]]
|
||||
---
|
||||
title: "Prometheus"
|
||||
type: entity
|
||||
tags: [monitoring, time-series, devops, observability]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Prometheus — 开源监控系统与时序数据库
|
||||
|
||||
**官方网址：** https://prometheus.io/
|
||||
|
||||
**类型：** 开源项目 / 监控系统
|
||||
|
||||
**别名：**
|
||||
- prom
|
||||
- Prometheus TSDB
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
Prometheus 是由 SoundCloud 开发的开源监控系统，现由 CNCF 托管。采用**拉取（pull）模式**从配置的 targets 收集指标，存储为时间序列数据，支持强大的 PromQL 查询语言和灵活的告警规则引擎。
|
||||
|
||||
**核心特性：**
|
||||
- 多维数据模型（metric + labels）
|
||||
- PromQL 强大查询能力
|
||||
- 拉取模式优于推送（网络可控、无侵入）
|
||||
- HTTP API（易于集成）
|
||||
- Alertmanager 集成
|
||||
|
||||
**典型部署端口：** `9090`（Web UI + API）
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
- [[家庭网络环境概览_2026-04-03]]
|
||||
- [[ctp-topic-8-implementation-of-cloud-monitoring-using-micro-focus-operations-brid]]
|
||||
- [[ctp-topic-60-monitor-aws-using-hyperscale-observability-with-grafana]]
|
||||
- [[ctp-topic-67-cloud-native-observability-using-opentelemetry]]
|
||||
- [[public-cloud-learning-sessions-observability-with-opentelemetry]]
|
||||
|
||||
@@ -1,35 +1,35 @@
|
||||
---
|
||||
title: "Synology DSM"
|
||||
type: entity
|
||||
tags: [synology, nas, dsm, linux, docker]
|
||||
date: 2026-05-14
|
||||
---
|
||||
|
||||
# Synology DSM
|
||||
|
||||
## Aliases
|
||||
- Synology DSM
|
||||
- DSM
|
||||
- DSM 7.x
|
||||
- 群晖 DSM
|
||||
|
||||
## Definition
|
||||
Synology DiskStation Manager（DSM）是群晖 NAS 设备的操作系统，基于 Linux 内核，提供图形化 Web 管理界面。本文档中的部署环境为 DSM 7.x（DS718），Docker 服务名称为 `pkg-ContainerManager-dockerd`。
|
||||
|
||||
## Key Characteristics for Home Server Context
|
||||
- **Docker 服务名**：`pkg-ContainerManager-dockerd`（与标准 Linux 的 `dockerd` 不同）
|
||||
- **systemd 配置目录**：`/etc/systemd/system/pkg-ContainerManager-dockerd.service.d/`（用于配置 Docker Daemon 代理）
|
||||
- **IP 地址**：典型内网地址 `192.168.3.17`
|
||||
- **QuickConnect**：群晖远程访问服务，可作为透明代理失效时的备用连接方案
|
||||
|
||||
## Known Quirks
|
||||
- Docker Daemon 的网络栈不完全遵循 V2RayA 修改的 iptables 规则，需要显式配置 systemd 代理环境变量
|
||||
- 透明代理有极小概率导致局域网连接中断，远程操作时需谨慎
|
||||
|
||||
## Related Sources
|
||||
- [[群晖NAS科学上网方法]] — V2RayA 透明代理 + Docker Daemon 代理配置
|
||||
- [[Synology-NAS上安装CloudDrive2]] — CloudDrive2 套件安装
|
||||
|
||||
## Related Entities
|
||||
- [[Synology-NAS]] — Synology NAS 硬件设备
|
||||
- [[Docker]] — DSM 上的核心容器化平台
|
||||
---
|
||||
title: "Synology DSM"
|
||||
type: entity
|
||||
tags: [synology, nas, dsm, linux, docker]
|
||||
date: 2026-05-14
|
||||
---
|
||||
|
||||
# Synology DSM
|
||||
|
||||
## Aliases
|
||||
- Synology DSM
|
||||
- DSM
|
||||
- DSM 7.x
|
||||
- 群晖 DSM
|
||||
|
||||
## Definition
|
||||
Synology DiskStation Manager（DSM）是群晖 NAS 设备的操作系统，基于 Linux 内核，提供图形化 Web 管理界面。本文档中的部署环境为 DSM 7.x（DS718），Docker 服务名称为 `pkg-ContainerManager-dockerd`。
|
||||
|
||||
## Key Characteristics for Home Server Context
|
||||
- **Docker 服务名**：`pkg-ContainerManager-dockerd`（与标准 Linux 的 `dockerd` 不同）
|
||||
- **systemd 配置目录**：`/etc/systemd/system/pkg-ContainerManager-dockerd.service.d/`（用于配置 Docker Daemon 代理）
|
||||
- **IP 地址**：典型内网地址 `192.168.3.17`
|
||||
- **QuickConnect**：群晖远程访问服务，可作为透明代理失效时的备用连接方案
|
||||
|
||||
## Known Quirks
|
||||
- Docker Daemon 的网络栈不完全遵循 V2RayA 修改的 iptables 规则，需要显式配置 systemd 代理环境变量
|
||||
- 透明代理有极小概率导致局域网连接中断，远程操作时需谨慎
|
||||
|
||||
## Related Sources
|
||||
- [[群晖NAS科学上网方法]] — V2RayA 透明代理 + Docker Daemon 代理配置
|
||||
- [[Synology-NAS上安装CloudDrive2]] — CloudDrive2 套件安装
|
||||
|
||||
## Related Entities
|
||||
- [[Synology-NAS]] — Synology NAS 硬件设备
|
||||
- [[Docker]] — DSM 上的核心容器化平台
|
||||
|
||||
@@ -1,54 +1,54 @@
|
||||
---
|
||||
title: "Synology NAS"
|
||||
type: entity
|
||||
tags: [nas, storage, nfs, samba, backup]
|
||||
date: 2026-04-28
|
||||
---
|
||||
|
||||
# Synology NAS
|
||||
|
||||
## Aliases
|
||||
- Synology NAS
|
||||
- Synology DS718
|
||||
- 群晖 NAS
|
||||
|
||||
## Definition
|
||||
Synology NAS（网络附加存储）是由群晖科技生产的私有云存储设备，提供文件存储、备份、多媒体服务等功能。在 Home Office 架构中是核心数据存储节点，通过 NFS 或 Samba 协议向 Ubuntu 服务器提供备份存储空间。
|
||||
|
||||
## Docker 套件
|
||||
- V2RayA（透明代理 + Docker Daemon 代理）：通过 Docker 部署，为 NAS 本机和 Docker pull 提供科学上网能力
|
||||
- CloudDrive2：云盘挂载（矿神源安装）
|
||||
- Portainer：Docker 容器可视化管理
|
||||
|
||||
## Core Capabilities
|
||||
- **NFS 共享**：通过 DSM 控制面板启用 NFS 服务，配置导出路径和访问权限（IP 白名单、Squash 设置）
|
||||
- **SMB/CIFS 共享**：通过 Samba 协议向 Windows/macOS 机器提供文件共享
|
||||
- **Backup Target**：作为 rsync/Clonezilla 备份的目标存储
|
||||
- **Docker 宿主**：运行 CloudDrive2、Docker Compose 服务套件
|
||||
|
||||
## Key Configurations for Ubuntu Backup
|
||||
| 配置项 | 值 |
|
||||
|--------|-----|
|
||||
| NFS 导出路径 | `/volume2/backup` |
|
||||
| Ubuntu 挂载点 | `/mnt/nas_backup` |
|
||||
| NFS 服务器 IP | `192.168.3.17` |
|
||||
| 推荐 Squash | `admin`（映射为管理员权限） |
|
||||
| 安全模式 | `sys` |
|
||||
| fstab `_netdev` | 必须加，防止开机卡死 |
|
||||
|
||||
## Related Sources
|
||||
- [[如何在ubuntu-server上通过nfs挂载synology-nas上的共享文件夹]] — NFS 挂载完整配置
|
||||
- [[ubuntu服务器通过rsync实现日常增量备份]] — rsync 备份到 Synology NAS 的完整方案
|
||||
- [[用docker安装jellyfin]] — Jellyfin 部署在 Synology NAS Docker 环境
|
||||
- [[用docker中安装navidrome]] — Navidrome 音乐服务部署
|
||||
|
||||
## Related Concepts
|
||||
- [[永久挂载]] — Synology NFS 必须在 /etc/fstab 配置才能永久生效
|
||||
- [[挂载点检查]] — 备份脚本必须在 rsync 前验证挂载状态
|
||||
- [[增量备份]] — rsync 到 Synology NAS 是典型的增量备份场景
|
||||
|
||||
## Related Entities
|
||||
- [[rsync]] — 备份工具
|
||||
- [[Clonezilla]] — 全盘镜像备份目标
|
||||
- [[Ubuntu Server]] — NFS 客户端运行环境
|
||||
- [[NFS]] — 网络文件系统协议
|
||||
---
|
||||
title: "Synology NAS"
|
||||
type: entity
|
||||
tags: [nas, storage, nfs, samba, backup]
|
||||
date: 2026-04-28
|
||||
---
|
||||
|
||||
# Synology NAS
|
||||
|
||||
## Aliases
|
||||
- Synology NAS
|
||||
- Synology DS718
|
||||
- 群晖 NAS
|
||||
|
||||
## Definition
|
||||
Synology NAS（网络附加存储）是由群晖科技生产的私有云存储设备，提供文件存储、备份、多媒体服务等功能。在 Home Office 架构中是核心数据存储节点，通过 NFS 或 Samba 协议向 Ubuntu 服务器提供备份存储空间。
|
||||
|
||||
## Docker 套件
|
||||
- V2RayA（透明代理 + Docker Daemon 代理）：通过 Docker 部署，为 NAS 本机和 Docker pull 提供科学上网能力
|
||||
- CloudDrive2：云盘挂载（矿神源安装）
|
||||
- Portainer：Docker 容器可视化管理
|
||||
|
||||
## Core Capabilities
|
||||
- **NFS 共享**：通过 DSM 控制面板启用 NFS 服务，配置导出路径和访问权限（IP 白名单、Squash 设置）
|
||||
- **SMB/CIFS 共享**：通过 Samba 协议向 Windows/macOS 机器提供文件共享
|
||||
- **Backup Target**：作为 rsync/Clonezilla 备份的目标存储
|
||||
- **Docker 宿主**：运行 CloudDrive2、Docker Compose 服务套件
|
||||
|
||||
## Key Configurations for Ubuntu Backup
|
||||
| 配置项 | 值 |
|
||||
|--------|-----|
|
||||
| NFS 导出路径 | `/volume2/backup` |
|
||||
| Ubuntu 挂载点 | `/mnt/nas_backup` |
|
||||
| NFS 服务器 IP | `192.168.3.17` |
|
||||
| 推荐 Squash | `admin`（映射为管理员权限） |
|
||||
| 安全模式 | `sys` |
|
||||
| fstab `_netdev` | 必须加，防止开机卡死 |
|
||||
|
||||
## Related Sources
|
||||
- [[如何在ubuntu-server上通过nfs挂载synology-nas上的共享文件夹]] — NFS 挂载完整配置
|
||||
- [[ubuntu服务器通过rsync实现日常增量备份]] — rsync 备份到 Synology NAS 的完整方案
|
||||
- [[用docker安装jellyfin]] — Jellyfin 部署在 Synology NAS Docker 环境
|
||||
- [[用docker中安装navidrome]] — Navidrome 音乐服务部署
|
||||
|
||||
## Related Concepts
|
||||
- [[永久挂载]] — Synology NFS 必须在 /etc/fstab 配置才能永久生效
|
||||
- [[挂载点检查]] — 备份脚本必须在 rsync 前验证挂载状态
|
||||
- [[增量备份]] — rsync 到 Synology NAS 是典型的增量备份场景
|
||||
|
||||
## Related Entities
|
||||
- [[rsync]] — 备份工具
|
||||
- [[Clonezilla]] — 全盘镜像备份目标
|
||||
- [[Ubuntu Server]] — NFS 客户端运行环境
|
||||
- [[NFS]] — 网络文件系统协议
|
||||
|
||||
@@ -1,47 +1,47 @@
|
||||
---
|
||||
title: "V2RayA"
|
||||
type: entity
|
||||
tags: [vpn, proxy, transparent-proxy, docker, v2ray, open-source]
|
||||
date: 2026-05-14
|
||||
---
|
||||
|
||||
# V2RayA
|
||||
|
||||
## Aliases
|
||||
- V2RayA
|
||||
- v2raya
|
||||
- V2rayA
|
||||
|
||||
## Definition
|
||||
V2RayA 是基于 V2Ray 内核的轻量级透明代理 Web 管理界面，支持通过 Docker 部署在 NAS/服务器环境中，提供可视化的节点管理、分流规则配置和透明代理开关功能。
|
||||
|
||||
## Core Capabilities
|
||||
- **Web UI 管理**：通过浏览器配置代理节点、路由规则和透明代理开关
|
||||
- **透明代理**：劫持系统出站流量（基于 iptables），无需客户端显式配置
|
||||
- **Traffic Splitting（分流）**：支持多种分流规则，包括 GFWList、大陆白名单、全局代理等
|
||||
- **Docker 部署**：官方提供 Docker 镜像 `mzz2017/v2raya`，支持 Host 网络模式
|
||||
|
||||
## Key Configuration
|
||||
| 配置项 | 值 |
|
||||
|--------|-----|
|
||||
| Docker 镜像 | `mzz2017/v2raya` |
|
||||
| 推荐网络模式 | `--network=host` |
|
||||
| HTTP 代理端口 | 20171（默认） |
|
||||
| Web UI 端口 | 2017 |
|
||||
| 推荐分流模式 | "大陆白名单（Whitelist of Mainland China）" |
|
||||
| 环境变量 | `IPTABLES_MODE=legacy` |
|
||||
|
||||
## Related Sources
|
||||
- [[群晖NAS科学上网方法]] — V2RayA 在群晖 NAS 上的完整安装与 Docker Daemon 代理配置
|
||||
- [[Ubuntu-Server科学上网]] — V2RayA 在 Ubuntu Server 上的安装
|
||||
|
||||
## Related Concepts
|
||||
- [[透明代理]] — V2RayA 的核心实现机制
|
||||
- [[分流模式]] — V2RayA 的路由策略
|
||||
- [[Docker-Daemon-Proxy]] — V2RayA 的替代方案，直接为 Docker 守护进程配置代理
|
||||
- [[iptables]] — 透明代理依赖的内核防火墙规则
|
||||
|
||||
## Related Entities
|
||||
- [[Synology-DSM]] — V2RayA 的典型部署平台之一
|
||||
- [[Docker]] — V2RayA 的运行环境和被代理对象
|
||||
- [[Xray]] — V2Ray 的上游核心，V2RayA 基于此运行
|
||||
---
|
||||
title: "V2RayA"
|
||||
type: entity
|
||||
tags: [vpn, proxy, transparent-proxy, docker, v2ray, open-source]
|
||||
date: 2026-05-14
|
||||
---
|
||||
|
||||
# V2RayA
|
||||
|
||||
## Aliases
|
||||
- V2RayA
|
||||
- v2raya
|
||||
- V2rayA
|
||||
|
||||
## Definition
|
||||
V2RayA 是基于 V2Ray 内核的轻量级透明代理 Web 管理界面，支持通过 Docker 部署在 NAS/服务器环境中，提供可视化的节点管理、分流规则配置和透明代理开关功能。
|
||||
|
||||
## Core Capabilities
|
||||
- **Web UI 管理**：通过浏览器配置代理节点、路由规则和透明代理开关
|
||||
- **透明代理**：劫持系统出站流量（基于 iptables），无需客户端显式配置
|
||||
- **Traffic Splitting（分流）**：支持多种分流规则，包括 GFWList、大陆白名单、全局代理等
|
||||
- **Docker 部署**：官方提供 Docker 镜像 `mzz2017/v2raya`，支持 Host 网络模式
|
||||
|
||||
## Key Configuration
|
||||
| 配置项 | 值 |
|
||||
|--------|-----|
|
||||
| Docker 镜像 | `mzz2017/v2raya` |
|
||||
| 推荐网络模式 | `--network=host` |
|
||||
| HTTP 代理端口 | 20171（默认） |
|
||||
| Web UI 端口 | 2017 |
|
||||
| 推荐分流模式 | "大陆白名单（Whitelist of Mainland China）" |
|
||||
| 环境变量 | `IPTABLES_MODE=legacy` |
|
||||
|
||||
## Related Sources
|
||||
- [[群晖NAS科学上网方法]] — V2RayA 在群晖 NAS 上的完整安装与 Docker Daemon 代理配置
|
||||
- [[Ubuntu-Server科学上网]] — V2RayA 在 Ubuntu Server 上的安装
|
||||
|
||||
## Related Concepts
|
||||
- [[透明代理]] — V2RayA 的核心实现机制
|
||||
- [[分流模式]] — V2RayA 的路由策略
|
||||
- [[Docker-Daemon-Proxy]] — V2RayA 的替代方案，直接为 Docker 守护进程配置代理
|
||||
- [[iptables]] — 透明代理依赖的内核防火墙规则
|
||||
|
||||
## Related Entities
|
||||
- [[Synology-DSM]] — V2RayA 的典型部署平台之一
|
||||
- [[Docker]] — V2RayA 的运行环境和被代理对象
|
||||
- [[Xray]] — V2Ray 的上游核心，V2RayA 基于此运行
|
||||
|
||||
@@ -1,39 +1,39 @@
|
||||
---
|
||||
title: "WildCard"
|
||||
type: entity
|
||||
tags: [virtual-card, payment, cross-border]
|
||||
last_updated: 2025-12-31
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- WildCard 虚拟信用卡
|
||||
- 野卡
|
||||
|
||||
## Overview
|
||||
WildCard 是一款面向中国用户的虚拟信用卡（Virtual Credit Card, VCC）服务，不依赖实体银行卡，通过线上注册和支付宝充值，解决国内用户跨境支付的难题。
|
||||
|
||||
## Key Features
|
||||
- **无实体卡**：纯线上运营，开卡即用
|
||||
- **支付宝充值**：支持支付宝账户直接充值，方便国内用户
|
||||
- **手机号注册**：仅需手机号验证，无需复杂资质审核
|
||||
- **多场景支持**：支持 OpenAI（ChatGPT Plus）、Claude Pro、Midjourney 等海外AI服务订阅
|
||||
- **邀请链接**：yeka.ai/i/UPHSP
|
||||
|
||||
## Claude Pro Subscription Use Case
|
||||
Claude Pro 订阅（月费 20 美元）国内信用卡无法直接支付，WildCard 解决方案：
|
||||
1. 注册 WildCard 账号（yeka.ai/i/UPHSP 邀请链接）
|
||||
2. 手机号验证 + 支付宝充值（建议充值 22 美元以上以覆盖月费）
|
||||
3. 充值成功后，绑定 WildCard 信用卡信息到 Claude Pro 订阅页面
|
||||
4. 完成支付，开通 Claude Pro 会员
|
||||
|
||||
## Why Virtual Cards for AI Subscriptions
|
||||
- 国内发行的 Visa/Mastercard 信用卡默认不支持境外AI服务消费
|
||||
- 虚拟卡可绕过地域限制，且可随时注销，控制风险
|
||||
- WildCard 专门针对中国用户优化，支付宝充值降低门槛
|
||||
|
||||
## Related
|
||||
- [[接码平台]]
|
||||
- [[指纹浏览器]]
|
||||
|
||||
## 来源
|
||||
- [[如何用指纹浏览器安全注册并订阅claude-pro会员全攻略]]
|
||||
---
|
||||
title: "WildCard"
|
||||
type: entity
|
||||
tags: [virtual-card, payment, cross-border]
|
||||
last_updated: 2025-12-31
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- WildCard 虚拟信用卡
|
||||
- 野卡
|
||||
|
||||
## Overview
|
||||
WildCard 是一款面向中国用户的虚拟信用卡（Virtual Credit Card, VCC）服务，不依赖实体银行卡，通过线上注册和支付宝充值，解决国内用户跨境支付的难题。
|
||||
|
||||
## Key Features
|
||||
- **无实体卡**：纯线上运营，开卡即用
|
||||
- **支付宝充值**：支持支付宝账户直接充值，方便国内用户
|
||||
- **手机号注册**：仅需手机号验证，无需复杂资质审核
|
||||
- **多场景支持**：支持 OpenAI（ChatGPT Plus）、Claude Pro、Midjourney 等海外AI服务订阅
|
||||
- **邀请链接**：yeka.ai/i/UPHSP
|
||||
|
||||
## Claude Pro Subscription Use Case
|
||||
Claude Pro 订阅（月费 20 美元）国内信用卡无法直接支付，WildCard 解决方案：
|
||||
1. 注册 WildCard 账号（yeka.ai/i/UPHSP 邀请链接）
|
||||
2. 手机号验证 + 支付宝充值（建议充值 22 美元以上以覆盖月费）
|
||||
3. 充值成功后，绑定 WildCard 信用卡信息到 Claude Pro 订阅页面
|
||||
4. 完成支付，开通 Claude Pro 会员
|
||||
|
||||
## Why Virtual Cards for AI Subscriptions
|
||||
- 国内发行的 Visa/Mastercard 信用卡默认不支持境外AI服务消费
|
||||
- 虚拟卡可绕过地域限制，且可随时注销，控制风险
|
||||
- WildCard 专门针对中国用户优化，支付宝充值降低门槛
|
||||
|
||||
## Related
|
||||
- [[接码平台]]
|
||||
- [[指纹浏览器]]
|
||||
|
||||
## 来源
|
||||
- [[如何用指纹浏览器安全注册并订阅claude-pro会员全攻略]]
|
||||
|
||||
@@ -1,48 +1,48 @@
|
||||
---
|
||||
title: "cAdvisor"
|
||||
type: entity
|
||||
tags: [monitoring, container, docker, prometheus, devops]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## cAdvisor — Google 容器指标采集器
|
||||
|
||||
**官方网址：** https://github.com/google/cadvisor
|
||||
|
||||
**类型：** 开源项目 / 容器监控工具
|
||||
|
||||
**别名：**
|
||||
- cadvisor
|
||||
- Google cAdvisor
|
||||
- Container Advisor
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
cAdvisor 是 Google 开发的容器监控工具，自动采集单个节点上运行的所有容器的资源使用情况（CPU、内存、网络、磁盘 I/O），并以 Prometheus 可抓取的格式暴露指标。
|
||||
|
||||
**采集指标示例：**
|
||||
- `container_cpu_usage_seconds_total` — 容器 CPU 使用
|
||||
- `container_memory_usage_bytes` — 容器内存使用
|
||||
- `container_network_receive_bytes_total` — 容器网络接收
|
||||
- `container_last_seen` — 容器最后活跃时间
|
||||
- `container_restart_total` — 容器重启次数
|
||||
|
||||
**典型部署：**
|
||||
- Docker: `gcr.io/cadvisor/cadvisor:latest`
|
||||
- 端口：`8080`
|
||||
- 需要挂载：`/var/run`（Docker socket）、`/sys`、`/var/lib/docker/`
|
||||
|
||||
**关键告警规则示例：**
|
||||
- 容器异常退出: `increase(container_last_seen[5m]) == 0`（容器未上报即可能已退出）
|
||||
|
||||
**安全注意：** 需审慎挂载 Docker socket（权限等同于宿主机 root）
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
---
|
||||
title: "cAdvisor"
|
||||
type: entity
|
||||
tags: [monitoring, container, docker, prometheus, devops]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## cAdvisor — Google 容器指标采集器
|
||||
|
||||
**官方网址：** https://github.com/google/cadvisor
|
||||
|
||||
**类型：** 开源项目 / 容器监控工具
|
||||
|
||||
**别名：**
|
||||
- cadvisor
|
||||
- Google cAdvisor
|
||||
- Container Advisor
|
||||
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
cAdvisor 是 Google 开发的容器监控工具，自动采集单个节点上运行的所有容器的资源使用情况（CPU、内存、网络、磁盘 I/O），并以 Prometheus 可抓取的格式暴露指标。
|
||||
|
||||
**采集指标示例：**
|
||||
- `container_cpu_usage_seconds_total` — 容器 CPU 使用
|
||||
- `container_memory_usage_bytes` — 容器内存使用
|
||||
- `container_network_receive_bytes_total` — 容器网络接收
|
||||
- `container_last_seen` — 容器最后活跃时间
|
||||
- `container_restart_total` — 容器重启次数
|
||||
|
||||
**典型部署：**
|
||||
- Docker: `gcr.io/cadvisor/cadvisor:latest`
|
||||
- 端口：`8080`
|
||||
- 需要挂载：`/var/run`（Docker socket）、`/sys`、`/var/lib/docker/`
|
||||
|
||||
**关键告警规则示例：**
|
||||
- 容器异常退出: `increase(container_last_seen[5m]) == 0`（容器未上报即可能已退出）
|
||||
|
||||
**安全注意：** 需审慎挂载 Docker socket（权限等同于宿主机 root）
|
||||
|
||||
---
|
||||
|
||||
## Used By
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
## Related Sources
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]
|
||||
|
||||
@@ -1,68 +1,68 @@
|
||||
---
|
||||
title: "frp"
|
||||
type: entity
|
||||
tags: [networking, open-source, golang, tunneling, self-hosted]
|
||||
last_updated: 2026-04-03
|
||||
---
|
||||
|
||||
# frp
|
||||
|
||||
## Overview
|
||||
**frp（Fast Reverse Proxy）** 是一款开源的高性能内网穿透工具，由 Go 语言编写，通过客户端-服务端架构（frps + frpc）建立反向隧道，使处于 NAT 或防火墙后的内网服务可以被公网访问。本 Wiki 使用 **frp v0.65.0**（INI 配置文件格式）。
|
||||
|
||||
## Core Architecture
|
||||
```
|
||||
公网用户 → VPS:7000(frps) ←——— 反向隧道 ←——— frpc(内网设备)
|
||||
```
|
||||
|
||||
## Components
|
||||
- **frps**（frp server）：运行在公网 VPS，监听 7000 端口（默认），接收 frpc 连接，管理端口映射
|
||||
- **frpc**（frp client）：运行在内网设备，主动连接 frps，建立反向隧道
|
||||
|
||||
## Supported Protocol Types
|
||||
| 类型 | 说明 | 适用场景 |
|
||||
|------|------|---------|
|
||||
| TCP | 原始 TCP 流量 | SSH、任意 TCP 端口 |
|
||||
| UDP | 原始 UDP 流量 | DNS、视频流 |
|
||||
| HTTP/HTTPS | 应用层代理 | Web 服务 |
|
||||
| STCP | 加密 TCP | 安全内网访问 |
|
||||
| SUDP | 加密 UDP | 安全数据传输 |
|
||||
| XTCP | P2P UDP | 穿越对称型 NAT |
|
||||
|
||||
## 在本 Wiki 中的应用
|
||||
- [[通过VPS+内网反向代理实现域名访问内网穿透]]：完整实践指南（frps + Caddy + 阿里云 DNS）
|
||||
- [[ubuntu-安装-frp-0-65-0-x86-64-操作笔记]]：Ubuntu frpc 客户端安装配置
|
||||
- [[mac-mini-安装-frp-0-65-0-arm64-操作笔记]]：Mac Mini ARM64 安装配置
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]：通过 frp 穿透 Grafana/Prometheus 端口
|
||||
|
||||
## frpc 端口映射表（内网 Ubuntu 192.168.3.47）
|
||||
| 服务 | local_port | remote_port |
|
||||
|------|-----------|-------------|
|
||||
| n8n | 5678 | 15678 |
|
||||
| Transmission | 9091 | 19091 |
|
||||
| Grafana | 3000 | 13000 |
|
||||
| SSH | 22 | 60022 |
|
||||
|
||||
## SSH 穿透注意事项
|
||||
SSH 穿透使用 `type = tcp`，不走 Caddy（Caddy 只处理 HTTP/HTTPS）。SSH 连接命令：`ssh -p 60022 user@ubuntu1.ishenwei.online`
|
||||
|
||||
## Troubleshooting
|
||||
详见 [[通过VPS+内网反向代理实现域名访问内网穿透]] 故障排查章节：
|
||||
1. 确认 frps 监听端口 `ss -lntup | grep frps`
|
||||
2. 确认 token 与 frpc 一致 `journalctl -u frps -n 100`
|
||||
3. 确认防火墙放行 7000 端口
|
||||
4. telnet 诊断确认连接是否到达 frps
|
||||
5. 强制重启 frps + frpc
|
||||
|
||||
## Related Entities
|
||||
- [[RackNerd]]：托管 frps 的 VPS 提供商（IP: 192.227.222.142）
|
||||
- [[VPS]]：运行 frps 的公网服务器
|
||||
|
||||
## Related Concepts
|
||||
- [[内网穿透]]：frp 是实现内网穿透的工具
|
||||
- [[反向代理]]：Caddy 在 frp 上层提供 HTTPS 访问
|
||||
- [[TCP隧道]]：frp 的 TCP 类型映射建立 TCP 隧道
|
||||
|
||||
## References
|
||||
- GitHub: https://github.com/fatedier/frp
|
||||
- 文档: https://github.com/fatedier/frp#configuration
|
||||
---
|
||||
title: "frp"
|
||||
type: entity
|
||||
tags: [networking, open-source, golang, tunneling, self-hosted]
|
||||
last_updated: 2026-04-03
|
||||
---
|
||||
|
||||
# frp
|
||||
|
||||
## Overview
|
||||
**frp（Fast Reverse Proxy）** 是一款开源的高性能内网穿透工具，由 Go 语言编写，通过客户端-服务端架构（frps + frpc）建立反向隧道，使处于 NAT 或防火墙后的内网服务可以被公网访问。本 Wiki 使用 **frp v0.65.0**（INI 配置文件格式）。
|
||||
|
||||
## Core Architecture
|
||||
```
|
||||
公网用户 → VPS:7000(frps) ←——— 反向隧道 ←——— frpc(内网设备)
|
||||
```
|
||||
|
||||
## Components
|
||||
- **frps**（frp server）：运行在公网 VPS，监听 7000 端口（默认），接收 frpc 连接，管理端口映射
|
||||
- **frpc**（frp client）：运行在内网设备，主动连接 frps，建立反向隧道
|
||||
|
||||
## Supported Protocol Types
|
||||
| 类型 | 说明 | 适用场景 |
|
||||
|------|------|---------|
|
||||
| TCP | 原始 TCP 流量 | SSH、任意 TCP 端口 |
|
||||
| UDP | 原始 UDP 流量 | DNS、视频流 |
|
||||
| HTTP/HTTPS | 应用层代理 | Web 服务 |
|
||||
| STCP | 加密 TCP | 安全内网访问 |
|
||||
| SUDP | 加密 UDP | 安全数据传输 |
|
||||
| XTCP | P2P UDP | 穿越对称型 NAT |
|
||||
|
||||
## 在本 Wiki 中的应用
|
||||
- [[通过VPS+内网反向代理实现域名访问内网穿透]]：完整实践指南（frps + Caddy + 阿里云 DNS）
|
||||
- [[ubuntu-安装-frp-0-65-0-x86-64-操作笔记]]：Ubuntu frpc 客户端安装配置
|
||||
- [[mac-mini-安装-frp-0-65-0-arm64-操作笔记]]：Mac Mini ARM64 安装配置
|
||||
- [[家庭监控方案-prometheus-grafana-node-exporter-cadvisor-blackbox]]：通过 frp 穿透 Grafana/Prometheus 端口
|
||||
|
||||
## frpc 端口映射表（内网 Ubuntu 192.168.3.47）
|
||||
| 服务 | local_port | remote_port |
|
||||
|------|-----------|-------------|
|
||||
| n8n | 5678 | 15678 |
|
||||
| Transmission | 9091 | 19091 |
|
||||
| Grafana | 3000 | 13000 |
|
||||
| SSH | 22 | 60022 |
|
||||
|
||||
## SSH 穿透注意事项
|
||||
SSH 穿透使用 `type = tcp`，不走 Caddy（Caddy 只处理 HTTP/HTTPS）。SSH 连接命令：`ssh -p 60022 user@ubuntu1.ishenwei.online`
|
||||
|
||||
## Troubleshooting
|
||||
详见 [[通过VPS+内网反向代理实现域名访问内网穿透]] 故障排查章节：
|
||||
1. 确认 frps 监听端口 `ss -lntup | grep frps`
|
||||
2. 确认 token 与 frpc 一致 `journalctl -u frps -n 100`
|
||||
3. 确认防火墙放行 7000 端口
|
||||
4. telnet 诊断确认连接是否到达 frps
|
||||
5. 强制重启 frps + frpc
|
||||
|
||||
## Related Entities
|
||||
- [[RackNerd]]：托管 frps 的 VPS 提供商（IP: 192.227.222.142）
|
||||
- [[VPS]]：运行 frps 的公网服务器
|
||||
|
||||
## Related Concepts
|
||||
- [[内网穿透]]：frp 是实现内网穿透的工具
|
||||
- [[反向代理]]：Caddy 在 frp 上层提供 HTTPS 访问
|
||||
- [[TCP隧道]]：frp 的 TCP 类型映射建立 TCP 隧道
|
||||
|
||||
## References
|
||||
- GitHub: https://github.com/fatedier/frp
|
||||
- 文档: https://github.com/fatedier/frp#configuration
|
||||
|
||||
@@ -1,98 +1,98 @@
|
||||
---
|
||||
title: "rsync"
|
||||
type: entity
|
||||
tags: [backup, linux, sync, incremental]
|
||||
date: 2026-04-26
|
||||
---
|
||||
|
||||
# rsync
|
||||
|
||||
## Overview
|
||||
**rsync**（Remote Sync）是一款开源增量文件同步工具，广泛用于 Linux/Unix 系统间的备份和同步操作。它通过高效差异算法，仅传输源文件和目标文件之间的差异部分，实现带宽和时间的高效利用。
|
||||
|
||||
## Key Characteristics
|
||||
| 特性 | 说明 |
|
||||
|------|------|
|
||||
| **增量同步** | 仅传输变更部分，支持 `-a`（归档）、`-v`（详细）、`-z`（压缩传输） |
|
||||
| **协议支持** | 本地、SSH、Rsync Daemon、NFS、Samba |
|
||||
| **权限保留** | `-a` 保留文件所有权、时间戳、权限等属性 |
|
||||
| **Dry Run** | `--dry-run` / `-n` 预览同步效果，不实际执行 |
|
||||
| **删除选项** | `--delete` 同步目标端多余文件（谨慎使用） |
|
||||
|
||||
## Common Usage Patterns
|
||||
|
||||
### 1. 本地到 NFS 挂载点（Home Server 备份）
|
||||
```bash
|
||||
# 同步 /home/user/data 到 NAS 挂载点
|
||||
rsync -avz --delete /home/user/data/ /mnt/nas_backup/user_data/
|
||||
```
|
||||
|
||||
### 2. 通过 SSH 远程同步
|
||||
```bash
|
||||
# 远程备份（需 SSH key 免密）
|
||||
rsync -avz -e ssh /local/path/ user@remote:/remote/path/
|
||||
```
|
||||
|
||||
### 3. 自动化备份脚本（推荐）
|
||||
```bash
|
||||
#!/bin/bash
|
||||
# /usr/local/bin/rsync_backup.sh
|
||||
|
||||
SOURCE_DIR="/home/ubuntu/data"
|
||||
TARGET_DIR="/mnt/nas_backup"
|
||||
LOG_FILE="/var/log/rsync_backup.log"
|
||||
|
||||
# 挂载点安全检查
|
||||
if ! mountpoint -q $TARGET_DIR; then
|
||||
echo "$(date) 错误：NAS 未挂载，备份任务取消！" >> $LOG_FILE
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# 执行增量同步
|
||||
rsync -avz --delete --bwlimit=5000 \
|
||||
$SOURCE_DIR/ $TARGET_DIR/ \
|
||||
>> $LOG_FILE 2>&1
|
||||
|
||||
echo "$(date) 备份完成" >> $LOG_FILE
|
||||
```
|
||||
|
||||
## Key Parameters for NAS Backup
|
||||
| 参数 | 用途 |
|
||||
|------|------|
|
||||
| `-a` | 归档模式（保留权限、时间戳、所有者） |
|
||||
| `-v` | 详细输出 |
|
||||
| `-z` | 压缩传输（节省带宽） |
|
||||
| `--delete` | 目标端删除源端不存在的文件 |
|
||||
| `--bwlimit=5000` | 限速 5000 KB/s，保护 NAS 性能 |
|
||||
| `-n` / `--dry-run` | 预览模式，正式运行前必测 |
|
||||
|
||||
## rsync + NFS 备份工作流
|
||||
```
|
||||
Ubuntu Server (rsync 客户端)
|
||||
→ 挂载点 /mnt/nas_backup (NFS)
|
||||
→ Synology NAS (NFS 服务端, volume2/backup)
|
||||
```
|
||||
|
||||
**关键依赖**：
|
||||
1. Synology DSM NFS 权限已配置（Squash=admin）
|
||||
2. Ubuntu 已通过 /etc/fstab 永久挂载 NFS
|
||||
3. 挂载点检查通过后再执行 rsync
|
||||
|
||||
## Related Concepts
|
||||
- [[永久挂载]] — rsync 备份目标端必须先完成 NFS 永久挂载
|
||||
- [[挂载点检查]] — rsync 备份脚本的安全前置检查
|
||||
- [[增量备份]] — rsync 是增量备份的核心工具
|
||||
- [[NFS]] — NFS 是 rsync 备份到 NAS 的网络传输层
|
||||
- [[Cron定时任务]] — rsync 通常通过 Cron 实现定时自动执行
|
||||
|
||||
## Related Sources
|
||||
- [[ubuntu服务器通过rsync实现日常增量备份]] — rsync + Cron + NFS 完整备份方案
|
||||
- [[如何在ubuntu-server上通过nfs挂载synology-nas上的共享文件夹]] — NFS 挂载配置
|
||||
|
||||
## Related Entities
|
||||
- [[Ubuntu Server]] — rsync 客户端运行环境
|
||||
- [[Synology-NAS]] — rsync 备份的目标 NAS 存储
|
||||
|
||||
## References
|
||||
- rsync 官网: https://rsync.samba.org/
|
||||
- man rsync (本地查看)
|
||||
---
|
||||
title: "rsync"
|
||||
type: entity
|
||||
tags: [backup, linux, sync, incremental]
|
||||
date: 2026-04-26
|
||||
---
|
||||
|
||||
# rsync
|
||||
|
||||
## Overview
|
||||
**rsync**（Remote Sync）是一款开源增量文件同步工具，广泛用于 Linux/Unix 系统间的备份和同步操作。它通过高效差异算法，仅传输源文件和目标文件之间的差异部分，实现带宽和时间的高效利用。
|
||||
|
||||
## Key Characteristics
|
||||
| 特性 | 说明 |
|
||||
|------|------|
|
||||
| **增量同步** | 仅传输变更部分，支持 `-a`（归档）、`-v`（详细）、`-z`（压缩传输） |
|
||||
| **协议支持** | 本地、SSH、Rsync Daemon、NFS、Samba |
|
||||
| **权限保留** | `-a` 保留文件所有权、时间戳、权限等属性 |
|
||||
| **Dry Run** | `--dry-run` / `-n` 预览同步效果，不实际执行 |
|
||||
| **删除选项** | `--delete` 同步目标端多余文件（谨慎使用） |
|
||||
|
||||
## Common Usage Patterns
|
||||
|
||||
### 1. 本地到 NFS 挂载点（Home Server 备份）
|
||||
```bash
|
||||
# 同步 /home/user/data 到 NAS 挂载点
|
||||
rsync -avz --delete /home/user/data/ /mnt/nas_backup/user_data/
|
||||
```
|
||||
|
||||
### 2. 通过 SSH 远程同步
|
||||
```bash
|
||||
# 远程备份（需 SSH key 免密）
|
||||
rsync -avz -e ssh /local/path/ user@remote:/remote/path/
|
||||
```
|
||||
|
||||
### 3. 自动化备份脚本（推荐）
|
||||
```bash
|
||||
#!/bin/bash
|
||||
# /usr/local/bin/rsync_backup.sh
|
||||
|
||||
SOURCE_DIR="/home/ubuntu/data"
|
||||
TARGET_DIR="/mnt/nas_backup"
|
||||
LOG_FILE="/var/log/rsync_backup.log"
|
||||
|
||||
# 挂载点安全检查
|
||||
if ! mountpoint -q $TARGET_DIR; then
|
||||
echo "$(date) 错误：NAS 未挂载，备份任务取消！" >> $LOG_FILE
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# 执行增量同步
|
||||
rsync -avz --delete --bwlimit=5000 \
|
||||
$SOURCE_DIR/ $TARGET_DIR/ \
|
||||
>> $LOG_FILE 2>&1
|
||||
|
||||
echo "$(date) 备份完成" >> $LOG_FILE
|
||||
```
|
||||
|
||||
## Key Parameters for NAS Backup
|
||||
| 参数 | 用途 |
|
||||
|------|------|
|
||||
| `-a` | 归档模式（保留权限、时间戳、所有者） |
|
||||
| `-v` | 详细输出 |
|
||||
| `-z` | 压缩传输（节省带宽） |
|
||||
| `--delete` | 目标端删除源端不存在的文件 |
|
||||
| `--bwlimit=5000` | 限速 5000 KB/s，保护 NAS 性能 |
|
||||
| `-n` / `--dry-run` | 预览模式，正式运行前必测 |
|
||||
|
||||
## rsync + NFS 备份工作流
|
||||
```
|
||||
Ubuntu Server (rsync 客户端)
|
||||
→ 挂载点 /mnt/nas_backup (NFS)
|
||||
→ Synology NAS (NFS 服务端, volume2/backup)
|
||||
```
|
||||
|
||||
**关键依赖**：
|
||||
1. Synology DSM NFS 权限已配置（Squash=admin）
|
||||
2. Ubuntu 已通过 /etc/fstab 永久挂载 NFS
|
||||
3. 挂载点检查通过后再执行 rsync
|
||||
|
||||
## Related Concepts
|
||||
- [[永久挂载]] — rsync 备份目标端必须先完成 NFS 永久挂载
|
||||
- [[挂载点检查]] — rsync 备份脚本的安全前置检查
|
||||
- [[增量备份]] — rsync 是增量备份的核心工具
|
||||
- [[NFS]] — NFS 是 rsync 备份到 NAS 的网络传输层
|
||||
- [[Cron定时任务]] — rsync 通常通过 Cron 实现定时自动执行
|
||||
|
||||
## Related Sources
|
||||
- [[ubuntu服务器通过rsync实现日常增量备份]] — rsync + Cron + NFS 完整备份方案
|
||||
- [[如何在ubuntu-server上通过nfs挂载synology-nas上的共享文件夹]] — NFS 挂载配置
|
||||
|
||||
## Related Entities
|
||||
- [[Ubuntu Server]] — rsync 客户端运行环境
|
||||
- [[Synology-NAS]] — rsync 备份的目标 NAS 存储
|
||||
|
||||
## References
|
||||
- rsync 官网: https://rsync.samba.org/
|
||||
- man rsync (本地查看)
|
||||
|
||||
@@ -1,31 +1,31 @@
|
||||
# 梅林固件
|
||||
|
||||
## Aliases
|
||||
- Merlin Firmware
|
||||
- ASUSWRT-Merlin
|
||||
- 梅林固件
|
||||
|
||||
## Basic Info
|
||||
- **Type**: 第三方路由器固件
|
||||
- **Developer**: Eric Sauvageau
|
||||
- **Based On**: 华硕官方固件（ASUSWRT）
|
||||
- **Platforms**: 华硕路由器、网件路由器（部分型号）
|
||||
|
||||
## Description
|
||||
梅林固件是基于华硕官方路由器固件的第三方改良版本，由开发者Eric Sauvageau维护。它在原厂固件基础上增加了更多高级功能和插件支持，是路由器玩家和科学上网用户最常使用的第三方固件之一。
|
||||
|
||||
## Key Features
|
||||
- 支持更多插件（软件中心）
|
||||
- 高级网络配置选项
|
||||
- JFFS 分区支持（用于安装插件）
|
||||
- 科学上网插件支持
|
||||
- SSH/Telnet 远程访问
|
||||
- 更灵活的安全设置
|
||||
|
||||
## Related
|
||||
- [[网件RAX50]] — 支持梅林固件的路由器型号
|
||||
- [[MerlinClash插件]] — 梅林固件上的科学上网插件
|
||||
- [[过渡固件]] — 刷入梅林固件的前置固件
|
||||
- [[策略组分流]] — MerlinClash 的核心功能
|
||||
- [[故障转移]] — MerlinClash 配套可靠性机制
|
||||
- [[订阅机制]] — MerlinClash 节点配置来源
|
||||
# 梅林固件
|
||||
|
||||
## Aliases
|
||||
- Merlin Firmware
|
||||
- ASUSWRT-Merlin
|
||||
- 梅林固件
|
||||
|
||||
## Basic Info
|
||||
- **Type**: 第三方路由器固件
|
||||
- **Developer**: Eric Sauvageau
|
||||
- **Based On**: 华硕官方固件（ASUSWRT）
|
||||
- **Platforms**: 华硕路由器、网件路由器（部分型号）
|
||||
|
||||
## Description
|
||||
梅林固件是基于华硕官方路由器固件的第三方改良版本，由开发者Eric Sauvageau维护。它在原厂固件基础上增加了更多高级功能和插件支持，是路由器玩家和科学上网用户最常使用的第三方固件之一。
|
||||
|
||||
## Key Features
|
||||
- 支持更多插件（软件中心）
|
||||
- 高级网络配置选项
|
||||
- JFFS 分区支持（用于安装插件）
|
||||
- 科学上网插件支持
|
||||
- SSH/Telnet 远程访问
|
||||
- 更灵活的安全设置
|
||||
|
||||
## Related
|
||||
- [[网件RAX50]] — 支持梅林固件的路由器型号
|
||||
- [[MerlinClash插件]] — 梅林固件上的科学上网插件
|
||||
- [[过渡固件]] — 刷入梅林固件的前置固件
|
||||
- [[策略组分流]] — MerlinClash 的核心功能
|
||||
- [[故障转移]] — MerlinClash 配套可靠性机制
|
||||
- [[订阅机制]] — MerlinClash 节点配置来源
|
||||
|
||||
@@ -1,22 +1,22 @@
|
||||
# 网件RAX50
|
||||
|
||||
## Aliases
|
||||
- NETGEAR Nighthawk RAX50
|
||||
- 网件RAX50
|
||||
- RAX50
|
||||
|
||||
## Basic Info
|
||||
- **Type**: 路由器（网络硬件）
|
||||
- **Manufacturer**: NETGEAR（网件）
|
||||
- **Model**: Nighthawk RAX50
|
||||
- **WiFi Standard**: WiFi 6 (802.11ax)
|
||||
- **Bands**: 双频 (2.4GHz + 5GHz)
|
||||
- **Class**: AX3000
|
||||
|
||||
## Description
|
||||
网件RAX50是一款支持WiFi 6的双频路由器，型号为Nighthawk RAX50。它支持刷入第三方梅林固件以扩展功能，包括安装科学上网插件。
|
||||
|
||||
## Related
|
||||
- [[梅林固件]] — RAX50 支持的第三方固件
|
||||
- [[MerlinClash插件]] — 梅林固件上的科学上网插件
|
||||
- sources: [[网件rax50路由器刷梅林固件与科学上网插件安装教程]]
|
||||
# 网件RAX50
|
||||
|
||||
## Aliases
|
||||
- NETGEAR Nighthawk RAX50
|
||||
- 网件RAX50
|
||||
- RAX50
|
||||
|
||||
## Basic Info
|
||||
- **Type**: 路由器（网络硬件）
|
||||
- **Manufacturer**: NETGEAR（网件）
|
||||
- **Model**: Nighthawk RAX50
|
||||
- **WiFi Standard**: WiFi 6 (802.11ax)
|
||||
- **Bands**: 双频 (2.4GHz + 5GHz)
|
||||
- **Class**: AX3000
|
||||
|
||||
## Description
|
||||
网件RAX50是一款支持WiFi 6的双频路由器，型号为Nighthawk RAX50。它支持刷入第三方梅林固件以扩展功能，包括安装科学上网插件。
|
||||
|
||||
## Related
|
||||
- [[梅林固件]] — RAX50 支持的第三方固件
|
||||
- [[MerlinClash插件]] — 梅林固件上的科学上网插件
|
||||
- sources: [[网件rax50路由器刷梅林固件与科学上网插件安装教程]]
|
||||
|
||||
@@ -1,36 +1,36 @@
|
||||
---
|
||||
title: "阿里云 DNS"
|
||||
type: entity
|
||||
tags: [dns, domain, aliyun, cloud, hosting]
|
||||
last_updated: 2026-04-03
|
||||
---
|
||||
|
||||
# 阿里云 DNS
|
||||
|
||||
## Overview
|
||||
**阿里云 DNS**（Alibaba Cloud DNS）是阿里云提供的域名解析服务，用于管理域名的 DNS 记录，将域名指向服务器 IP 地址。本 Wiki 中用于管理 `ishenwei.online` 域名解析。
|
||||
|
||||
## 在本 Wiki 中的应用
|
||||
- [[通过VPS+内网反向代理实现域名访问内网穿透]]：配置 `nas.ishenwei.online` 和 `n8n.ishenwei.online` A 记录指向 RackNerd VPS IP（192.227.222.142）
|
||||
|
||||
## DNS 记录配置示例
|
||||
| 主机记录 | 记录类型 | 记录值 | TTL |
|
||||
|---------|---------|--------|-----|
|
||||
| nas | A | 192.227.222.142 | 600 |
|
||||
| n8n | A | 192.227.222.142 | 600 |
|
||||
| ubuntu1 | A | 192.227.222.142 | 600 |
|
||||
| transmission | A | 192.227.222.142 | 600 |
|
||||
| grafana | A | 192.227.222.142 | 600 |
|
||||
|
||||
## 验证命令
|
||||
```bash
|
||||
dig nas.ishenwei.online +short # 应返回 192.227.222.142
|
||||
```
|
||||
|
||||
## Related Entities
|
||||
- [[RackNerd]]：VPS 提供商，运行托管域名解析目标的公网服务
|
||||
- [[VPS]]：DNS A 记录指向的公网服务器
|
||||
|
||||
## Related Concepts
|
||||
- [[内网穿透]]：DNS 解析是内网穿透方案的第一步
|
||||
- [[反向代理]]：域名解析后由 Caddy 处理反向代理
|
||||
---
|
||||
title: "阿里云 DNS"
|
||||
type: entity
|
||||
tags: [dns, domain, aliyun, cloud, hosting]
|
||||
last_updated: 2026-04-03
|
||||
---
|
||||
|
||||
# 阿里云 DNS
|
||||
|
||||
## Overview
|
||||
**阿里云 DNS**（Alibaba Cloud DNS）是阿里云提供的域名解析服务，用于管理域名的 DNS 记录，将域名指向服务器 IP 地址。本 Wiki 中用于管理 `ishenwei.online` 域名解析。
|
||||
|
||||
## 在本 Wiki 中的应用
|
||||
- [[通过VPS+内网反向代理实现域名访问内网穿透]]：配置 `nas.ishenwei.online` 和 `n8n.ishenwei.online` A 记录指向 RackNerd VPS IP（192.227.222.142）
|
||||
|
||||
## DNS 记录配置示例
|
||||
| 主机记录 | 记录类型 | 记录值 | TTL |
|
||||
|---------|---------|--------|-----|
|
||||
| nas | A | 192.227.222.142 | 600 |
|
||||
| n8n | A | 192.227.222.142 | 600 |
|
||||
| ubuntu1 | A | 192.227.222.142 | 600 |
|
||||
| transmission | A | 192.227.222.142 | 600 |
|
||||
| grafana | A | 192.227.222.142 | 600 |
|
||||
|
||||
## 验证命令
|
||||
```bash
|
||||
dig nas.ishenwei.online +short # 应返回 192.227.222.142
|
||||
```
|
||||
|
||||
## Related Entities
|
||||
- [[RackNerd]]：VPS 提供商，运行托管域名解析目标的公网服务
|
||||
- [[VPS]]：DNS A 记录指向的公网服务器
|
||||
|
||||
## Related Concepts
|
||||
- [[内网穿透]]：DNS 解析是内网穿透方案的第一步
|
||||
- [[反向代理]]：域名解析后由 Caddy 处理反向代理
|
||||
|
||||
Reference in New Issue
Block a user