Nick Sweeting

With v0.6 released now we've taken another step towards the goal of using a message-passing architecture to fully support parallel archiving. v0.6 moves that last bit of ArchiveResult state into...

@1105420698, allocating more than 1 cpu is definitely still advised, as django will use all available cores to handle incoming requests in parallel, and a few of the extractors already...

Ok I'm pretty set on using Huey at this point for the job scheduler, it can use SQLite, it comes with a great django admin dashboard, and it supports nested...

It works better in some cases (fast SSDs) than others so it's still worth trying, shouldn't be dangerous to data integrity, it'll just lock up if it's on a slow...

Note I've added a new DB/filesystem troubleshooting area to the wiki that may help people arriving here from Google: https://github.com/ArchiveBox/ArchiveBox/wiki/Upgrading-or-Merging-Archives#database-troubleshooting Contributions/suggestions welcome there.

Yeah this is definitely on our mind, it probably won't be added for a couple versions but this is definitely something I've been planning. It's blocked by adding a background...

Here's my proposed implementation of a new model to track scheduled imports: https://github.com/ArchiveBox/ArchiveBox/pull/707/files **Remaining TODOs:** - figure out which python scheduler to use - `huey` + [`django-huey-monitor`](https://github.com/boxine/django-huey-monitor) (my current favorite)...

Maybe we can fix it with a symlink shim created in the Dockerfile that points `/usr/bin/chromium-browser` -> `/usr/bin/chromium`?

🤷 No idea, if you're able to reproduce the ignoring of the CLI arg with bare SingleFile, want to open an issue over on their repo https://github.com/gildas-lormeau/SingleFile/issues? I'm not too...

`docker-compose exec archivebox ln -s /usr/bin/chromium /usr/bin/chromium-browser` for now until I add a fix to the Dockerfile later.