What really is a swear word?
The drivers should make up new words, repeat them, use them in anger often. Encourage others around them to join in.
We need a 2025 New Swear Word Awards!
CodeMonkeyUK
joined 2 years ago
That too, but no, I was referring to the data/config folders for each container.
For example, radarr it would be the config volume you mounted. Generally, the *arrs use a volume called 'config', but other containers will differ.
I've only had to recover from backups twice in 5 years, once was my fault after fiddling with databases. But if you're using the development/nightly branches, it's best to be cautious and avoid having to reconfigure.
Cannot recommend container approach enough. The learning curve isn't too bad, initially it can be daunting but best way is to jump straight in and try it.
Few things I recommend:
- Portainer, a very nice container management webapp
- Use compose /stack from day 1, or at least try it before you get carried away with too many containers. Take a copy and save somewhere and build up your catalogue of containers/configs.
- Volumes, make sure they are persistent.
- Backup your docker config folders, especially if using development branches.
- Spend a day/weekend playing with setup, expecting to throw away and start again. Sounds bad but it's not. If you use compose/stacks you can spin up in seconds.
Same here...
Underpowered server is what I suspect. It's taking too long to extract subtitles that it times out. Subsequent requests will work as the result is cached once it eventually finishes.
My workaround was to use external subtitles to remove the need to extract. If you're using the *arrs checkout bazarr.
Removed the red paint to go faster?
Works for me. Possibly issue if you don't have a handler/app that it can open with?