mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-26 01:26:00 +03:00
[GH-ISSUE #94] Configurable Output Directory #68
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#68
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 @pigmonkey on GitHub (Sep 14, 2018).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/94
I want bookmark-archiver to place its output in a directory I specify, not the default
output/directory in the repository. To do this I replaced theOUTPUT_DIRvariable inconfig.pywith a check for an environment variable and a fallback to the current default. This matches the rest of the configuration options and works great for me.I'm happy to submit a pull request with this, but I'm curious if there was some reason this was not already the default config. Does this break something I haven't considered?
@pirate commented on GitHub (Sep 20, 2018):
I was originally intending on adding paid multi-user support which would include multiple custom output directories, (so people could host a federated collection of archives all managed together for their community), but given how little time I have these days I think it's about time to enable custom output folders and let people do it themselves.
Feel free to submit that PR and I'll accept it, otherwise I can add this line myself.