[GH-ISSUE #283] ArchiveBox shows the wrong output path when run from a different directory than the binary #202

New issue

Closed

opened 2026-03-01 14:41:30 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 14:41:30 +03:00

Owner

Originally created by @Julian on GitHub (Oct 13, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/283

When running e.g. cd Desktop; /path/to/archivebox/archive foo.html, archivebox shows:

[X] [2019-10-13 19:18:51] Downloading paused on link 1563727241.19 (37/2834)
    To view your archive, open: output/index.html
    Continue where you left off by running:
        archive 1563727241.19

when exiting the process, but output there is actually seemingly by default relative to the archive binary, not the working directory.

Software versions

OS: macos
ArchiveBox version: eb641b3
Python version: pypy3 (3.6.1)

Originally created by @Julian on GitHub (Oct 13, 2019). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/283 When running e.g. `cd Desktop; /path/to/archivebox/archive foo.html`, archivebox shows: ``` [X] [2019-10-13 19:18:51] Downloading paused on link 1563727241.19 (37/2834) To view your archive, open: output/index.html Continue where you left off by running: archive 1563727241.19 ``` when exiting the process, but `output` there is actually seemingly by default relative to the archive binary, not the working directory. #### Software versions - OS: macos - ArchiveBox version: eb641b3 - Python version: pypy3 (3.6.1)

kerem closed this issue

2026-03-01 14:41:30 +03:00

kerem commented

2026-03-01 14:41:31 +03:00

Author

Owner

@pirate commented on GitHub (Oct 17, 2019):

Thanks for reporting! The whole model of where the data folder is stored changes in >=v0.4. archivebox becomes a command that can be globally installed on the whole system with pip install archivebox, then whatever folder it's run in becomes the data folder.

e.g.

mkdir ~/archivebox && cd ~/archivebox
archivebox init
...

The v0.4 release is blocked by a few security issues, but once it lands you can pip install and you'll find this issue is fixed.

@pirate commented on GitHub (Oct 17, 2019): Thanks for reporting! The whole model of where the data folder is stored changes in `>=v0.4`. `archivebox` becomes a command that can be globally installed on the whole system with `pip install archivebox`, then whatever folder it's run in becomes the data folder. e.g. ```bash mkdir ~/archivebox && cd ~/archivebox archivebox init ... ``` The v0.4 release is blocked by a few security issues, but once it lands you can `pip install` and you'll find this issue is fixed.

kerem referenced this issue

2026-03-01 17:52:31 +03:00

[GH-ISSUE #202] Windows Docker error on resuming archiving process #1647

kerem referenced this issue

2026-03-14 21:21:30 +03:00

[GH-ISSUE #202] Windows Docker error on resuming archiving process #3158

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#202

No description provided.

Rows
Columns