Extension Products
Extension products are the commercial add-ons: the extension channels (a set of domestic channels, deployed as a channel sub-application container) and the three mini-program clients (admin, merchant, cashier). The open-source platform is complete and unaffected by them. To enable these extensions, first configure code-source credentials under "Extension Source", then operate on the corresponding pages. Editions and pricing are covered on the official pricing page.
Extension Source
Configuring Code-Source Credentials
The code source is where extension repositories are pulled from, Yunxiao Codeup by default. The form has three fields:
| Field | Description |
|---|---|
| Base URL | The code-source address; click "Restore Defaults" if changed in error |
| Username | The code-source account |
| Clone password | The HTTPS clone password; leave blank to keep the configured one |
Where to get the clone password: Yunxiao Codeup → Personal Settings → HTTPS clone password. After saving, the panel probes whether the credentials work and shows a message if the account or password is wrong.
Configure the credentials once; they are shared by the extension channel's source pulls and image builds and by mini-program builds. Without them the related features are unavailable and the pages show guidance.
Repository Status Board
The status board lists extension repositories by group with access, local commit, and probe time; click "Re-check Permissions" to refresh:
| Group | Repositories | Form |
|---|---|---|
| standard | The three mini-program source repositories | Source-delivery: pull the source, then build on the Mobile Management page |
| premium | The extension channel repository | Container-delivery: build the image, then deploy as a channel sub-application |
The tier badge at the top is derived from current permissions: all three mini-program clients accessible shows "Enhanced", plus the extension channel shows "Ultimate", and partial access shows "N / 4 authorized".
Mobile Management
Manages the three mini-program clients: the admin client (management mini-program), the merchant client (merchant self-service mini-program), and the cashier client (customer-payment mini-program). Code-source credentials are a prerequisite; the page shows a guidance banner when they are missing.
Each product has a card with version selection, source sync, and build.
Version and Source Sync
- Version selection supports following a branch or pinning a release tag, with a refreshable version list.
- Source sync pulls the selected version's source to the machine; the card shows the current source status and a summary of configured appids.
Building a Mini Program
Click "Build" to open the build dialog with three fields:
| Field | Description |
|---|---|
| Build platform | WeChat / Alipay / Douyin mini programs; the admin and merchant clients additionally offer the app platform, which produces a uni-app App resource bundle (for HBuilderX cloud packaging or offline Android packaging — not an APK); the cashier client has no app platform |
| Mini-program AppID | Recorded per platform; left blank it falls back to the value built into the source; for the app platform fill in the uni-app app identifier |
| API endpoint | The backend address the mini program calls. Left blank, the gateway backend domain is used automatically (HTTPS required); mini programs that use the mobile API domain should fill in that domain — see Gateway Management - Domain Binding |
Builds run as tasks; when one finishes, download the artifact zip from the build history (last 10 kept, with size and SHA256 checksum) and import it into the platform's developer tools to upload and publish.
Relation to Other Pages
- The extension channel's image build and deployment happen in the Business Environment, joining "One-Click Build All" automatically once credentials are ready.
- The gateway rules required for mini-program / APP login are covered in Gateway Management - External Endpoints.