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 #1003] Request: Support Modelfile management API #486

New Issue
Closed
opened 2026-04-12 10:09:56 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-12 10:09:56 -05:00
Owner
Copy Link

Originally created by @LushVoid on GitHub (Nov 4, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/1003

Description

As a developer integrating with the Ollama server, I find the current workflow for creating and managing models requires handling Modelfiles locally before uploading. This process can be cumbersome.

Feature Request

I would like to request an enhancement to the API that would allow for direct editing of Modelfiles through API requests. This would enable more dynamic and automated workflows, particularly for applications that are deployed as browsers.

Suggested Solution

Implement a new API endpoint (e.g., PUT /api/model/:name) that allows users to send a Modelfile's content or updates to an existing model's Modelfile directly in the request body. The server could then apply these changes to the model without requiring the webapp user to manage and upload files manually and/or copy a new file entirely.

Dynamic Model Management: This feature would simplify the process of programmatically adjusting models based on application needs or user feedback without the overhead of file management.

Somthing like:

curl -X PUT http://localhost:11434/api/models/rMario -d '{ "modelfile": "<updated_modelfile_content_here>" }'

Conclusion

Providing a means to edit Modelfiles directly via the API would greatly enhance the developer experience and broaden the use cases for the Ollama server. It would also bring the tool in line with contemporary cloud-native practices.

Thank you for considering this request.

Originally created by @LushVoid on GitHub (Nov 4, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/1003 ### Description As a developer integrating with the Ollama server, I find the current workflow for creating and managing models requires handling Modelfiles locally before uploading. This process can be cumbersome. ### Feature Request I would like to request an enhancement to the API that would allow for direct editing of Modelfiles through API requests. This would enable more dynamic and automated workflows, particularly for applications that are deployed as browsers. ### Suggested Solution Implement a new API endpoint (e.g., `PUT /api/model/:name`) that allows users to send a Modelfile's content or updates to an existing model's Modelfile directly in the request body. The server could then apply these changes to the model without requiring the webapp user to manage and upload files manually and/or copy a new file entirely. **Dynamic Model Management:** This feature would simplify the process of programmatically adjusting models based on application needs or user feedback without the overhead of file management. Somthing like: `curl -X PUT http://localhost:11434/api/models/rMario -d '{ "modelfile": "<updated_modelfile_content_here>" }'` ### Conclusion Providing a means to edit Modelfiles directly via the API would greatly enhance the developer experience and broaden the use cases for the Ollama server. It would also bring the tool in line with contemporary cloud-native practices. Thank you for considering this request.
GiteaMirror commented 2026-04-12 10:09:57 -05:00
Author
Owner
Copy Link

@LushVoid commented on GitHub (Nov 5, 2023):

My current workaround is to set up an additional node server for my React app, then have it act as the intermediate for the Ollam.

<!-- gh-comment-id:1793886037 --> @LushVoid commented on GitHub (Nov 5, 2023): My current workaround is to set up an additional node server for my React app, then have it act as the intermediate for the Ollam.
GiteaMirror commented 2026-04-12 10:09:57 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Nov 5, 2023):

If I understand this issue correctly, this will be resolved by #898

<!-- gh-comment-id:1793887534 --> @mxyng commented on GitHub (Nov 5, 2023): If I understand this issue correctly, this will be resolved by #898
GiteaMirror commented 2026-04-12 10:09:57 -05:00
Author
Owner
Copy Link

@jmorganca commented on GitHub (Dec 22, 2023):

Closing with #898 (would love feedback!)

<!-- gh-comment-id:1867203061 --> @jmorganca commented on GitHub (Dec 22, 2023): Closing with #898 (would love feedback!)
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
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#486
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?