Long long ago before archivebox was a Django app, it used to be a one-shot bash script called archive-pocket-stream.sh. When we moved to the Django system archivebox oneshot was provided as an escape hatch for users that did not like being forced to create collections and manage data directories all of a sudden. It allows the new fancy django archivebox to run in "oneshot" mode without creating a main index file, data dir, etc. and only outputting the results of one snapshot into PWD.

As you might imagine, it required tremendous haxx to run the new Django archivebox without a db file in this way, including instantiating a fake sqlite3 db in memory, filesystem write filtering, etc. and it's imposing a large maintenance burden by making it hard to refactor other subsystems.

Now that we have solidly been on Django for several major versions, I think we can safely retire archivebox oneshot ?

Iif anyone is using it, speak up now and make a case for keeping it 😅 🤠👋