mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #1025] Enhancement: Add WGET_EXTRA_ARGS, CURL_EXTRA_ARGS, SINGLEFILE_EXTRA_ARGS to extend default args without overriding defaults #2150
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#2150
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 @ntevenhere on GitHub (Sep 12, 2022).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1025
These
WGET_ARGS,CURL_ARGS, etc. options let the user shoot themselves in the foot, silently. I think the documentation or the variables themselves should be changed to be more ergonomic.Did you need to add a header to wget?
Look at this configuration, it looks inoffensive. Checking the documention, nothing ticks you off you're using it wrong. But no.
After this, your 🆆 button won't take you to the main html you archived, and wget archives things slighlty differently, silently.
Why? By setting WGET_ARGS you overwrote vital settings, as it turns out they're also stored in WGET_ARGS. The documentation doesn't tell you about this. This happened to me, I just happily overwrote the variable. When I should've written something like this:
Proposal:
*_ARGSshould have a good warning or display the default value, so that users can suspect they're overwriting something.EXTRA_WGET_ARGS,EXTRA_CURL_ARGS, and so on. These won't overwrite the now-considered low-level*_ARGS.EXTRA_*_ARGSshall be the more user-facing option and more promoted in the documentation.@pirate commented on GitHub (Sep 28, 2022):
I'm ok with the EXTRA_ options as I want users to be able to override the defaults.