lingtai-update-mainland

Configure mirrors and dependency indexes for LingTai installs from mainland China.

692|60|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-update-mainland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lingtai-update-mainland
Source: https://github.com/Lingtai-AI/lingtai/tree/main/tui/internal/preset/skills/lingtai-update/reference/mainland-china
Command: npx skills add https://github.com/Lingtai-AI/lingtai --skill lingtai-update-mainland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Installing or updating LingTai TUI/portal releases from mainland China often fails because GitHub, proxy.golang.org, and pypi.org are unreachable or unreliable. This Skill documents how install.sh routes around those failures using domestic mirrors and provider selection.

Core Features & Use Cases

  • Automatic mirror configuration: When the Go proxy probe fails, install.sh exports GOPROXY (goproxy.cn), GOSUMDB (sum.golang.google.cn), and NPM_CONFIG_REGISTRY (registry.npmmirror.com).
  • Release provider selection: --source auto|github|gitee (or LINGTAI_SOURCE) picks where release archives and the pinned kernel bundle come from, with fail-open fallback to GitHub for the same tag.
  • Single Python dependency index: Selects exactly one index — LINGTAI_PYPI_INDEX_URL if set, Tsinghua TUNA for Gitee provider, or pypi.org for GitHub — while LingTai itself always installs from the checksum-verified local artifact.
  • Use Case: An engineer on an Aliyun host runs the TUI updater and the upgrade fails fetching third-party Python packages from pypi.org; this Skill explains that the Gitee route switches the dependency index to the Tsinghua TUNA mirror and how to override it with LINGTAI_PYPI_INDEX_URL.

Quick Start

Ask the agent to diagnose a failed LingTai install from mainland China and configure the appropriate Go, npm, and PyPI mirrors before retrying.

Frequently Asked Questions about lingtai-update-mainland

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install LingTai from mainland China?

Run install.sh with --source auto or set LINGTAI_SOURCE; auto mode detects mainland China via a fail-open IP lookup and prefers the Gitee mirror. If the Go proxy probe fails, the script exports goproxy.cn, sum.golang.google.cn, and registry.npmmirror.com automatically.

How do I change the PyPI index used during LingTai installation?

Set LINGTAI_PYPI_INDEX_URL to your preferred index before running install.sh. Otherwise the installer uses Tsinghua TUNA (mirrors.tuna.tsinghua.edu.cn/pypi/web/simple) for the Gitee provider or pypi.org for GitHub, with exactly one index consulted.

What is the difference between the GitHub and Gitee release providers?

Both serve the same checksum-verified LingTai bundle for the same resolved tag. Gitee is preferred for mainland China reachability; any detection or reachability failure falls back to GitHub for the identical tag and bundle.

Why does the LingTai update still fail on the first download step in China?

The /update-tui and Homebrew bootstrap fetch the version-pinned install.sh from GitHub raw before any provider selection happens. That first fetch requires a working GitHub raw route regardless of which mirror or index is chosen later.

Does the mirror configuration affect Windows installs or --latest builds?

No. The dependency-index selection applies only to the POSIX verified-bundle path in install.sh. install.ps1 on Windows and the --latest main-from-source flow are unchanged.

How does Homebrew handle Go and npm mirrors differently?

Homebrew's superenv can scrub ordinary variables, so it uses HOMEBREW_GOPROXY mapped to GOPROXY and HOMEBREW_NPM_CONFIG_REGISTRY mapped to NPM_CONFIG_REGISTRY. The formula probes the npm registry with npm ping and leaves npm's registry unchanged if the probe fails.