Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #3640] [DOCS]: How to add local folder (Docker volume mount) as document source in Workspace? #2350

New Issue
Closed
opened 2026-02-22 18:29:18 -05:00 by yindo · 7 comments
yindo commented 2026-02-22 18:29:18 -05:00
Owner
Copy Link
Copy Source

Originally created by @witzker on GitHub (Apr 13, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3640

Description

Hi AnythingLLM community,

I'm setting up AnythingLLM using the latest Docker image via Docker Compose on an Ubuntu VM. My goal is to use documents stored on my Synology NAS, which is mounted into the VM via NFS.

My setup:

Synology NAS share mounted via NFS to /mnt/nas_docs on the Ubuntu VM host.

The relevant volume mount in my docker-compose.yml for the anythingllm service is:

volumes:

  • /mnt/nas_docs:/app/server/storage/documents/nas_docs:ro
    Use code with caution.
    Yaml
    I have verified that the mount works on the VM host (ls -l /mnt/nas_docs shows files) and adjusted NAS/host permissions (chmod 755).

Ollama is running in a separate container and configured correctly within the AnythingLLM workspace settings.

My Problem:
I cannot find the option in the AnythingLLM web UI to add the existing folder /app/server/storage/documents/nas_docs (which represents my NAS share inside the container) as a document source for my workspace ("K.I-Docs-NAS").

Clicking the "Upload/Manage Documents" icon (⬆️ icon next to the workspace name) only shows options to upload individual files or drag & drop.

Clicking "+ New Folder" inside that dialog only allows creating a new empty folder within AnythingLLM's storage.

The "Data Connectors" tab only shows external sources like GitHub, YouTube etc.

Question:
Where in the UI should I look to select and sync an existing local directory from within the container (specifically /app/server/storage/documents/nas_docs) as a document source? Is there a specific button or menu I'm missing?

Thanks for your help!

Originally created by @witzker on GitHub (Apr 13, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3640 ### Description Hi AnythingLLM community, I'm setting up AnythingLLM using the latest Docker image via Docker Compose on an Ubuntu VM. My goal is to use documents stored on my Synology NAS, which is mounted into the VM via NFS. My setup: Synology NAS share mounted via NFS to /mnt/nas_docs on the Ubuntu VM host. The relevant volume mount in my docker-compose.yml for the anythingllm service is: volumes: - /mnt/nas_docs:/app/server/storage/documents/nas_docs:ro Use code [with caution](https://support.google.com/legal/answer/13505487). Yaml I have verified that the mount works on the VM host (ls -l /mnt/nas_docs shows files) and adjusted NAS/host permissions (chmod 755). Ollama is running in a separate container and configured correctly within the AnythingLLM workspace settings. My Problem: I cannot find the option in the AnythingLLM web UI to add the existing folder /app/server/storage/documents/nas_docs (which represents my NAS share inside the container) as a document source for my workspace ("K.I-Docs-NAS"). Clicking the "Upload/Manage Documents" icon (⬆️ icon next to the workspace name) only shows options to upload individual files or drag & drop. Clicking "+ New Folder" inside that dialog only allows creating a new empty folder within AnythingLLM's storage. The "Data Connectors" tab only shows external sources like GitHub, YouTube etc. Question: Where in the UI should I look to select and sync an existing local directory from within the container (specifically /app/server/storage/documents/nas_docs) as a document source? Is there a specific button or menu I'm missing? Thanks for your help!
yindo added the documentation label 2026-02-22 18:29:18 -05:00
yindo closed this issue 2026-02-22 18:29:18 -05:00
yindo commented 2026-02-22 18:29:18 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Apr 14, 2025):

Document uploading must be done via the UI/API - you cannot attach a folder into the storage and expect those files to be available for RAG, since all documents need to be processed by the collector to parse + format them into the proper format to be consumed and upserted to the local vector db.

So in this case, you dont need to virtual mount anything. If your client has access to the file, you can select it to be uploaded and the file will be passed over the wire to the backend and parsed without Anythingllm ever having to reach out and access the NAS.

@timothycarambat commented on GitHub (Apr 14, 2025): Document uploading must be done via the UI/API - you cannot attach a folder into the storage and expect those files to be available for RAG, since all documents need to be processed by the collector to parse + format them into the proper format to be consumed and upserted to the local vector db. So in this case, you dont need to virtual mount anything. If your client has access to the file, you can select it to be uploaded and the file will be passed over the wire to the backend and parsed without Anythingllm ever having to reach out and access the NAS.
yindo commented 2026-02-22 18:29:18 -05:00
Author
Owner
Copy Link
Copy Source

@lesfuller commented on GitHub (Oct 10, 2025):

I am new to ALLM, and so this may sound like a silly question, but just what is "+ New Folder" used for then? I am trying to upload technical docs that remain constant and available for various workspaces and I though this might be the answer.

@lesfuller commented on GitHub (Oct 10, 2025): I am new to ALLM, and so this may sound like a silly question, but just what is "+ New Folder" used for then? I am trying to upload technical docs that remain constant and available for various workspaces and I though this might be the answer.
yindo commented 2026-02-22 18:29:18 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Oct 10, 2025):

