Skip to content

docs: update .env.example with comprehensive variables and comments#511

Merged
CaralHsi merged 2 commits intoMemTensor:mainfrom
fancyboi999:docs/update-env-example
Nov 24, 2025
Merged

docs: update .env.example with comprehensive variables and comments#511
CaralHsi merged 2 commits intoMemTensor:mainfrom
fancyboi999:docs/update-env-example

Conversation

@fancyboi999
Copy link
Copy Markdown
Contributor

Summary

Updated docker/.env.example to include all currently used environment variables in the codebase, ensuring users have a complete reference for configuration.

Source

Changes

  • Added missing variables (e.g., API_SCHEDULER_ON, MOS_CUBE_PATH).
  • Clarified comments and usage for existing variables.
  • Verified against [src/memos/api/config.py] and other source files.

Suggestion

To further improve the onboarding experience, I suggest we consider providing multiple preset configuration files (e.g., .env.simple, .env.production, .env.dev) or a .env.sync mechanism. This would allow users to quickly choose a configuration that matches their use case without needing to manually toggle every option in a single large file.

@CaralHsi CaralHsi requested a review from fridayL November 21, 2025 09:16
@CaralHsi CaralHsi merged commit 5d434ea into MemTensor:main Nov 24, 2025
tianxing02 pushed a commit to tianxing02/MemOS that referenced this pull request Feb 24, 2026
…emTensor#511)

## Summary
Updated
[docker/.env.example](cci:7://file:///Users/nowcoder/Desktop/MemOS/docker/.env.example:0:0-0:0)
to include all currently used environment variables in the codebase,
ensuring users have a complete reference for configuration.

## Source
- Related Issue: MemTensor#505

## Changes
- Added missing variables (e.g., `API_SCHEDULER_ON`, `MOS_CUBE_PATH`).
- Clarified comments and usage for existing variables.
- Verified against [src/memos/api/config.py] and other source files.

## Suggestion
To further improve the onboarding experience, I suggest we consider
providing multiple preset configuration files (e.g., `.env.simple`,
`.env.production`, `.env.dev`) or a `.env.sync` mechanism. This would
allow users to quickly choose a configuration that matches their use
case without needing to manually toggle every option in a single large
file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants