Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #207] [MERGED] Implement dumpENV if in prod environment #3242

New Issue
Closed
opened 2026-02-22 18:33:22 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:33:22 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/207
Author: @shatfield4
Created: 8/21/2023
Status: ✅ Merged
Merged: 8/21/2023
Merged by: @timothycarambat

Base: master ← Head: 206-dump-envs-on-update-in-production

📝 Commits (1)

  • 4e9f113 implement dumpENV if in prod environment

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 server/endpoints/system.js (+1 -0)

📄 Description

resolves #206

In production mode, if there are updates to the env it previously did not dump the .env file and if for any reason the system were to reboot all the env variables will be lost. This fix makes the backend dump the .env file on any environment variable change to ensure all .env variables are stored.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/207 **Author:** [@shatfield4](https://github.com/shatfield4) **Created:** 8/21/2023 **Status:** ✅ Merged **Merged:** 8/21/2023 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `206-dump-envs-on-update-in-production` --- ### 📝 Commits (1) - [`4e9f113`](https://github.com/Mintplex-Labs/anything-llm/commit/4e9f1134ac773c9d5081771324da682e3acff618) implement dumpENV if in prod environment ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `server/endpoints/system.js` (+1 -0) </details> ### 📄 Description resolves #206 In production mode, if there are updates to the env it previously did not dump the .env file and if for any reason the system were to reboot all the env variables will be lost. This fix makes the backend dump the .env file on any environment variable change to ensure all .env variables are stored. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:33:22 -05:00
yindo closed this issue 2026-02-22 18:33:22 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#3242
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?