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

[GH-ISSUE #15673] docs: continue collapsing legacy compatibility snapshots into canonical docs buckets #72058

New Issue
Closed
opened 2026-05-05 03:24:26 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-05 03:24:26 -05:00
Owner
Copy Link

Originally created by @PureBlissAK on GitHub (Apr 18, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15673

Summary\n\nThe repository now has canonical on-prem documentation entry points in docs/operations/ON_PREM_DEPLOYMENT_MODEL.md and docs/operations/ON_PREM_EXECUTION_INDEX.md. The remaining cleanup work is to continue collapsing older compatibility snapshots and duplicate navigation pages into the canonical docs buckets so the docs tree stays shallow, consistent, and easy to navigate.\n\n## Why this is still needed\n\n- Several legacy pages still exist as compatibility snapshots outside the new canonical buckets.\n- The canonical docs map is now in place, so the remaining work is mostly consolidation and link cleanup rather than new structure design.\n- Keeping this tracked separately will make it easier for other contributors or agents to continue the cleanup in small, reviewable steps.\n\n## Suggested acceptance criteria\n\n- Remaining legacy docs are either reduced to short compatibility snapshots or moved into the canonical docs buckets.\n- Root-level or duplicate navigation pages point to the canonical docs where appropriate.\n- No broken references remain for the on-prem execution entry points.\n- The docs tree continues to prefer SSOT pages over duplicated guidance.\n\n## Notes\n\nThis issue is intentionally scoped to documentation consolidation only. It does not change the on-prem execution model itself.

Originally created by @PureBlissAK on GitHub (Apr 18, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15673 ## Summary\n\nThe repository now has canonical on-prem documentation entry points in docs/operations/ON_PREM_DEPLOYMENT_MODEL.md and docs/operations/ON_PREM_EXECUTION_INDEX.md. The remaining cleanup work is to continue collapsing older compatibility snapshots and duplicate navigation pages into the canonical docs buckets so the docs tree stays shallow, consistent, and easy to navigate.\n\n## Why this is still needed\n\n- Several legacy pages still exist as compatibility snapshots outside the new canonical buckets.\n- The canonical docs map is now in place, so the remaining work is mostly consolidation and link cleanup rather than new structure design.\n- Keeping this tracked separately will make it easier for other contributors or agents to continue the cleanup in small, reviewable steps.\n\n## Suggested acceptance criteria\n\n- Remaining legacy docs are either reduced to short compatibility snapshots or moved into the canonical docs buckets.\n- Root-level or duplicate navigation pages point to the canonical docs where appropriate.\n- No broken references remain for the on-prem execution entry points.\n- The docs tree continues to prefer SSOT pages over duplicated guidance.\n\n## Notes\n\nThis issue is intentionally scoped to documentation consolidation only. It does not change the on-prem execution model itself.
GiteaMirror commented 2026-05-05 03:24:27 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

Completed in repo: added docs/operations/ON_PREM_EXECUTION_INDEX.md and docs/operations/ON_PREM_DEPLOYMENT_MODEL.md, aligned shared/meta navigation, and kept the docs tree centered on the new canonical on-prem entry points. No pnpm docs bucket was added because there is no pnpm workspace evidence in this repository.

<!-- gh-comment-id:4274105482 --> @PureBlissAK commented on GitHub (Apr 18, 2026): Completed in repo: added docs/operations/ON_PREM_EXECUTION_INDEX.md and docs/operations/ON_PREM_DEPLOYMENT_MODEL.md, aligned shared/meta navigation, and kept the docs tree centered on the new canonical on-prem entry points. No pnpm docs bucket was added because there is no pnpm workspace evidence in this repository.
GiteaMirror commented 2026-05-05 03:24:28 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

Follow-up: collapsed the remaining legacy operations compatibility snapshots (LOCAL_DEVELOPMENT_SETUP.md, DEVELOPER_QUICK_REFERENCE.md, and DOCUMENTATION_UPDATE_SUMMARY.md) into short pointer pages. The stale real-IP guidance was removed, and the canonical path remains ON_PREM_EXECUTION_INDEX.md plus ON_PREM_DEPLOYMENT_MODEL.md.

<!-- gh-comment-id:4274118674 --> @PureBlissAK commented on GitHub (Apr 18, 2026): Follow-up: collapsed the remaining legacy operations compatibility snapshots (LOCAL_DEVELOPMENT_SETUP.md, DEVELOPER_QUICK_REFERENCE.md, and DOCUMENTATION_UPDATE_SUMMARY.md) into short pointer pages. The stale real-IP guidance was removed, and the canonical path remains ON_PREM_EXECUTION_INDEX.md plus ON_PREM_DEPLOYMENT_MODEL.md.
GiteaMirror commented 2026-05-05 03:24:28 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

Follow-up: collapsed the remaining legacy operations compatibility snapshots (LOCAL_DEVELOPMENT_SETUP.md, DEVELOPER_QUICK_REFERENCE.md, and DOCUMENTATION_UPDATE_SUMMARY.md) into short pointer pages. The stale real-IP guidance was removed, and the canonical path remains ON_PREM_EXECUTION_INDEX.md plus ON_PREM_DEPLOYMENT_MODEL.md.

<!-- gh-comment-id:4274118783 --> @PureBlissAK commented on GitHub (Apr 18, 2026): Follow-up: collapsed the remaining legacy operations compatibility snapshots (LOCAL_DEVELOPMENT_SETUP.md, DEVELOPER_QUICK_REFERENCE.md, and DOCUMENTATION_UPDATE_SUMMARY.md) into short pointer pages. The stale real-IP guidance was removed, and the canonical path remains ON_PREM_EXECUTION_INDEX.md plus ON_PREM_DEPLOYMENT_MODEL.md.
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#72058
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?