Replies: 1 comment
-
Just wanna say great job on this! I've got an extremely large archive (28k links or so, mostly pulled from Pocket), and I've been intermittently running I upgraded to 0.6.0 the other day and ran |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
New features
Re-snapshot
buttoninit --quick
andserver --quick-init
options to quickly update the db version without doing a full re-init (for users with large archive collections this will make version upgrades a lot faster / less painful)archivebox setup
command andarchivebox init --setup
flag to aid in automatically installing dependencies and creating a superuser during initial setupSNAPSHOTS_PER_PAGE=40
andMEDIA_MAX_SIZE=750m
config options#hash
e.g./archive/<timestamp>/index.html#git
/archive/https://example.com/some/url
-> redirects to ->/archive/<timestamp>/index.html
(also works without scheme/archive/example.com
)archivebox add --tag=tag1,tag2,tag3 ...
CUSTOM_TEMPLATES_DIR
Enhancements
data/logs/errors.log
file (so users no longer have to run in --debug mode to see error details)archivebox schedule
logging and changed logfile location to./logs/schedule.log
docker-compose.yml
djdt_flamegraph
for developers to profile UI performance--overwrite
flag support toarchivebox schedule
, archived urls get added similarly toadd --overwrite
SEARCH_BACKEND_TIMEOUT
config option to tune amount of time search backend can take before it gives upBugfixes
AssertionError
error when archivebox would to attempt archive withCHROME_BINARY=None
when Chrome was not found on host systemThis discussion was created from the release v0.6.0: Major performance improvements, new ArchiveResult admin UI, ability to tag URLs while adding them, and better URL handling.
Beta Was this translation helpful? Give feedback.
All reactions