starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-25 07:56:05 +03:00

[GH-ISSUE #1091] Seperate locations for downloads and DB #716

New issue

Closed

opened 2026-03-02 11:52:07 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 11:52:07 +03:00

Owner

Originally created by @sdenike on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1091

Describe the feature you'd like

I would love to see an option to split up the DB and Assets that are downloaded to two different locations. With my docker setup I have many things running on the host such as the DB for containers, and system files as they are served on an NVME drive, but for storage I do have a NAS mounted to my system where I have much more space, and would love to store items there to keep the host filesystem trimmed down.

Describe the benefits this would bring to existing Hoarder users

This could help with data storage.

Can the goal of this request already be achieved via other means?

This could likely be achieved by symlinking the proper directories to the other filesystem, but it seems kind of hacky.

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundamental request

Additional context

No response

Originally created by @sdenike on GitHub (Mar 4, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1091 ### Describe the feature you'd like I would love to see an option to split up the DB and Assets that are downloaded to two different locations. With my docker setup I have many things running on the host such as the DB for containers, and system files as they are served on an NVME drive, but for storage I do have a NAS mounted to my system where I have much more space, and would love to store items there to keep the host filesystem trimmed down. ### Describe the benefits this would bring to existing Hoarder users This could help with data storage. ### Can the goal of this request already be achieved via other means? This could likely be achieved by symlinking the proper directories to the other filesystem, but it seems kind of hacky. ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### Additional context _No response_

kerem

2026-03-02 11:52:07 +03:00

closed this issue
added the
feature request

status/approved

pri/medium

good first issue
labels

kerem commented

2026-03-02 11:52:09 +03:00

Author

Owner

@patach commented on GitHub (Mar 28, 2025):

I would definitely second this, as someone who bumped into the issue of trying to get the data folder installed on the mounted NAS I have, resulting in an SQLITE BUSY error.

Installing /data/ on the native machine solves this issue.

@patach commented on GitHub (Mar 28, 2025): I would definitely second this, as someone who bumped into the issue of trying to get the data folder installed on the mounted NAS I have, resulting in an SQLITE BUSY error. Installing /data/ on the native machine solves this issue.

kerem commented

2026-03-02 11:52:09 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Mar 29, 2025):

The new release will include a new env variable ASSETS_DIR that you can override to your liking and then mount a volume in that path. This will be available in the nightly build in 15mins.

@MohamedBassem commented on GitHub (Mar 29, 2025): The new release will include a new env variable `ASSETS_DIR` that you can override to your liking and then mount a volume in that path. This will be available in the nightly build in 15mins.

kerem commented

2026-03-02 11:52:09 +03:00

Author

Owner

@sdenike commented on GitHub (Mar 31, 2025):

The new release will include a new env variable ASSETS_DIR that you can override to your liking and then mount a volume in that path. This will be available in the nightly build in 15mins.

This is working great, thank you for the update! So far, everything looks to be working fine once I set the assets/ directory to my NAS location. Keep up the good work!

@sdenike commented on GitHub (Mar 31, 2025): > The new release will include a new env variable `ASSETS_DIR` that you can override to your liking and then mount a volume in that path. This will be available in the nightly build in 15mins. This is working great, thank you for the update! So far, everything looks to be working fine once I set the assets/ directory to my NAS location. Keep up the good work!

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/karakeep#716

No description provided.

Rows
Columns