This is my entire use case, I need to be able to do single page snapshots on a daily basis, and have no need for any of the other functionality of ArchiveBox, I'll be running it CLI only, and using another tool to trigger the daily snapshots of the pages, and piping them into specific directories.

Without the ability to create multiple snapshots of the same URL in your normal use cases, this is the only way I can achieve it.

Good to know! Would your needs be satisfied if we add better native support for multiple snapshots in archivebox instead of keeping this older feature? @ianrobertsFF

I'm also using this. I think it makes a lot of sense to keep a command like oneshot around because it's fairly self-contained, and it aligns well with the UNIX philosophy. It does one thing and it does it well, without the need for archive init and the use of the rest of the software. Please don't take it away.

My needs would be satisfied by multiple snapshots, although I still wouldn't be using any of the functionality that oneshot doesn't currently use, so it wouldn't be a better workflow, as oneshot does exactly what I need.

However assuming I can continue to take on-demand snapshots with the native support for multiple snapshots, this would be acceptable to me.

Q:
Would it be possible to fork this off into its own separate project/repo?
Would it even be desireable?

I appreciate @jvican ’s comments on this, and agree.

Ok I've decided to keep oneshot because it ties in nicely with the ongoing refactor to move ArchiveBox towards an event-driven job queue model. The old oneshot will be renamed and joined by a new command to run a single extractor method:

archivebox snapshot

Can be run to snapshot an individual URL into the current directory (runs all extractors by default).

archivebox snapshot --methods=all 'https://example.com/somepage.html'
# creates a subfolder for each extractor method, and an index.html and index.json file in $PWD

This works the same way as oneshot does now, and I'll alias oneshot to the new command so we don't break backwards compatibility.

archivebox extract

This runs an individual extractor method and outputs into the current directory.

archivebox extract --method=PDF --method-args-here 'https://example.com/somepage.html'
# writes output.pdf (and an index.json containing cmd+output for each run) into $PWD using the headless browser

After the refactor, archivebox add will work by internally enqueuing a job that runs archivebox snapshot ... for each imported URL.
The snapshot job then in turn enqueues a job for each extractor needed on that URL.
Each extractor job then runs archivebox extract --method=... internally to write the output into the final archive directory.

Please subscribe to this issue for updates: #1289