ihawo - L
type: channel
link: https://www.ihawo.com/author/1/
description: L
items: centos_stream_9部署SFTPGo+ELK日志采集(统一版)
items: dify部署手册
items: 公文api部署手册
items: AnythingLLM部署手册
items: SearXNG部署手册
items: LiteLLM部署手册
items: vLLM部署手册
items: 为AWS Lightsail vps开启root登陆权限，也适用于EC2等
items: [搬运]OpenSSL 自签 CA 及 SSL 证书
items: GitKraken 6.5.1

centos_stream_9部署SFTPGo+ELK日志采集(统一版)
type: item
date: 2026-07-03T17:21:18+08:00
description: 业务链说明本文档将SFTPGo部署手册与ELK日志采集手册合并为一个项目目录、一个docker-compose.yml，四个服务（sftpgo / elasticsearch / kibana / filebeat）统一编排、统一网络，形成完整业务链：SFTPGo产生日志 → 写入宿主机共享目录 → Filebeat采集 → 写入Elasticsearch → Kibana可视化查看sftpgo与filebeat通过同一个宿主机目录（./sftpgo/logs）实现日志传递，不依赖网络；filebeat与elasticsearch之间通过compose内部网络elastic-net用容器名互相访问，不再依赖外部域名，部署更内聚、迁移更方便。一、环境准备1.安装Docker（已安装可跳过）# 卸载旧版本(按需) yum remove docker docker-client docker-client-latest docker-common \ docker-latest docker-latest-logrotate docker-logrotate docker-engine # 配置阿里云docker-ce源 yum install -y yum-utils yum-config-manager --add-repo https://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo # 安装docker-ce yum install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin # 启动并设置开机自启 systemctl start docker && systemctl enable docker二、创建项目目录结构所有配置、数据、日志统一收拢在一个项目目录下，方便整体迁移与备份：mkdir -p /home/sftpgo-elk/{sftpgo/home,sftpgo/data,sftpgo/logs,filebeat/config,filebeat/data,filebeat/logs,elasticsearch/es_data,kibana/kibana_data} cd /home/sftpgo-elk目录规划：/home/sftpgo-elk/ ├── docker-compose.yml # 唯一的compose文件，四个服务统一编排 ├── sftpgo/ │ ├── home/ # 挂载至容器 /var/lib/sftpgo（配置/元数据） │ ├── data/ # 挂载至容器 /srv/sftpgo（文件存储） │ └── logs/ # 挂载至容器 /var/log/sftpgo，同时被filebeat只读挂载采集 ├── filebeat/ │ ├── config/filebeat.yml │ ├── data/ # filebeat注册表(registry)，记录采集进度，需持久化 │ └── logs/ # filebeat自身运行日志 ├── elasticsearch/ │ └── es_data/ └── kibana/ └── kibana_data/赋予数据目录读写权限chown -R 1000:1000 /home/sftpgo-elk/sftpgo/home chown -R 1000:1000 /home/sftpgo-elk/sftpgo/data chown -R 1000:1000 /home/sftpgo-elk/sftpgo/logs chown -R 1000:1000 /home/sftpgo-elk/elasticsearch/es_data chown -R 1000:1000 /home/sftpgo-elk/kibana/kibana_data1000为SFTPGo、Elasticsearch、Kibana官方镜像默认使用的容器内运行用户UID/GID，统一赋权避免EACCES权限报错。三、用cat生成统一docker-compose.yml⚠️ 以下配置以你实际生产环境正在使用的sftpgo配置为准（日志输出、限流轮转参数均保留），仅将挂载路径统一收拢到项目目录下，并把filebeat、elasticsearch、kibana并入同一份compose、同一网络。cat <<'EOF' > docker-compose.yml version: "3.8" services: # ------------------------- 业务服务：SFTPGo -------…

