Nick Sweeting

In docker you don't need to run `--setup`, `docker-compose run archivebox init` is enough.

I'm actually going to re-open this because this issue shouldn't happen even in docker, it's a sign that there's a `b'...'` or missing `.decode()` somewhere.

It's pretty difficult, but not impossible, there are a lot of `/relative` urls all over the codebase. A bunch are in the static html too, so it's hard to change...

Reopening because I do want to allow this to be done eventually when I have time, it just probably wont be done anytime soon.

Doing this breaks a surprising amount of things because of how relative paths are written statically to the filesystem in the index.json/html files. It's fixable with rewriting in a Django...

`archivebox schedule --every=hour https://twitter.com/...` `archivebox schedule --every=day --depth=1 https://twitter.com/...` `archivebox schedule --help` You'll have to try it and see, I don't know the answers for that kind of scale.

Inspired by https://github.com/aurelg/linkbak I've had this on my mind for a while since it's super easy to implement, but @aurelg inspired me to actually make an issue for it.

I think I can fix the parallel process stdout multiplexing problem with one of two solutions: - a program like [curtsies](https://github.com/bpython/curtsies) two show each stream in a grid, tail -f...

It's not an issue of overloading archivebox, it's an issue of overloading / hitting rate-limits on the content servers, which piping through a proxy wont solve.

A quick update for everyone watching this, v0.5.0 is going to be released soon with improvements to how ArchiveResults are stored (we moved them into the SqliteDB). This was a...