Splitting API and zurg/zilean/decypharr scraping #94
Description
Hey @iPromKnight ,
Wanted to run an idea by you...
In reference to this warning:
Note: When doing this - ensure you have stopped Your api instance, as the scraper and the api scheduler scraping tasks will cause data corruption.
If I configured a Zilean instance without zurg/zilean scraping, and then a configured separate cronjobs which just ran the scraper (i.e., a different configuration file with the same database details), would I risk any corruption?
My usecase is that ElfHosted users now use a combination of Zurg or Decypharr, both of which have different ingestion endpoints, so I'm thinking the simplest fix is 2 dedicated scraper jobs, each with a different LabelSelector and ZurgEndpointSuffix value...
Cheers!
D