API Proxy Release Package
===================================

Contents:
- api-proxy.jar
- deploy-api-proxy.sh
- collect-api-proxy-logs.sh
- cleanup-api-proxy-logs.sh
- install-api-proxy.sh
- deploy/api-proxy-common.sh
- DEPLOYMENT.zh-CN.pdf
- DEPLOYMENT.en-US.pdf
- build-info.properties

Build Identity:
- Version: 1.0.0
- Git Build UUID: f592c1fb9ed894d8081a01b797f8237784c0f942
- Build Time UTC: 2026-05-25T10:01:56Z

Workflow:
1. Extract the .tar.gz package.
2. Enter the extracted directory: cd api-proxy-1.0.0
3. Read DEPLOYMENT.zh-CN.pdf or DEPLOYMENT.en-US.pdf for prerequisites and operational details.
4. Run ./deploy-api-proxy.sh --install root@<node-ip> to deploy, or ./deploy-api-proxy.sh --uninstall root@<node-ip> to stop the service and remove its install workspace, logs, upload workspace, runtime workspace, and owned database tables.
5. Input the hidden SSH password when prompted, or export API_PROXY_SSH_PASSWORD ahead of time.
6. The script auto-detects single-node or dual-node HA and, in HA mode, relays peer-node operations through the entered node.
7. Run ./collect-api-proxy-logs.sh root@<node-ip> to collect full logs, service journals, keepalived data in HA mode, and node logs from all detected nodes.
8. Run ./cleanup-api-proxy-logs.sh root@<node-ip> to clear logs without moving the VIP or stopping keepalived; if api-proxy is running, the script restarts it after cleanup.

Build Notes:
- The packaged api-proxy.jar is an obfuscated release jar.
- The ProGuard mapping file is generated locally at api-proxy-1.0.0-proguard.map and is not bundled into the release package.

Safety:
- If an existing deployment is detected, the deploy script asks for confirmation before replacing it.
- install-api-proxy.sh keeps a timestamped jar backup on the remote host before overwriting the current jar.
- Uninstall drops only owned MySQL tables; it never drops the database/schema itself.
