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

[GH-ISSUE #1912] [Suggestion] Rename DISABLE_TELEMETRY to something app-specific #1241

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

Originally created by @levicki on GitHub (Jul 21, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1912

While naming an environment variable DISABLE_TELEMETRY is just fine for a docker container it's not really the best choice for a desktop app which shares global environment namespace with other apps.

Imagine the fallout if all apps started using such generic ennvironment variable names — users would not be able to control anything per app.

It's of course possible to set the telemetry opt-out variable in a command prompt and launch the app from there, but that's far from a convenient icon double-click.

Therefore, I suggest renaming it to ALLM_DISABLE_TELEMETRY or something similar.

Originally created by @levicki on GitHub (Jul 21, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1912 While naming an environment variable `DISABLE_TELEMETRY` is just fine for a docker container it's not really the best choice for a desktop app which shares global environment namespace with other apps. Imagine the fallout if all apps started using such generic ennvironment variable names — users would not be able to control anything per app. It's of course possible to set the telemetry opt-out variable in a command prompt and launch the app from there, but that's far from a convenient icon double-click. Therefore, I suggest renaming it to `ALLM_DISABLE_TELEMETRY` or something similar.
yindo closed this issue 2026-02-22 18:23:53 -05:00
yindo commented 2026-02-22 18:23:53 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 21, 2024):

The variable name in the app is not loaded from a global namespace (like system envs) - it comes from a .env file that is used to start the backend processes with the correct settings. While I presume someone could run a CLI command to start these same processes with written-in ENV commands.

Additionally, this is toggleable from the UI as well so disabling of telemetry is not restricted to an ENV variable and its value will persist between restarts

@timothycarambat commented on GitHub (Jul 21, 2024): The variable name in the app is not loaded from a global namespace (like system envs) - it comes from a `.env` file that is used to start the backend processes with the correct settings. While I presume someone _could_ run a CLI command to start these same processes with written-in ENV commands. Additionally, this is toggleable from the UI as well so disabling of telemetry is not restricted to an ENV variable and its value will persist between restarts
yindo commented 2026-02-22 18:23:53 -05:00
Author
Owner
Copy Link
Copy Source

@levicki commented on GitHub (Jul 21, 2024):

The variable name in the app is not loaded from a global namespace (like system envs) - it comes from a .env file that is used to start the backend processes with the correct settings.

Are we talking about Windows native app or a docker app?

Because as I said, for Docker it doesn't really matter, I was mostly suggesting it because of Windows app.

Anyway, it's not a big deal — it's just a good practice to prefix your env vars with something unique.

@levicki commented on GitHub (Jul 21, 2024): > The variable name in the app is not loaded from a global namespace (like system envs) - it comes from a .env file that is used to start the backend processes with the correct settings. Are we talking about Windows native app or a docker app? Because as I said, for Docker it doesn't really matter, I was mostly suggesting it because of Windows app. Anyway, it's not a big deal — it's just a good practice to prefix your env vars with something unique.
yindo changed title from [Suggestion] Rename DISABLE_TELEMETRY to something app-specific to [GH-ISSUE #1912] [Suggestion] Rename DISABLE_TELEMETRY to something app-specific 2026-06-05 14:39:42 -04: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
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#1241
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?