You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Loving the idea and approach, have been trying to find something for this purpose for a number of years.
Now it may because of the shear size of my libraries but I'm finding that if the script hits any errors it goes back to the beginning of the first library and with a big library this not ideal.
I think a some form of resume point tracking would be good.
Also currently it seems to replace all items on every run which again in a large library is a heavy on disk and if you happen to be replicating the library to other nodes (resilio sync), hits the network as well.
The text was updated successfully, but these errors were encountered:
Thanks for your thoughts. Unfortunately, I'm not using plex at the moment and do not have plans to extend the exporter. However, feel free to fork the repo and adjust the code ;)
Cool, I'll take a look at using axios-retry as a first step. I'll also look to sprinkle a bit of git action magic to automate build (including amd64 and arm64) and upload to dockerhub based on secrets (that way I can test but if you want to adopt you can accept the PR and create the relevant secrets for you existing account.
Loving the idea and approach, have been trying to find something for this purpose for a number of years.
Now it may because of the shear size of my libraries but I'm finding that if the script hits any errors it goes back to the beginning of the first library and with a big library this not ideal.
I think a some form of resume point tracking would be good.
Also currently it seems to replace all items on every run which again in a large library is a heavy on disk and if you happen to be replicating the library to other nodes (resilio sync), hits the network as well.
The text was updated successfully, but these errors were encountered: