mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #263] Bugfix: ArchiveBox ignoring config values via environment variable and ArchiveBox.conf #1697
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#1697
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 @LaserWires on GitHub (Sep 6, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/263
Downloading sites without enforcing SSL verification doesen't function
does not permit user to download from site with outdated or incorrectly setup certificates.
ArchiveBox.conf.default.txt
Aliasing in ~/.bashrc did not resolve the issue with ArchiveBox SSL verification.
@LaserWires commented on GitHub (Sep 10, 2019):
CHECK_SSL_VALIDITY malfunctions regardless of file location.
It only downloads sites with SSL issues when line in archivebox/config.py
is modified
@pirate commented on GitHub (Sep 19, 2019):
Can you verify that the environment variable is actually making it to archivebox by adding a line that line to print:
Or by running
archivebox config --get=CHECK_SSL_VALIDITY.@LaserWires commented on GitHub (Sep 19, 2019):
Outputs CHECK_SSL_VALIDITY= UNSET
This is likely identical culprit to bug https://github.com/pirate/ArchiveBox/issues/268
@pirate commented on GitHub (Sep 19, 2019):
Going to close the other issue and rename this one, since it seems to be a generic issue with config handling.
@pirate commented on GitHub (Sep 19, 2019):
Do you mind posting the full output of
archivebox versionandarchivebox config, and the exact command you're using to run archivebox.@LaserWires commented on GitHub (Sep 19, 2019):
From git
git clone https://github.com/pirate/ArchiveBoxConfig files are identical
To archive
./archive http://www.site-to-archive.com@pirate commented on GitHub (Sep 19, 2019):
Ah I thought you were running the v0.4 branch. The current version on master actually doesn't support config files at all, it's all done via environment variables, so you'd have to source your config file before running the command manually.
Can you confirm that that outputs
falsebefore archivebox starts.@LaserWires commented on GitHub (Sep 19, 2019):
There is no issue any longer, setting environment variables works really well including for disabling media downloads.
Would be nice to define link depth and media specific objects.