-
-
Notifications
You must be signed in to change notification settings - Fork 803
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
Add stash scraper type #269
Conversation
Performers scrape seem to work ok. For the scenes i found the following from a quick test
|
Note that the current implementation does not overwrite fields if they are already populated. |
that might explain the title .... but the url and rating were definetely blank on the test i did.. |
URL should now be populating correctly. Rating was left off intentionally as I didn't think it should be included by default. In future, I think we should show the difference between the current and scraped values and allow the user to set accordingly. The IDs of performers, studio and tags should never have been returned by the scrape, as they will seldom match between instances, and the local stash sets the IDs explicitly after matching them. This has now been fixed. |
URL is ok now A small bug left... |
Can we have the system programmatically generate a clean demo config so that the end-users always have the most accurate example in their installs? |
Everything seems fine now ... @Leopere the config for this PR is an extra file like this ~/.stash/scrapers/stash.yml , it doesn't change anything for the main config file |
* Add stash scraper type * Add graphql client to vendor * Embed stash credentials in URL * Fill URL from scraped scene * Nil IDs returned from remote stash * Nil check
Adds stash as a scraper type. This allows one to scrape performer and scene metadata from another remote stash instance.
Here is an example yaml config for a stash scraper:
Allows searching performer by name and scene by fragment.
sceneByFragment
is implemented by searching by scene checksum.