-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bridging ArchiveBox #388
Comments
Excited to see this! It adds some logs to the fire under my butt to get that REST API pushed out 😆 In the meantime you can go one step further than just mocking out API requests as no-ops. If you're willing to have your REST API stubs call Python API functions imported from |
Thanks for the hints, it opened my mind and gave me new ideas! |
ArchiveBox is a powerful open-source web archiving tool that supports a wide range of archive formats, includes an administrative backend, and offers various other features. It performs well in archiving tasks, and Wayback aims to build upon it to provide even richer functionality.
Our plan is to utilize ArchiveBox as an additional backend for requesting archiving through an REST API. Unfortunately, ArchiveBox's API plan has not been implemented yet. To accomplish this particular feature, we will initially implement it by simulating web requests during the early stage. Once ArchiveBox's API plan is completed, we will further migrate to a REST API in a later stage.
The text was updated successfully, but these errors were encountered: