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

[GH-ISSUE #11183] Windows: ALWAYS enable custom folders - don't force user profile, appdata or similar #7371

New Issue
Closed
opened 2026-04-12 19:25:47 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 19:25:47 -05:00
Owner
Copy Link

Originally created by @DoctorMG on GitHub (Jun 24, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11183

Nearly in every newer new open source project the same trouble: the software installs itself in any default folder (user, appdata etc.) and even the mega fat files go in the same SMALL but fast SSD harddisk, whereas the 24 TByte harddisk catches dust form being ignored.
I can shift models to this place - but I have no idea how I can publish another path than the default one.

FYI: since some years the hardware guys offer fast but small SSD memory - but with some Operating Systems they are full. With the the models, we need here - even bigger than some OS - Ollama and all the other tools that work like this, are unusable at all: dead by missing place, although on the machine terrabytes are free.

Please always think on options for setting paths (for the software itself, for the models that become added later).

Originally created by @DoctorMG on GitHub (Jun 24, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11183 Nearly in every newer new open source project the same trouble: the software installs itself in any default folder (user, appdata etc.) and even the mega fat files go in the same SMALL but fast SSD harddisk, whereas the 24 TByte harddisk catches dust form being ignored. I can shift models to this place - but I have no idea how I can publish another path than the default one. FYI: since some years the hardware guys offer fast but small SSD memory - but with some Operating Systems they are full. With the the models, we need here - even bigger than some OS - Ollama and all the other tools that work like this, are unusable at all: dead by missing place, although on the machine terrabytes are free. Please always think on options for setting paths (for the software itself, for the models that become added later).
GiteaMirror added the feature request label 2026-04-12 19:25:47 -05:00
GiteaMirror commented 2026-04-12 19:25:48 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jun 24, 2025):

https://github.com/ollama/ollama/blob/main/docs/windows.md#changing-install-location

<!-- gh-comment-id:3000164115 --> @rick-github commented on GitHub (Jun 24, 2025): https://github.com/ollama/ollama/blob/main/docs/windows.md#changing-install-location
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#7371
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?