docs: Clarify .env file scope in Flash documentation#562
Conversation
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
|
|
||
| <Warning> | ||
| Your Runpod API key needs **All** access permissions to your Runpod account. | ||
| Values in your `.env` file are only used for local CLI commands and development. They are **not** passed to deployed endpoints. To set environment variables on deployed endpoints, use the `env` parameter in your endpoint configuration. See [Endpoint parameters](/flash/configuration/parameters#env) for details. |
There was a problem hiding this comment.
Citation: Based on PR #39 which clarifies that .env files only populate os.environ for local CLI use—they are not carried to deployed endpoints. Key files: docs/cli/getting-started.md, docs/cli/workflows.md.
View source
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
| ``` | ||
|
|
||
| <Warning> | ||
| Values in your project's `.env` file are only available locally for CLI commands and development. They are **not** passed to deployed endpoints. You must declare environment variables explicitly using the `env` parameter. |
There was a problem hiding this comment.
Citation: Based on PR #39 which documents the pattern env={"KEY": os.environ["KEY"]} to pass local env vars to deployed endpoints. Key files: docs/cli/commands.md, docs/cli/workflows.md.
View source
|
|
||
| **Option 3: Add to your shell profile (`~/.bashrc` or `~/.zshrc`) for global authorization** | ||
| <Note> | ||
| Values in your `.env` file are only available locally for CLI commands. They are not passed to deployed endpoints. |
There was a problem hiding this comment.
Citation: Based on PR #39 which recommends flash login as primary auth method and clarifies .env scope. Key files: docs/cli/troubleshooting.md, docs/cli/getting-started.md.
View source
| ``` | ||
|
|
||
| <Note> | ||
| Values in your `.env` file are only available locally for CLI commands. They are not passed to deployed endpoints. |
There was a problem hiding this comment.
Citation: Based on PR #39 which clarifies .env scope for local development. Added flash login as recommended auth fix per the PR guidance.
View source
|
Just a reminder: If you'd like me to act on any feedback you have via Github comments, just type @Promptless in your suggestion and I'll get right on it! (I won't show up in the user dropdown, but I'll process any request that has @Promptless in the comment body.) |
1 participant
Open this suggestion in Promptless to view citations and reasoning process
Clarifies that
.envfiles only work for local CLI commands and development—values are not passed to deployed endpoints. Updates login, parameters, troubleshooting, and local-testing docs to recommendflash loginas primary auth and show how to use theenvparameter to pass variables to deployed workers.Trigger Events
Internal discussion about ensuring Flash documentation covers how .env files work, referencing a specific PR in the flash-examples repository.
Promptless Research (9 files, 1 GitHub PR)
.long_term_context/product_knowledge/product_overview.md.long_term_context/doc_workflow/client_instructions.md.long_term_context/style/client_style_guide.mdflash/cli/env.mdxflash/cli/login.mdxflash/configuration/parameters.mdxflash/quickstart.mdxflash/apps/local-testing.mdxflash/troubleshooting.mdxAgent Response
Tip: Assign suggestions to team members in the Promptless dashboard to claim work 👥