[GH-ISSUE #206] Dump ENVs on update in production #128

Closed
opened 2026-02-22 18:18:02 -05:00 by yindo · 0 comments
Owner

Originally created by @timothycarambat on GitHub (Aug 21, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/206

Originally assigned to: @shatfield4 on GitHub.

When in production mode, we should proactively dump the ENV to the .env file so that in the event of a reboot the system reboots with the most recent changes at all times.

It is possible the env was not dumped and changes occurred - leading the the system to boot with old or outdated ENVs

Originally created by @timothycarambat on GitHub (Aug 21, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/206 Originally assigned to: @shatfield4 on GitHub. When in production mode, we should proactively dump the ENV to the `.env` file so that in the event of a reboot the system reboots with the most recent changes at all times. It is possible the env was not dumped and changes occurred - leading the the system to boot with old or outdated ENVs
yindo added the enhancement label 2026-02-22 18:18:02 -05:00
yindo closed this issue 2026-02-22 18:18:02 -05:00
yindo changed title from Dump ENVs on update in production to [GH-ISSUE #206] Dump ENVs on update in production 2026-06-05 14:33:38 -04:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#128