chore: land in-progress workspace changes before 1.16.2
The tree carried uncommitted work from several areas (web push, mobile screens, admin charts, test-hygiene cleanup, CI and map docs). It is landed as one commit so the release pipeline can start from a clean tree; the desktop transcript-correction behaviour shipped in the previous commit and is unchanged here.
This commit is contained in:
parent
9c2b6a9782
commit
7fe49c437e
144 changed files with 3760 additions and 4523 deletions
|
|
@ -35,7 +35,8 @@ for value in \
|
|||
"$SUPABASE_SERVICE_ROLE_KEY" \
|
||||
"$NEXT_PUBLIC_SUPABASE_URL" \
|
||||
"$NEXT_PUBLIC_SUPABASE_ANON_KEY" \
|
||||
"${NEXT_PUBLIC_PAYPLE_CLIENT_KEY:-}"; do
|
||||
"${NEXT_PUBLIC_PAYPLE_CLIENT_KEY:-}" \
|
||||
"${NEXT_PUBLIC_VAPID_PUBLIC_KEY:-${WEBPUSH_VAPID_PUBLIC_KEY:-}}"; do
|
||||
case "$value" in
|
||||
*$'\n'*|*$'\r'*) echo "Deployment values must be single-line" >&2; exit 1 ;;
|
||||
esac
|
||||
|
|
@ -79,10 +80,15 @@ echo -e "\n${YELLOW}[1.6/4] Building D3RO Voice Next.js Web App Image (/app)...$
|
|||
if [ -z "${NEXT_PUBLIC_PAYPLE_CLIENT_KEY:-}" ]; then
|
||||
echo -e "${YELLOW}NEXT_PUBLIC_PAYPLE_CLIENT_KEY is empty: Payple checkout will be disabled in the web app.${NC}"
|
||||
fi
|
||||
WEB_VAPID_PUBLIC_KEY="${NEXT_PUBLIC_VAPID_PUBLIC_KEY:-${WEBPUSH_VAPID_PUBLIC_KEY:-}}"
|
||||
if [ -z "$WEB_VAPID_PUBLIC_KEY" ]; then
|
||||
echo -e "${YELLOW}NEXT_PUBLIC_VAPID_PUBLIC_KEY is empty: browser notifications will stay unavailable and fail closed.${NC}"
|
||||
fi
|
||||
docker build -t d3ro-voice-web:latest -f "$ROOT_DIR/apps/web/Dockerfile" \
|
||||
--build-arg "NEXT_PUBLIC_SUPABASE_URL=$NEXT_PUBLIC_SUPABASE_URL" \
|
||||
--build-arg "NEXT_PUBLIC_SUPABASE_ANON_KEY=$NEXT_PUBLIC_SUPABASE_ANON_KEY" \
|
||||
--build-arg "NEXT_PUBLIC_PAYPLE_CLIENT_KEY=${NEXT_PUBLIC_PAYPLE_CLIENT_KEY:-}" \
|
||||
--build-arg "NEXT_PUBLIC_VAPID_PUBLIC_KEY=$WEB_VAPID_PUBLIC_KEY" \
|
||||
"$ROOT_DIR"
|
||||
echo -e "${GREEN}Docker image built: d3ro-voice-web:latest${NC}"
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue