Skip to content

Instantly share code, notes, and snippets.

View cmzz's full-sized avatar
🐱
Out sick

cmzz

🐱
Out sick
  • 11:40 (UTC +08:00)
View GitHub Profile
@cmzz
cmzz / README.md
Last active October 19, 2026 16:23
Dify multilingual support triage: credential-free workflow, EN/ZH/RU setup and observed test limits

Multilingual support triage in Dify

A small, inspectable chatflow for human support operators: paste a redacted message, receive its category, stated facts, unknowns and a reply draft in the sender’s language. The graph is User Input → LLM → Answer. It has no email, payment or account tools.

Maintained by Joe Wu / 1ZheAI. The workflow and guide were prepared with AI assistance and tested on synthetic examples. This is an independent template, not an official Dify product or endorsement.

Setup

  1. Download multilingual-support-triage.yml and import it into Dify Studio. Install the official OpenAI-API-compatible provider dependency when prompted (tested version 0.0.68; DSL version 0.7.0).
  2. Configure your own model credential under Integrations → Model Provider. No API key is included. For the tested gateway, the API base URL is https://1zheai.com/v1; choose a currently available model from your account. Other compatible providers can be selected in the LLM node.
@cmzz
cmzz / README-en.md
Last active October 19, 2026 00:12
OpenAI Node SDK baseURL path probe: local HTTP fixture, no API key required | 1折AI

Debugging OpenAI Node SDK baseURL paths without an API key

A 404 can come from the URL path your SDK constructs. If you set baseURL to the full /v1/chat/completions endpoint, the SDK may append /chat/completions again.

The accompanying probe.mjs starts a local HTTP fixture on 127.0.0.1, captures five request paths, prints the results, and exits. It does not call a remote model or incur model charges. The API key in the script is a local placeholder, not a credential.

Run the example

Save probe.mjs from this Gist into a new directory, then run:

# 你可以从该 URL 下载这个配置文件: http://surge.run/config-example/ios.conf
# 用编辑器编辑后,再通过 iTunes, URL, AirDrop 或者 iCloud Drive 复制回 iOS 设备
# Version 2.0
[General]
# 日志等级: warning, notify, info, verbose (默认值: notify)
loglevel = notify
# 跳过某个域名或者 IP 段,这些目标主机将不会由 Surge Proxy 处理。(在 macOS
# 版本中,如果启用了 Set as System Proxy, 那么这些值会被写入到系统网络代理
# 设置中.)
@cmzz
cmzz / readme.txt
Created October 17, 2015 15:54 — forked from fqrouter/readme.txt
shadowsocks 公共代理的必要设置
good, 你已经有了一个自己的shadowsocks代理了,现在想要把这个代理公布出去给所有人分享。
但是没有两个小时,代理就没法使用了,为什么?因为你需要额外注意以下事项(以下步骤需要比较高的linux技能)
本文只关注于确保shadowsocks服务还“活着”,如果你希望让其跑得更快,请参考
https://github.com/clowwindy/shadowsocks/wiki/Optimizing-Shadowsocks
1、 shadowsocks的timeout设置
超时时间越长,连接被保持得也就越长,导致并发的tcp的连接数也就越多。对于公共代理,这个值应该调整得小一些。推荐60秒。
2、 检查操作系统的各种限制
对于openvz的vps,特别需要检查一下