返回首页

Wiki Schema

📝 743 字

Wiki Schema

Domain

运维排障与数据管理 — 涵盖 Kubernetes 集群运维、Redis/MySQL 等数据库管理、容器化部署、生产环境最佳实践 2026-05-12 拓宽：新增"电商运营与广告投放"领域（亚马逊广告策略） 2026-05-13 拓宽：新增"无线网络与硬件优化"领域（Wi-Fi 6/7 路由器性能调优）

Conventions

  • File names: lowercase, hyphens, no spaces (e.g., pod-troubleshooting.md)
  • Every wiki page starts with YAML frontmatter (see below)
  • Use [[wikilinks]] to link between pages (minimum 2 outbound links per page)
  • When updating a page, always bump the updated date
  • Every new page must be added to index.md under the correct section
  • Every action must be appended to log.md
  • Provenance markers: On pages that synthesize 3+ sources, append [raw/articles/source-file.md](/page/raw/articles/source-file) at the end of paragraphs whose claims come from a specific source.

Concepts 子目录结构

概念页按领域分类存入 concepts/ 下的子目录，禁止平铺：

concepts/
├── kubernetes/   # K8s 集群、Pod、Service、存储、调度
├── linux/        # Linux 系统与内核、性能分析、安全加固
├── nginx/        # Nginx 反向代理配置与排障
├── database/     # MySQL + Redis 数据库
├── docker/       # Docker 容器化与镜像
├── amazon/       # 电商运营与广告
├── hardware/     # 无线网络与硬件
├── terraform/    # Terraform 基础设施即代码
└── general/      # 跨领域/综合性内容

归类优先规则：

  1. 文件名前缀优先（k8s-* → kubernetes/，linux-* → linux/）
  2. 无明确前缀按 tags 中 domain 级标签归类
  3. 跨 3+ 领域的综合性内容放 general/
  4. 新建概念页前确认已有对应子目录；如需新增子目录，先更新本文件再创建

Frontmatter

---
title: Page Title
created: YYYY-MM-DD
updated: YYYY-MM-DD
type: entity | concept | comparison | query | summary
tags: [kubernetes, troubleshooting, ...]
sources: [raw/articles/k8s-troubleshooting-article.md]
confidence: high | medium | low
contested: true
contradictions: [other-page-slug]
---

raw/ Frontmatter

---
source_url: https://...
ingested: YYYY-MM-DD
sha256: <hex digest of the body content>
---

Tag Taxonomy

核心域:

  • tcp: TCP 协议与连接排查
  • kubernetes: 核心 K8s 概念
  • scheduling: Pod 调度策略与机制
  • troubleshooting: 排障相关
  • production: 生产环境
  • deployment: 部署相关
  • networking: 网络相关
  • nfs: NFS 网络文件系统
  • storage: 存储相关
  • security: 安全/RBAC/权限
  • monitoring: 监控与日志
  • linux: Linux 系统与内核
  • performance: 性能分析与优化
  • java: Java 应用层排障
  • jvm: JVM 调优与 GC 分析
  • cni: CNI 网络插件（Flannel/Calico）
  • dns: DNS 解析/CoreDNS
  • certificate: 证书管理与 TLS
  • messaging: 消息队列/Kafka/RocketMQ

工作负载:

  • pod: Pod 相关
  • service: Service/网络
  • node: Node 相关
  • statefulset: 有状态应用
  • daemonset: DaemonSet

资源对象:

  • configmap: ConfigMap/Secret
  • pvc: 持久化存储
  • ingress: Ingress/入口
  • hpa: 自动伸缩

运维工具:

  • kubectl: kubectl 命令
  • debugging: 调试工具与方法
  • automation: 自动化脚本与工具
  • disk: 磁盘管理工具
  • filesystem: 文件系统
  • case-study: 实战案例分析
  • command: Linux 命令与工具用法
  • compression: 压缩与解压技术
  • tar: tar 归档工具
  • gzip: gzip 压缩工具
  • archive: 归档与备份策略

数据库:

  • redis: Redis 内存数据库
  • mysql: MySQL 数据库
  • database: 数据库通用
  • persistence: 数据持久化
  • backup: 备份恢复
  • data-loss: 数据丢失与容灾
  • deadlock: 死锁分析
  • lock: 锁机制详解
  • replication: 复制机制
  • sentinel: Redis Sentinel 哨兵
  • memory: 内存管理与优化

容器化:

  • docker: Docker 容器与镜像
  • container: 容器技术通用
  • image: 镜像构建/优化
  • build: 构建与 CI
  • multistage: 多阶段构建
  • golang: Go 语言编译/部署

微服务:

  • microservices: 微服务架构
  • service-discovery: 服务发现
  • nacos: Nacos 注册中心/配置中心
  • zookeeper: Zookeeper 分布式协调
  • consul: Consul 服务目录
  • architecture: 架构设计与选型

负载均衡与高可用:

  • nginx: Nginx 反向代理与配置
  • websocket: WebSocket 协议与代理
  • sse: Server-Sent Events 实时推送
  • keepalived: Keepalived 高可用管理
  • ha: 高可用架构
  • high-availability: 高可用架构（全称）
  • load-balancing: 负载均衡

电商运营与广告:

  • amazon: 亚马逊平台运营
  • advertising: 广告投放策略
  • ecommerce: 电商运营
  • ppc: PPC 广告竞价
  • brand: 品牌建设与推广

工具推荐:

  • tools: 工具推荐与评测
  • opensource: 开源项目

无线网络与硬件:

  • wifi: Wi-Fi 6/7 路由器性能调优

基础设施即代码 (IaC):

  • terraform: Terraform 基础设施即代码
  • iac: 基础设施即代码通用概念
  • devops: DevOps 工具链与平台工程

Page Thresholds

  • Create a page when an entity/concept appears in 2+ sources OR is central to one source
  • Add to existing page when a source mentions something already covered
  • DON'T create a page for passing mentions, minor details, or things outside the domain
  • Split a page when it exceeds ~200 lines — break into sub-topics with cross-links
  • Archive a page when its content is fully superseded — move to _archive/, remove from index

Entity Pages

One page per notable entity (tool, controller, resource type). Include:

  • Overview / what it is
  • Key facts and common issues
  • Relationships to other entities (wikilinks)
  • Source references

Concept Pages

One page per concept or scenario. Include:

  • Definition / explanation
  • Common failure patterns
  • Troubleshooting steps
  • Related concepts (wikilinks)

Comparison Pages

Side-by-side analyses. Include:

  • What is being compared and why
  • Dimensions of comparison (table format preferred)
  • Verdict or synthesis
  • Sources

Update Policy

When new information conflicts with existing content:

  1. Check the dates — newer sources generally supersede older ones
  2. If genuinely contradictory, note both positions with dates and sources
  3. Mark the contradiction in frontmatter: contradictions: [page-name]
  4. Flag for user review in the lint report