github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-06 16:11:34 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #12306] manual dotenv: adding a flag for ollama to read a specific dotenv file #54690

New Issue
Open
opened 2026-04-29 06:57:30 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-29 06:57:30 -05:00
Owner
Copy Link

Originally created by @xushidev on GitHub (Sep 16, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12306

Hey! I would like to ask if it is possible to add a flag for Ollama to pull a specific dotenv file?

Following the guidelines,
New features: new features (e.g. API fields, environment variables) add surface area to Ollama and make it harder to maintain in the long run as they cannot be removed without potentially breaking users in the future.
This shouldn't potentially make Ollama harder to maintain, since it isn't gonna read a specific path, as users still need to provide the flag manually (unless it is for bash files).

Explain why the change is important.
Adding a way to point towards a specific dotenv file I think would help in the development of Ollama and it's models, along with testing various models.

Explain how the change will be used.

  1. This change can be used to make Ollama point towards a specific model directory almost permanently (in case of an external drive which may change directory letter on windows for example).
  2. Allows for easy changes to the environmental variables, before they are copied as global environment variables.

The proposal in short is:
Adding something alike ollama serve --config "/path/to/config.env"

Originally created by @xushidev on GitHub (Sep 16, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12306 Hey! I would like to ask if it is possible to add a flag for Ollama to pull a specific dotenv file? Following the guidelines, **New features: new features (e.g. API fields, environment variables) add surface area to Ollama and make it harder to maintain in the long run as they cannot be removed without potentially breaking users in the future.** This shouldn't potentially make Ollama harder to maintain, since it isn't gonna read a specific path, as users still need to provide the flag manually (unless it is for bash files). **Explain why the change is important.** Adding a way to point towards a specific dotenv file I think would help in the development of Ollama and it's models, along with testing various models. **Explain how the change will be used.** 1. This change can be used to make Ollama point towards a specific model directory almost permanently (in case of an external drive which may change directory letter on windows for example). 2. Allows for easy changes to the environmental variables, before they are copied as global environment variables. The proposal in short is: Adding something alike `ollama serve --config "/path/to/config.env"`
GiteaMirror added the feature request label 2026-04-29 06:57:30 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#54690
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?