Auto-sync: 2026-04-17 08:35
This commit is contained in:
36
wiki/sources/how-to-get-youtube-channel-id.md
Normal file
36
wiki/sources/how-to-get-youtube-channel-id.md
Normal file
@@ -0,0 +1,36 @@
|
||||
---
|
||||
title: "How to get Youtube Channel ID"
|
||||
type: source
|
||||
tags: []
|
||||
date: 2025-03-16
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Others/How to get Youtube Channel ID.md]]
|
||||
|
||||
## Summary
|
||||
- 核心主题:通过 view-source 获取 YouTube 频道 ID
|
||||
- 问题域:YouTube 频道标识符获取
|
||||
- 方法/机制:访问频道页面源码,搜索 channel_id 参数
|
||||
- 结论/价值:获取的 channel_id 可用于 n8n 工作流集成
|
||||
|
||||
## Key Claims
|
||||
- 访问 YouTube 频道页面的 view-source 页面可以获取频道 ID
|
||||
- 频道 ID 格式为 UC 开头,可用于 RSS 订阅或 API 调用
|
||||
|
||||
## Key Quotes
|
||||
> "view-source:https://www.youtube.com/@Numberblocks" — 通过查看源码方式获取频道信息
|
||||
|
||||
## Key Concepts
|
||||
- [[Channel ID]]: YouTube 频道的唯一标识符,格式为 UC 开头
|
||||
|
||||
## Key Entities
|
||||
- [[YouTube]]: 视频分享平台
|
||||
- [[n8n]]: 开源工作流自动化工具
|
||||
|
||||
## Connections
|
||||
- [[YouTube]] ← provides → [[Channel ID]]
|
||||
- [[Channel ID]] ← used_in → [[n8n]]
|
||||
|
||||
## Contradictions
|
||||
- (暂无)
|
||||
40
wiki/sources/n8n-configure-telegram-trigger.md
Normal file
40
wiki/sources/n8n-configure-telegram-trigger.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
title: "n8n configure telegram trigger"
|
||||
type: source
|
||||
tags: [n8n, telegram, webhook]
|
||||
date: 2026-04-17
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Agent/n8n configure telegram trigger.md]]
|
||||
|
||||
## Summary
|
||||
- 核心主题:n8n Telegram Trigger 配置问题排查与解决
|
||||
- 问题域:工作流自动化、Webhook 配置
|
||||
- 方法/机制:通过设置 WEBHOOK_URL 环境变量为 HTTPS URL 解决 Telegram Webhook 必须使用 HTTPS 的要求
|
||||
- 结论/价值:n8n 部署时需确保Webhook URL 可通过 HTTPS 访问,否则 Telegram Bot API 无法注册 Webhook
|
||||
|
||||
## Key Claims
|
||||
- Telegram Bot API 要求 Webhook URL 必须是 HTTPS 格式
|
||||
- n8n 通过 WEBHOOK_URL 环境变量指定生成的 Webhook URL 协议
|
||||
- 在 Docker 环境中配置 WEBHOOK_URL=https://your-domain.com/ 可解决此问题
|
||||
|
||||
## Key Quotes
|
||||
> "Telegram Trigger: Bad Request: bad webhook: An HTTPS URL must be provided for webhook" — n8n Telegram Trigger 配置错误信息
|
||||
|
||||
## Key Concepts
|
||||
- [[Webhook]]: Webhook 是一种 HTTP 回调机制,允许外部服务通过 HTTP 请求触发本地服务
|
||||
- [[Telegram Bot API]]: Telegram 提供的机器人 API,支持通过 Webhook 接收消息
|
||||
- [[环境变量]]: 在操作系统级别配置应用行为的变量,n8n 通过 WEBHOOK_URL 指定公开访问的 Webhook 地址
|
||||
|
||||
## Key Entities
|
||||
- [[n8n]]: 开源工作流自动化工具
|
||||
- [[Docker Desktop]]: Docker 桌面版,用于运行 n8n 容器
|
||||
|
||||
## Connections
|
||||
- [[n8n]] ← uses ← [[Webhook]]
|
||||
- [[Telegram Bot API]] ← requires ← [[Webhook#HTTPS]]
|
||||
- [[n8n-docker-install-update]] ← related_to ← [[n8n-configure-telegram-trigger]]
|
||||
|
||||
## Contradictions
|
||||
- (暂无)
|
||||
103
wiki/sources/n8n-docker-install-update.md
Normal file
103
wiki/sources/n8n-docker-install-update.md
Normal file
@@ -0,0 +1,103 @@
|
||||
---
|
||||
title: "n8n Docker install & update"
|
||||
type: source
|
||||
tags: [docker, n8n, workflow]
|
||||
date: 2026-04-17
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Agent/n8n docker install & update.md]]
|
||||
|
||||
## Summary
|
||||
- 核心主题:n8n 工作流自动化工具的 Docker 部署与网络代理配置
|
||||
- 问题域:Docker 容器化部署、网络代理配置、宿主机代理访问
|
||||
- 方法/机制:Docker Compose 编排、Dockerfile 自定义镜像、SOCKS5 代理配置
|
||||
- 结论/价值:实现 n8n 容器内科学上网,支持工作流自动化执行
|
||||
|
||||
## Key Claims
|
||||
- n8n 可通过 Docker Compose 快速部署,配置数据卷持久化
|
||||
- 容器内网络流量可通过 SOCKS5 代理访问外网
|
||||
- 需将宿主机代理监听地址改为 `0.0.0.0` 使容器可访问
|
||||
- Docker 网桥 IP(Gateway)可通过 `docker network inspect` 获取
|
||||
|
||||
## Key Quotes
|
||||
> "注意:`172.21.0.1` 需替换为以下命令输出的网桥 IP(Gateway)"
|
||||
|
||||
> "V2Ray/Tuic 配置中 **本地监听地址改为 `0.0.0.0`**,端口假设为 `10808`"
|
||||
|
||||
## Key Concepts
|
||||
- [[Docker]]:容器化平台
|
||||
- [[Docker-Compose]]:Docker 编排工具,定义多容器应用
|
||||
- [[Dockerfile]]:容器镜像构建文件
|
||||
- [[SOCKS5代理]]:支持 TCP/UDP 的网络代理协议
|
||||
- [[Docker-网桥]]:Docker 虚拟网桥,容器与宿主机通信的桥梁
|
||||
|
||||
## Key Entities
|
||||
- [[n8n]]:开源工作流自动化工具
|
||||
|
||||
## Connections
|
||||
- [[n8n]] ← runs_in ← [[Docker]]
|
||||
- [[Docker]] ← uses ← [[Docker-Compose]]
|
||||
- [[Docker]] ← built_from ← [[Dockerfile]]
|
||||
- [[n8n]] ← accesses_network_via ← [[SOCKS5代理]]
|
||||
|
||||
## Contradictions
|
||||
- (暂无)
|
||||
|
||||
---
|
||||
|
||||
## Docker Compose 配置
|
||||
|
||||
```yaml
|
||||
version: '3.8'
|
||||
services:
|
||||
n8n:
|
||||
build: .
|
||||
image: docker.n8n.io/n8nio/n8n
|
||||
container_name: n8n
|
||||
ports:
|
||||
- "5678:5678"
|
||||
volumes:
|
||||
- n8n_data:/home/node/.n8n
|
||||
environment:
|
||||
- N8N_PROTOCOL=https
|
||||
- N8N_HOST=n8n.ishenwei.online
|
||||
- WEBHOOK_URL=https://n8n.ishenwei.online/
|
||||
- N8N_TRUST_PROXY=true
|
||||
- N8N_SECURE_COOKIE=true
|
||||
- N8N_PROXY_HOPS=1
|
||||
- ALL_PROXY=socks5://172.21.0.1:10808
|
||||
restart: unless-stopped
|
||||
|
||||
volumes:
|
||||
n8n_data:
|
||||
|
||||
networks:
|
||||
n8n_default:
|
||||
external: true
|
||||
```
|
||||
|
||||
## Dockerfile 配置
|
||||
|
||||
```dockerfile
|
||||
FROM n8nio/n8n:latest
|
||||
USER root
|
||||
RUN apk update && apk add --no-cache curl wget
|
||||
USER node
|
||||
```
|
||||
|
||||
## 更新步骤
|
||||
|
||||
```bash
|
||||
cd /path/to/your/compose/file/directory
|
||||
docker compose pull
|
||||
docker compose down
|
||||
docker compose up -d
|
||||
```
|
||||
|
||||
## 容器内测试代理
|
||||
|
||||
```bash
|
||||
docker exec -it n8n /bin/sh
|
||||
curl --socks5 172.18.0.1:10808 https://ifconfig.me
|
||||
```
|
||||
54
wiki/sources/万字讲透OpenClaw-Workspace深度解析-2026-03-21.md
Normal file
54
wiki/sources/万字讲透OpenClaw-Workspace深度解析-2026-03-21.md
Normal file
@@ -0,0 +1,54 @@
|
||||
---
|
||||
title: "万字讲透OpenClaw🦞从"能用"到"真好用"的分水岭:Workspace 深度解析"
|
||||
type: source
|
||||
tags: [OpenClaw, Agent, Workspace, AGENTS.md, SOUL.md]
|
||||
date: 2026-03-21
|
||||
---
|
||||
|
||||
## Source File
|
||||
- [[raw/Agent/万字讲透OpenClaw-Workspace深度解析-2026-03-21.md]]
|
||||
|
||||
## Summary
|
||||
- 核心主题:OpenClaw workspace 文件体系深度解析
|
||||
- 问题域:AI Agent 个性化配置与长期记忆
|
||||
- 方法/机制:workspace 目录结构、各文件职责(AGENTS.md、SOUL.md、USER.md、IDENTITY.md、TOOLS.md、BOOTSTRAP.md、memory/)
|
||||
- 结论/价值:workspace 是让 Agent 从"能工作"变成"好用"的关键,通过固化用户偏好、Agent 性格和长期记忆实现个性化
|
||||
|
||||
## Key Claims
|
||||
- workspace 是 OpenClaw 中决定 Agent 如何工作的核心文件体系
|
||||
- AGENTS.md 是岗位说明书,SOUL.md 是性格档案,两者分工明确不应混写
|
||||
- USER.md 作用是固化用户偏好,减少重复交代
|
||||
- TOOLS.md 规范工具使用,减少误操作
|
||||
- BOOTSTRAP.md 是一次性引导,完成初始化后应删除
|
||||
- memory/ 目录是 Agent 的长期记忆机制
|
||||
|
||||
## Key Quotes
|
||||
> "workspace 是 Agent 的'工作台'(决定怎么工作),agentDir 是 openclaw.json 里的一个配置字段(指向存放运行状态的目录),sessions 是'工作日志'(记对话历史)。三者职责不同,不要混为一谈。"
|
||||
> "一个没有 SOUL.md 的 Agent,每次对话都像第一次见面——它不记得自己是谁,说话没有固定风格,遇到同样的问题今天这么说、明天那么说。"
|
||||
> "300-500 字的 AGENTS.md,比 2000 字的更有效。"
|
||||
> "SOUL.md 是新来的助理的个人简历,USER.md 是 HR 给这位助理写的'关于你的上司,你需要提前知道的事'。"
|
||||
|
||||
## Key Concepts
|
||||
- [[Workspace]]:OpenClaw 中 Agent 的工作台目录,包含行为规则、性格设定、用户偏好等配置文件
|
||||
- [[AGENTS.md]]:Agent 的行为规则与多 Agent 协调文件,相当于岗位说明书
|
||||
- [[SOUL.md]]:Agent 的叙事性格设定文件,相当于人物小传
|
||||
- [[USER.md]]:用户画像与偏好固化文件
|
||||
- [[IDENTITY.md]]:Agent 的结构化身份元数据
|
||||
- [[TOOLS.md]]:工具权限声明与使用规范
|
||||
- [[BOOTSTRAP.md]]:首次启动引导文件,一次性使用后应删除
|
||||
- [[Memory 目录]]:Agent 的长期记忆机制,按日期滚动存储
|
||||
|
||||
## Key Entities
|
||||
- [[OpenClaw]]:AI Agent 管理工具,支持 workspace 个性化配置
|
||||
- [[DracoVibeCoding]]:本文作者,公众号「Draco正在VibeCoding」
|
||||
|
||||
## Connections
|
||||
- [[OpenClaw]] ← contains ← [[Workspace]]
|
||||
- [[Workspace]] ← manages ← [[AGENTS.md]]
|
||||
- [[Workspace]] ← manages ← [[SOUL.md]]
|
||||
- [[Workspace]] ← manages ← [[USER.md]]
|
||||
- [[SOUL.md]] ← complements ← [[IDENTITY.md]]
|
||||
- [[BOOTSTRAP.md]] ← initializes ← [[IDENTITY.md]], [[USER.md]], [[SOUL.md]]
|
||||
|
||||
## Contradictions
|
||||
- (暂无)
|
||||
Reference in New Issue
Block a user