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

[PR #15117] Windows installer options #15034

New Issue
Open
opened 2026-04-13 01:08:56 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 01:08:56 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/15117
Author: @PiyushInt
Created: 3/28/2026
Status: 🔄 Open

Base: main ← Head: windows-installer-options

📝 Commits (2)

  • cbb9112 Expose numeric parameter_count in model details
  • 0ecd204 Add Windows installer directory and models options

📊 Changes

4 files changed (+116 additions, -2 deletions)

View changed files

📝 api/types.go (+1 -0)
📝 app/ollama.iss (+59 -1)
📝 server/routes.go (+55 -1)
📝 server/routes_create_test.go (+1 -0)

📄 Description

This pull request improves the Windows installer user experience and addresses the main pain points from issue #15038.

It makes two key changes. First, it re-enables the installer directory selection page so that users can choose a custom installation path through the GUI, instead of being forced to use the default path or rely on the /DIR command-line flag. Second, it adds a new “Model storage location” wizard page that allows users to choose where downloaded models are stored. The selected models directory is wired to the OLLAMA_MODELS environment variable for the current user. If OLLAMA_MODELS was already set and the user keeps that value, it is preserved. If OLLAMA_MODELS was not set and the user keeps the default path (%USERPROFILE%.ollama\models), no environment variable is written and behavior remains unchanged. If the user chooses a custom path, OLLAMA_MODELS is set to that directory. If OLLAMA_MODELS previously existed but the user reverts to the built-in default path, the override is removed.

This pull request keeps the existing Inno Setup–based installer and focuses on adding the requested configuration options and a more typical Windows GUI experience, rather than migrating to NSIS.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/15117 **Author:** [@PiyushInt](https://github.com/PiyushInt) **Created:** 3/28/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `windows-installer-options` --- ### 📝 Commits (2) - [`cbb9112`](https://github.com/ollama/ollama/commit/cbb91120d2045d57057c1e931f9d16e91cc4ea71) Expose numeric parameter_count in model details - [`0ecd204`](https://github.com/ollama/ollama/commit/0ecd204eecf9b9517e426874a2834185747cf3a8) Add Windows installer directory and models options ### 📊 Changes **4 files changed** (+116 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `api/types.go` (+1 -0) 📝 `app/ollama.iss` (+59 -1) 📝 `server/routes.go` (+55 -1) 📝 `server/routes_create_test.go` (+1 -0) </details> ### 📄 Description This pull request improves the Windows installer user experience and addresses the main pain points from issue #15038. It makes two key changes. First, it re-enables the installer directory selection page so that users can choose a custom installation path through the GUI, instead of being forced to use the default path or rely on the /DIR command-line flag. Second, it adds a new “Model storage location” wizard page that allows users to choose where downloaded models are stored. The selected models directory is wired to the OLLAMA_MODELS environment variable for the current user. If OLLAMA_MODELS was already set and the user keeps that value, it is preserved. If OLLAMA_MODELS was not set and the user keeps the default path (%USERPROFILE%.ollama\models), no environment variable is written and behavior remains unchanged. If the user chooses a custom path, OLLAMA_MODELS is set to that directory. If OLLAMA_MODELS previously existed but the user reverts to the built-in default path, the override is removed. This pull request keeps the existing Inno Setup–based installer and focuses on adding the requested configuration options and a more typical Windows GUI experience, rather than migrating to NSIS. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 01:08:56 -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 pull-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#15034
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?