@lesfuller

I am new to ALLM, and so this may sound like a silly question, but just what is "+ New Folder" used for then? I am trying to upload technical docs that remain constant and available for various workspaces and I though this might be the answer.

New folder is how you can partition uploaded documents in the uploader UI, this is not a representation of your filesystem. However we are going to support filestorage mounts to the container soon to alleviate this confusion

@timothycarambat commented on GitHub (Oct 10, 2025): @lesfuller > I am new to ALLM, and so this may sound like a silly question, but just what is "+ New Folder" used for then? I am trying to upload technical docs that remain constant and available for various workspaces and I though this might be the answer. New folder is how you can partition uploaded documents in the uploader UI, this is not a representation of your filesystem. However we are going to support filestorage mounts to the container soon to alleviate this confusion
yindo commented 2026-02-22 18:29:18 -05:00
Author
Owner
Copy Link
Copy Source

@lesfuller commented on GitHub (Oct 11, 2025):

Great, thanks for the quick reply, looking forward to that.

@lesfuller commented on GitHub (Oct 11, 2025): Great, thanks for the quick reply, looking forward to that.
yindo commented 2026-02-22 18:29:18 -05:00
Author
Owner
Copy Link
Copy Source

@whattheschnell commented on GitHub (Feb 12, 2026):

Any update on incorporating that? If i'm running anything remotely, I want to be able to upload via local file path, rather than only being able to upload from the remote device

@whattheschnell commented on GitHub (Feb 12, 2026): Any update on incorporating that? If i'm running anything remotely, I want to be able to upload via local file path, rather than only being able to upload from the remote device
yindo changed title from [DOCS]: How to add local folder (Docker volume mount) as document source in Workspace? to [GH-ISSUE #3640] [DOCS]: How to add local folder (Docker volume mount) as document source in Workspace? 2026-06-05 14:46:04 -04:00
yindo commented 2026-06-05 14:46:05 -04:00
Author
Owner
Copy Link
Copy Source

@heartacker commented on GitHub (Apr 7, 2026):

I want this indeed, any update , my brother

<!-- gh-comment-id:4196992258 --> @heartacker commented on GitHub (Apr 7, 2026): I want this indeed, any update , my brother
yindo commented 2026-06-05 14:46:05 -04:00
Author
Owner
Copy Link
Copy Source

@heartacker commented on GitHub (Apr 7, 2026):

I deploy this to my nas, I want my doc being rag.thank you all the time

<!-- gh-comment-id:4196995641 --> @heartacker commented on GitHub (Apr 7, 2026): I deploy this to my nas, I want my doc being rag.thank you all the time
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#2350
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?