Provide a screenshot and describe the bug
Previously the archive directory in the data dir was used for the stored archives and everything archive wise was contained in that directory. This made things like backups and using this behaviour along side individual mount points within Docker to enable using remote storage for the captured archives. Also worked well with enabling integration of other tools for indexing and archive viewing such as pywb.
The new behaviour of linking to a directory outside the archive directory will break a lot of workflows and makes it harder to using external storage such as a mounted S3 bucket for the bulky archives, while retaining minimal container host file system and storage impact and making backups etc easier..
Can I suggest flipping the logic for the creation of the archive folders so links go into the archive directory and not out. It will also also make it easier to deal with existing archives, and keeps the captured archives in one place so it can be handled easier with external storage or for backups.
Steps to reproduce
Logs or errors
ArchiveBox Version
How did you install the version of ArchiveBox you are using?
Docker (or Podman/LXC/K8s/TrueNAS/Proxmox/etc)
What operating system are you running on?
Linux (Ubuntu/Debian/Arch/Alpine/etc.)
What type of drive are you using to store your ArchiveBox data?
Docker Compose Configuration
ArchiveBox Configuration
Provide a screenshot and describe the bug
Previously the archive directory in the data dir was used for the stored archives and everything archive wise was contained in that directory. This made things like backups and using this behaviour along side individual mount points within Docker to enable using remote storage for the captured archives. Also worked well with enabling integration of other tools for indexing and archive viewing such as pywb.
The new behaviour of linking to a directory outside the archive directory will break a lot of workflows and makes it harder to using external storage such as a mounted S3 bucket for the bulky archives, while retaining minimal container host file system and storage impact and making backups etc easier..
Can I suggest flipping the logic for the creation of the archive folders so links go into the archive directory and not out. It will also also make it easier to deal with existing archives, and keeps the captured archives in one place so it can be handled easier with external storage or for backups.
Steps to reproduce
Logs or errors
ArchiveBox Version
How did you install the version of ArchiveBox you are using?
Docker (or Podman/LXC/K8s/TrueNAS/Proxmox/etc)
What operating system are you running on?
Linux (Ubuntu/Debian/Arch/Alpine/etc.)
What type of drive are you using to store your ArchiveBox data?
data/is on a local SSD or NVMe drivedata/is on a spinning hard drive or external USB drivedata/is on a network mount (e.g. NFS/SMB/Ceph/GlusterFS/etc.)data/is on a FUSE mount (e.g. SSHFS/RClone/S3/B2/Google Drive/Dropbox/etc.)Docker Compose Configuration
ArchiveBox Configuration