Files
life-echo/app-expo/.env.example
Sully f09ae248f9 feat: OpenTelemetry LGTM observability, dev tooling, and memoir UX fixes (#31) (#32)
* add staging ios app build script

* feat(api): add OpenTelemetry LGTM stack for local observability

Wire OTel traces, metrics, and logs through a collector to Tempo,
Prometheus, and Loki, with custom LLM instrumentation, dev compose overlay,
Grafana provisioning, env templates, and development.sh auto-start.



* feat: expand observability, harden dev tooling, and fix expo staging UX

Add business and LLM Prometheus metrics with Grafana dashboards, alerting,
and a metrics verification script. Wire telemetry through adapters and core
LLM paths, and document the local LGTM workflow.

Fix development.sh for macOS bash 3.2, open Grafana and eval-web in Chrome,
and repair eval-web auto-open (unbound EVAL_WEB_BROWSER_SCHEDULED). Merge
internal-eval into the main dev script with improved compose handling.

Require EXPO_PUBLIC_* at build time, improve iOS HTTP ATS for staging IPs,
show memoir empty state instead of load errors when no chapters exist, and
add jest env setup plus chapter list response normalization.



* chore: enable Grafana Assistant Cursor plugin



* fix: memoir empty state and repair withdrawn 0020_chapters_book_id stamp

Show empty memoir UI when the chapter list succeeds with no items; treat auth/404 as non-fatal. Extend alembic revision repair so local dev DBs stamped with the removed 0020_chapters_book_id migration can roll back and upgrade to 0019.



---------

Co-authored-by: Kevin <kevin@brighteng.org>
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-20 15:14:13 +08:00

32 lines
1.6 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 环境模板在 app-expo/env/{development,staging,production}(勿在根目录放 .env.production
# 本地npm start 会通过 prestart 执行 `use-env development` 生成 .env
# 或手动 `npm run use-env -- staging` / `npm run use-env -- production`。
# CIGitHub Actions 在构建 APK 前会按分支调用 use-envmain → stagingtag → production
#
# 勿在 app-expo 根目录创建 .env.staging / .env.productionRelease 构建时 Expo 会按
# NODE_ENV=production 自动加载 .env.production覆盖 use-env 写入的 .env。
#
# APP_VARIANT / EXPO_PUBLIC_APP_VARIANT控制 Bundle ID 与「关于」页是否显示后端地址
# development / staging → 显示版本 + API 地址production → 仅版本号
#
# 变量在构建时注入;修改后需重新 prebuild/打包客户端。
#
# 助手朗读:无独立 EXPO_PUBLIC_* TTS 开关。会话页顶栏在每轮 WebSocket 中带 `tts_this_turn`
# 服务端是否具备合成能力见 api/.env 中 ENABLE_TTS 等(模板见 api/.env.example
# --- development本地关于页显示版本 + API---
# APP_VARIANT=development
# EXPO_PUBLIC_APP_VARIANT=development
# EXPO_PUBLIC_API_URL=http://127.0.0.1:8000
# EXPO_PUBLIC_WS_URL=ws://127.0.0.1:8000
# --- staging必填无默认值示例见 env/staging---
# APP_VARIANT=staging
# EXPO_PUBLIC_APP_VARIANT=staging
# EXPO_PUBLIC_API_URL=http://your-staging-host:8000
# EXPO_PUBLIC_WS_URL=ws://your-staging-host:8000
# --- production ---
# EXPO_PUBLIC_API_URL=https://your-api.example.com
# EXPO_PUBLIC_WS_URL=wss://your-api.example.com