mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #1039] ARCHIVE_DIR and SOURCES_DIR #653
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#653
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @lx30011 on GitHub (Oct 26, 2022).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1039
Hello, I would like to use archivebox and store all the data to a network share.
I thought about running archivebox directly on the network share mount but this isn't a good idea because of the sqlite database. So I want to store everything apart from the sqlite database on the network share. The sqlite database I'm going to fetch periodically from my network share.
Is there any way to edit ARCHIVE_DIR and SOURCES_DIR to point to my mounted network share?
Also do these two folders cover all the important data apart apart from the sqlite database or is there anything else I missed?
Sorry if my question is stupid. I find it difficult to make sense of archivebox.
@lx30011 commented on GitHub (Oct 26, 2022):
I forgot about symlinks. That works for me.
@pirate commented on GitHub (Nov 1, 2022):
Yeah we used to allow editing ARCHIVE_DIR and SOURCES_DIR but it's a lot of work to support having those mutable so symlinks are the best way. 👍
There's lots of details on how to run on network shares spread around the wiki too.
@Dontkickmi22 commented on GitHub (Mar 22, 2023):
Well, I got a really stupid question for ya, hope you don't mind.
Same boat here, but no luck with symlink. Care to share how it's done?
Below is what I got, gives me FileExistsError: [Errno 17] File exists: '/data/archive'
Really appreciated any help
@pirate commented on GitHub (Mar 23, 2023):
Can you post the output of
ls -lah /mnt/nas/archivebox/archive@Dontkickmi22 commented on GitHub (Mar 24, 2023):
Really appreciated.
Battled with chown, but a restart reverts back, at the end I changed my mind and allowed it. :-)