starred/ArchiveBox

Fork 0

mirror of https://github.com/ArchiveBox/ArchiveBox.git synced 2026-04-26 01:26:00 +03:00

[GH-ISSUE #1150] How do I configure ArchiveBox to persist data on a NAS? #3735

New issue

Closed

opened 2026-03-15 00:13:38 +03:00 by kerem · 5 comments

kerem commented

2026-03-15 00:13:38 +03:00

Owner

Originally created by @omniowl on GitHub (May 18, 2023).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1150

I can see in the documentation it says:

Try to keep the index.sqlite3 file on local drive (not a network mount), and ideally on an SSD for maximum performance, however the archive/ folder can be on a network mount or spinning HDD.

That sounds great, but when I looked further I didn't seem to find anything suggesting how to achieve this? I'd love to have the sqlite database in my container to save on space and move everything that's archived to my NAS. How would I do that? Did I just miss that in the documentation?

Originally created by @omniowl on GitHub (May 18, 2023). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1150 I can see in the documentation it says: > Try to keep the index.sqlite3 file on local drive (not a network mount), and ideally on an SSD for maximum performance, however the archive/ folder can be on a network mount or spinning HDD. That sounds great, but when I looked further I didn't seem to find anything suggesting how to achieve this? I'd love to have the sqlite database in my container to save on space and move everything that's archived to my NAS. How would I do that? Did I just miss that in the documentation?

kerem

2026-03-15 00:13:38 +03:00

closed this issue
added the
status: needs followup
label

kerem commented

2026-03-15 00:13:54 +03:00

Author

Owner

@pirate commented on GitHub (May 19, 2023):

It's just a matter of mounting your NAS folder to the archive/ path, there's not really any setup beyond that required on the ArchiveBox side.

docker-compose.yml:


services:

  archivebox:
    ...
    volumes:
      - /path/to/your/SSD/archivebox:/data
      - /path/to/your/NAS/archivebox/archive:/data/archive

@pirate commented on GitHub (May 19, 2023): It's just a matter of mounting your NAS folder to the `archive/` path, there's not really any setup beyond that required on the ArchiveBox side. `docker-compose.yml`: ```yaml services: archivebox: ... volumes: - /path/to/your/SSD/archivebox:/data - /path/to/your/NAS/archivebox/archive:/data/archive ```

kerem commented

2026-03-15 00:13:59 +03:00

Author

Owner

@omniowl commented on GitHub (May 19, 2023):

The NAS is on my network separate from the container on a different subnet.
The host of the container is on the same subnet as the NAS though.
Is it still just a volumes line like that?

@omniowl commented on GitHub (May 19, 2023): The NAS is on my network separate from the container on a different subnet. The host of the container is on the same subnet as the NAS though. Is it still just a volumes line like that?

kerem commented

2026-03-15 00:14:04 +03:00

Author

Owner

@pirate commented on GitHub (May 19, 2023):

You need the mount the NAS to a local folder first, the instructions to do that vary wildly depending on you NAS, host OS, and network setup. You'll probably need to use SMB, NFS, SSHFS, SFTP or something similar to mount it.

To bridge separate subnets I recommend setting up Tailscale on your machine and the NAS (or use an SSH tunnel or some other similar VPN software).

@pirate commented on GitHub (May 19, 2023): You need the mount the NAS to a local folder first, the instructions to do that vary wildly depending on you NAS, host OS, and network setup. You'll probably need to use SMB, NFS, SSHFS, SFTP or something similar to mount it. To bridge separate subnets I recommend setting up Tailscale on your machine and the NAS (or use an SSH tunnel or some other similar VPN software).

kerem commented

2026-03-15 00:14:09 +03:00

Author

Owner

@omniowl commented on GitHub (May 19, 2023):

Hm, alright. I'll give it a try.

@omniowl commented on GitHub (May 19, 2023): Hm, alright. I'll give it a try.

kerem commented

2026-03-15 00:14:14 +03:00

Author

Owner

@pirate commented on GitHub (Jun 13, 2023):

Closing for now, but if you have any specific questions / issues you encounter during NAS setup, comment back here and I can reopen it.

@pirate commented on GitHub (Jun 13, 2023): Closing for now, but if you have any specific questions / issues you encounter during NAS setup, comment back here and I can reopen it.

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/ArchiveBox#3735

No description provided.

Rows
Columns