Files
cgm-remote-monitor/docs/example-template.env
T
Ben WestandCopilot 3bb100836b fix: change UUID_HANDLING default to true
Update default from false to true to enable AID client compatibility
out of the box:

- lib/server/env.js: readENVTruthy('UUID_HANDLING', true)
- README.md: Document UUID_HANDLING in Features section
- docs/example-template.env: Update comments, show true as default

Rationale:
- Loop, Trio, AAPS, xDrip+ use UUID sync patterns by default
- Before MongoDB 5.x, UUID _id didn't crash (just didn't CRUD properly)
- ObjectID users completely unaffected (quirk only triggers on UUID)
- Can set UUID_HANDLING=false for strict mode if needed

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-03-17 14:17:48 -07:00

26 lines
1.0 KiB
Bash

CUSTOMCONNSTR_mongo=mongodb://....
CUSTOMCONNSTR_mongo_collection=
MONGO_PROFILE_COLLECTION=
API_SECRET=1234567890abc
HOSTNAME=0.0.0.0
ENABLE="devicestatus rawbg upbat careportal iob profile cage bage avg cob basal treatments sage boluscalc pump openaps iage speech"
SHOW_PLUGINS="rawbg-on careportal upbat iob profile cage cob basal avg treatments boluscalc pump openaps iage speech"
DISPLAY_UNITS="mmol"
TIME_FORMAT=24
ALARM_TYPES="predict"
LANGUAGE=en
INSECURE_USE_HTTP=true
PORT=1337
NODE_ENV=development
AUTH_FAIL_DELAY=50
# UUID handling for AID clients (Loop, Trio, AAPS, xDrip+)
# When true (default): UUID _id values are normalized to 'identifier' field
# - POST/PUT: UUID in _id extracted to identifier, server generates ObjectId
# - GET/DELETE: UUID _id searches by identifier field
# When false: Strict mode - UUID _id values rejected on write, ignored on read
# Default is true to support Loop, Trio, AAPS, xDrip+ UUID sync patterns
# UUID_HANDLING=true
#
# Set to false for strict ObjectId-only mode:
# UUID_HANDLING=false