dify部署手册
type: item
date: 2026-07-03T11:36:37+08:00
description: 准备工作操作系统CentOS Stream 9 (x86)cat /etc/os-release NAME="CentOS Stream" VERSION="9" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="9" PLATFORM_ID="platform:el9" PRETTY_NAME="CentOS Stream 9" ANSI_COLOR="0;31" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:centos:centos:9" HOME_URL="https://centos.org/" BUG_REPORT_URL="https://issues.redhat.com/" REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 9" REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"已安装docker composeDocker version 29.5.3, build d1c06ef Docker Compose version v5.1.4一、部署difygit pull https://github.com/langgenius/dify.git创建.env文件cd dify/docker && cp .env.example .envdify的llm节点有内部流程60s超时限制，导致没法下载智能体文件，在.env中修改配置sed -i 's/TEXT_GENERATION_TIMEOUT_MS=60000/TEXT_GENERATION_TIMEOUT_MS=300000/' .env部署容器集群docker compose up -d测试访问webcurl http://localhost二、公文api开始构建部署FastAPI程序docker compose up -d五、测试chat用以下指令测试业务curl -s -o test.docx -w "HTTP状态码: %{http_code}\n文件大小: %{size_download} bytes\n" -X POST http://localhost:8765/generate_from_llm_text -H "Content-Type: application/json" -d '{"doc_redheader":"测试机关文件","doc_number":"测发〔2026〕1号","title_lines":["关于测试公文格式化服务的通知"],"recipient":"各测试单位","body":[{"type":"intro","text":"为验证公文格式化API服务是否正常，现通知如下："},{"type":"heading1","text":"一、测试内容"},{"type":"para","text":"本次测试涵盖红头、标题、正文、附件及版记等全部要素。"},{"type":"heading2","text":"（一）格式校验"},{"type":"para","text":"请检查生成文档的字体、字号、行距及页边距是否符合GB/T 9704-2012标准。"}],"attachments":["测试附件清单"],"signing_org_lines":["测试机关"],"date":"2026年7月2日","cc_orgs":"抄送测试部门","print_org":"测试机关办公室","print_date":"2026年7月2日"}' && echo "✅ 文件已保存为 test.docx，请用Word或WPS打开验证排版" || echo "❌ 请求失败"

公文api部署手册
type: item
date: 2026-07-03T11:36:14+08:00
description: 准备工作操作系统CentOS Stream 9 (x86)cat /etc/os-release NAME="CentOS Stream" VERSION="9" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="9" PLATFORM_ID="platform:el9" PRETTY_NAME="CentOS Stream 9" ANSI_COLOR="0;31" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:centos:centos:9" HOME_URL="https://centos.org/" BUG_REPORT_URL="https://issues.redhat.com/" REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 9" REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"已安装docker composeDocker version 29.5.3, build d1c06ef Docker Compose version v5.1.4一、目录结构gongwen/├── docker-compose.yml├── Dockerfile└──main.py二、创建配置文件创建目录mkdir -p gongwen/ && cd gongwen部署文件cat > docker-compose.yml << 'EOF' services: gongwen-api: build: . container_name: gongwen-api restart: unless-stopped ports: - "8765:8765" EOF镜像构件文件cat > Dockerfile << 'EOF' FROM python:3.11-slim # 安装 Node.js（用于 docx.js 生成 Word 文件） RUN apt-get update && apt-get install -y curl && \ curl -fsSL https://deb.nodesource.com/setup_20.x | bash - && \ apt-get install -y nodejs && \ apt-get clean && rm -rf /var/lib/apt/lists/* WORKDIR /app # 安装 docx npm 包到 /app/node_modules（本地安装，避免临时目录找不到模块） RUN npm install docx # 安装 Python 依赖 RUN pip install --no-cache-dir fastapi uvicorn pydantic python-docx COPY main.py . EXPOSE 8765 CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "8765"] EOF部署主程序源码cat > main.py<< 'EOF' """ 公文格式化 API 服务（最终版） 接口结构与 v11 完全一致，Word 格式按 GB/T 9704-2012 重写 XML 元素严格按 OOXML CT_PPr schema 顺序插入： pBdr(8) → tabs(10) → spacing(21) → ind(22) → jc(26) """ from fastapi import FastAPI, HTTPException, Body from fastapi.responses import StreamingResponse from pydantic import BaseModel from typing import Optional, List, Literal, Any import io, json from urllib.parse import quote from lxml import etree from docx import Document from docx.shared import Pt, Cm, RGBColor from docx.enum.text import WD_ALIGN_PARAGRAPH, WD_LINE_SPACING from docx.oxml.ns import qn from docx.oxml import OxmlElement app = FastAPI(title="公文格式化服务") # ── 数据模型（与 v11 完全一致）─────────…

AnythingLLM部署手册
type: item
date: 2026-07-03T11:35:40+08:00
description: 准备工作操作系统CentOS Stream 9 (x86)cat /etc/os-release NAME="CentOS Stream" VERSION="9" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="9" PLATFORM_ID="platform:el9" PRETTY_NAME="CentOS Stream 9" ANSI_COLOR="0;31" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:centos:centos:9" HOME_URL="https://centos.org/" BUG_REPORT_URL="https://issues.redhat.com/" REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 9" REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"已安装docker composeDocker version 29.5.3, build d1c06ef Docker Compose version v5.1.4AnythingLLM tag版本号为1.14.1配置好vLLM，并且可以curl访问chat和embedding模型接口配置好SearXNG，并且可以curl访问json接口一、目录结构anythingllm/├── docker-compose.yml└── storage/ (留空，需要777权限)二、创建配置文件mkdir -p -m 777 anythingllm/storage/ && cd anythingllmcat > docker-compose.yml << 'EOF' services: anythingllm: image: swr.cn-north-4.myhuaweicloud.com/ddn-k8s/docker.io/mintplexlabs/anythingllm:1.14.1 container_name: anythingllm ports: - "3001:3001" cap_add: - SYS_ADMIN environment: - TZ=Asia/Shanghai - STORAGE_DIR=/app/server/storage - JWT_SECRET=your_super_secret_key_here_1234567890 volumes: - /etc/localtime:/etc/localtime:ro - ./storage:/app/server/storage restart: unless-stopped EOF三、启动AnythingLLMdocker compose up -d正常启动后可以访问http://localhost:3001来访问后台管理web四、配置web1、配置模型供应商首次访问会出现欢迎界面流程LLM偏好选择LiteLLM字段名值说明Base URLhttp://118.193.117.134:3000/v1配置LiteLLM的网关地址Chat Model Selectionqwen3-public配置好url和api key后，会连接到网关查询可用模型列表，自行选择。如果没有出现模型列表，说明LiteLLM配置有问题，或者网络有问题。Model context window4096模型最大上下文长度，不要太大，超过vLLM的配置阈值可能会报错API Keysk-mHz0miMx_QyR6xAhxVmSgw根据之前的配置填写key2、配置用户账户将有多少用户使用此实例？根据实际使用来选择，我这里是选择只有我你想要设置密码吗？选择否3、测试chat正常配置到目前可以正常对话了，可以在对话中进行QA4、配置embedding模型进入设置--->人工智能提供商--->嵌入器(Embedding)--->选择LiteLLM字段名值说明Base URLhttp://118.193.117.134:3000/v1同上网关地址Embedding Model Selectionembedding-public配置好url和api key后，会连接到网关查询可用模型列表，自行选择。如果没有出现模型列表，说明LiteLLM配置有问题，或者网络有问题。Max embedding chunk length4096默认值API Keysk-mHz0miMx_QyR6xAhxVmSgw根据之前的配置填写key保存更改5、配置联网搜索RAG进入设置--->代理技能--->实时网络搜索和浏览--->打开开关实时网络搜索和浏览--->选择SearX…

SearXNG部署手册
type: item
date: 2026-07-03T11:34:00+08:00
description: 准备工作操作系统CentOS Stream 9 (x86)cat /etc/os-release NAME="CentOS Stream" VERSION="9" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="9" PLATFORM_ID="platform:el9" PRETTY_NAME="CentOS Stream 9" ANSI_COLOR="0;31" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:centos:centos:9" HOME_URL="https://centos.org/" BUG_REPORT_URL="https://issues.redhat.com/" REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 9" REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"已安装docker composeDocker version 29.5.3, build d1c06ef Docker Compose version v5.1.4SearXNG tag版本号为2026.6.17-4dfdc822c一、目录结构SearXNG/├── docker-compose.yml└── searxng-config/ └── settings.yml二、创建配置文件mkdir -p SearXNG/searxng-config/ && cd SearXNGcat > docker-compose.yml << 'EOF' services: searxng: image: swr.cn-north-4.myhuaweicloud.com/ddn-k8s/docker.io/searxng/searxng:2026.6.17-4dfdc822c container_name: searxng ports: - "18080:8080" # 将宿主机的18080端口映射到容器的8080端口 volumes: - ./searxng-config:/etc/searxng # 持久化配置文件，方便后续自定义设置 environment: - BASE_URL=http://localhost:18080 # 设置基础URL，确保API调用正确 - INSTANCE_NAME=my-searxng # 实例名称，用于标识你的搜索服务 - SEARXNG_SECRET=your-secret-key-here # 强烈建议替换为你的随机密钥，增强安全性 restart: always # 容器异常退出后自动重启 EOFcat > searxng-config/settings.yml << 'EOF' use_default_settings: true server: secret_key: "5dibmPP2UapoQ0NsvmPHZcabgr1QLgCS" image_proxy: true search: formats: - html - json default_engines: - baidu engines: # 1. 国内可用及保留的搜索引擎 (已启用) - name: baidu engine: baidu shortcut: bd disabled: false - name: sogou engine: sogou shortcut: sogou timeout: 5.0 disabled: false - name: 360search engine: 360search shortcut: 360so disabled: false - name: quark engine: quark shortcut: qk disabled: false - name: bing engine: bing shortcut: bi disabled: false - name: bilibili engine: bilibili shortcut: bil disabled: false - name: sogou_video engine: sogou_video shortcut: sogouv disabled: false - name: sogou_wechat engine: sogou_wechat shortcut: sogouw disabled: false # 2. 你要求禁用的搜索引擎 (已禁用) - name: brave engine: brave shortcut: br disabled: true - …

LiteLLM部署手册
type: item
date: 2026-07-03T11:24:00+08:00
description: 准备工作系统为openEuler 22.03 ARM架构 (x86也可以用，但是要自行修改镜像地址)cat /etc/os-release NAME="openEuler" VERSION="22.03 (LTS-SP4)" ID="openEuler" VERSION_ID="22.03" PRETTY_NAME="openEuler 22.03 (LTS-SP4)" ANSI_COLOR="0;31"已安装docker composeDocker version 29.5.3, build d1c06ef Docker Compose version v5.1.4LiteLLM版本号为v1.89.1vLLM已搭建，并且可以用curl请求，测试请求格式范例如下：chatcurl http://127.0.0.1:8000/v1/chat/completions -H "Content-Type: application/json" -d '{"model":"qwen3","messages":[{"role":"user","content":"你好，请简单介绍下自己"}],"temperature":0.7,"max_tokens":1024}'embeddingcurl http://127.0.0.1:9010/v1/embeddings -H "Content-Type: application/json" -d '{"model":"/model","input":"测试文本向量化"}'rerankcurl http://127.0.0.1:9011/v1/score -H "Content-Type: application/json" -d '{"model":"/model","pairs":[["人工智能是什么","人工智能是模拟人类智能的技术"],["人工智能是什么","今天下雨了"]]}'一、目录结构litellm/├── .env├── docker-compose.yml└── prometheus.yml二、创建配置文件mkdir litellm && cd litellm.env中的LITELLM_MASTER_KEY为默认登入密码，SEARXNG_API_BASE为可选配置cat > .env << 'EOF' LITELLM_MASTER_KEY="sk-c0oE4EgitT4DmXyRj4Av" SEARXNG_API_BASE="http://192.168.105.143:18080" EOFcat > docker-compose.yml << 'EOF' services: litellm: build: context: . args: target: runtime image: swr.cn-north-4.myhuaweicloud.com/ddn-k8s/docker.io/docker.litellm.ai/berriai/litellm:main-stable-linuxarm64 ######################################### ## Uncomment these lines to start proxy with a config.yaml file ## # volumes: # - ./config.yaml:/app/config.yaml # command: # - "--config=/app/config.yaml" ############################################## ports: - "3000:4000" # Map the container port to the host, change the host port if necessary environment: DATABASE_URL: "postgresql://llmproxy:dbpassword9090@db:5432/litellm" # Optional: route read-only queries (find_*, count, group_by, query_raw/_first) # to a separate reader endpoint, e.g. an Aurora reader. Leave unset for # single-DB deployments. With IAM_TOKEN_DB_AUTH enabled, the reader URL # is auto-refreshed alongside the writer. # DATABASE_URL_READ…

vLLM部署手册
type: item
date: 2026-07-03T11:22:00+08:00
description: 准备工作显卡为8卡910B，aarch64架构鲲鹏cpu[root@localhost ~]# lscpu 架构： aarch64 CPU 运行模式： 64-bit 字节序： Little Endian CPU: 128 在线 CPU 列表： 0-127 厂商 ID： HiSilicon BIOS Vendor ID: HiSilicon 型号名称： Kunpeng-920 BIOS Model name: HUAWEI Kunpeng 920 7260 型号： 0 每个核的线程数： 1 每个座的核数： 64 座： 2 步进： 0x1 BogoMIPS： 200.00 标记： fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma dcpop asimddp asimdfh m ssbs Caches (sum of all): L1d: 8 MiB (128 instances) L1i: 8 MiB (128 instances) L2: 64 MiB (128 instances) L3: 128 MiB (4 instances) NUMA: NUMA 节点： 4 NUMA 节点0 CPU： 0-31 NUMA 节点1 CPU： 32-63 NUMA 节点2 CPU： 64-95 NUMA 节点3 CPU： 96-127 Vulnerabilities: Gather data sampling: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Spectre v1: Mitigation; __user pointer sanitization Spectre v2: Not affected Srbds: Not affected Tsx async abort: Not affected[root@localhost ~]# npu-smi info +------------------------------------------------------------------------------------------------+ | npu-smi 25.5.1 Version: 25.5.1 | +---------------------------+---------------+----------------------------------------------------+ | NPU Name | Health | Power(W) Temp(C) Hugepages-Usage(page)| | Chip | Bus-Id | AICore(%) Memory-Usage(MB) HBM-Usage(MB) | +===========================+===============+====================================================+ | 3 910B4-1 | OK | 76.5 41 0 / 0 | | 0 | 0000:2F:00.0 | 0 0 / 0 3202 / 65536 | +===========================+===============+====================================================+ | 4 910B4-1 | OK | 77.4 41 0 / 0 | | 0 | 0000:2C:00.0 | 0 0 / 0 3202 / 65536 | +===========================+===============+====================================================+ | 5 910B4-1 | OK | 84.4 43 0 / 0 | | 0 | 0000:2B:00.0 | 0 0 / 0 3202 / 65536 | +===========…

为AWS Lightsail vps开启root登陆权限，也适用于EC2等
type: item
date: 2024-03-12T16:24:00+08:00
description: 将下面代码中的第一句中的muyijiang改为自己将要设置的密码。否则默认root密码为muyijiang。创建实例的时候，点击添加启动脚本，将下列代码复制进去(注意更改root密码)。#!/bin/bash echo root:muyijiang |sudo chpasswd root sudo sed -i 's/^.*PermitRootLogin.*/PermitRootLogin yes/g' /etc/ssh/sshd_config; sudo sed -i 's/^.*PasswordAuthentication.*/PasswordAuthentication yes/g' /etc/ssh/sshd_config; sudo reboot对于EC2，GCE等机器也可以使用.不能添加代码的机器，可以登录进ssh，再执行上面的代码。也可以开启root登陆。以上代码在Debian/Ubuntu/Centos上通过测试。其他发行版自行测试。原文来源：萌咖 木易酱

[搬运]OpenSSL 自签 CA 及 SSL 证书
type: item
date: 2022-01-22T00:47:00+08:00
description: 来源：樱花庄的白猫工具：OpenSSL 1.1.0g平台：Ubuntu 18.04准备工作检查 OpenSSL 配置文件：nano /etc/ssl/openssl.cnf找到 CA 配置部分，确认以下配置：[ CA_default ] dir = ./demoCA # Where everything is kept certs = $dir/certs # Where the issued certs are kept crl_dir = $dir/crl # Where the issued crl are kept database = $dir/index.txt # database index file. new_certs_dir = $dir/newcerts # default place for new certs. certificate = $dir/cacert.pem # The CA certificate serial = $dir/serial # The current serial number crlnumber = $dir/crlnumber # the current crl number crl = $dir/crl.pem # The current CRL private_key = $dir/private/cakey.pem# The private key RANDFILE = $dir/private/.rand # private random number file初始化目录：mkdir -p ./demoCA/{private,newcerts} && touch ./demoCA/index.txt && touch ./demoCA/serial && echo 01 > ./demoCA/serial签发 CA 证书创建 CA 配置文件：nano root.conf写入以下配置：[ req ] default_bits = 2048 default_keyfile = r.pem default_md = sha256 string_mask = nombstr distinguished_name = req_distinguished_name req_extensions = req_ext x509_extensions = x509_ext [ req_distinguished_name ] countryName = Country Name (2 letter code) countryName_default = CN stateOrProvinceName = State or Province Name (full name) stateOrProvinceName_default = Shanghai localityName = Locality Name (eg, city) localityName_default = Shanghai organizationName = Organization Name (eg, company) organizationName_default = Mashiro LLC commonName = Common Name (e.g. server FQDN or YOUR name) commonName_max = 64 commonName_default = Mashiro Internet Fake Authority CA [ x509_ext ] subjectKeyIdentifier = hash authorityKeyIdentifier = keyid,issuer basicConstraints = CA:TRUE keyUsage = digitalSignature, keyEncipherment, keyCertSign, cRLSign [ req_ext ] subjectKeyIdentifier = hash basicConstraints = CA:TRUE keyUsage = digitalSignature, keyEncipherment, keyCertSign, cRLSign参数含义：字段值countryName国家名缩写stateOrProvinceName州或省localityName地点，如城市organizationName组织名commonName商标（证书上显示的 CA 名称）*xxx_default设置该字段默认值，这样等一下生成证书时就不用手动填写信息，直接回车使用默认值就行了。生成 CA 根密钥：opens…

GitKraken 6.5.1
type: item
date: 2020-09-07T14:08:00+08:00
description: GitKraken 更新后免费版本无法打开私有库，可以退回6.5.1（最新可以私有库的版本）进行使用。安装完之后需要禁止自动更新，可通过添加下列host来禁止自动更新：127.0.0.1 release.gitkraken.com api.gitkraken.com防止官方封禁旧版本下载地址，这里进行备份。官方地址win-x86:release.axocdn.com/win32/GitKrakenSetup-6.5.1.exerelease.gitkraken.com/win32/GitKrakenSetup-6.5.1.exewin-x64:release.axocdn.com/win64/GitKrakenSetup-6.5.1.exerelease.gitkraken.com/win64/GitKrakenSetup-6.5.1.exelinux-deb:release.axocdn.com/linux/GitKraken-v6.5.1.debrelease.gitkraken.com/linux/GitKraken-v6.5.1.deblinux-rpm:release.axocdn.com/linux/GitKraken-v6.5.1.rpmrelease.gitkraken.com/linux/GitKraken-v6.5.1.rpmlinux-tar.gz:release.axocdn.com/linux/GitKraken-v6.5.1.tar.gzrelease.gitkraken.com/linux/GitKraken-v6.5.1.tar.gzmac:release.axocdn.com/darwin/GitKraken-v6.5.1.ziprelease.gitkraken.com/darwin/GitKraken-v6.5.1.zip本站备份win-x86: GitKrakenSetup-6.5.1-x86.exewin-x64: GitKrakenSetup-6.5.1-x64.exelinux-rpm:GitKraken-v6.5.1.rpmlinux-deb:GitKraken-v6.5.1.deblinux-tar.gz:GitKraken-v6.5.1.tar.gzmac:GitKraken-v6.5.1.zipGitKraken学习补丁（支持 7.7.0 ~ 8.2.0）：gitee.com/lepton-lee/GitCracken如无法使用请使用上方旧版GitKraken。