![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/ee634f30-7b97-424e-93bb-47945757fddc.png)
Wouldn’t that be a pain to maintain?
Wouldn’t that be a pain to maintain?
Not for the same resilience as in glacier, it is pretty price effective.
That would be most helpful, thanks 🙏
I mean going fronm docker compose to a k8s setup. The Docker compose version is no problem.
Cloud key Gen 2 Plus is about $200 and comes with a 2.5 inch 1TB hard drive so it is not that bad if you will have multiple cameras, but maybe not worth it just for one.
I had the same problem, had to use a different keyboard then it worked with F10.
NAS with Truenas, built myself:
And the following in a VM with docker compose:
Separate K8s cluster with Single control pane (2nd hand old small form-factor HP stuff) and 3 Nodes to run more resource intensive stuff that doesn’t need to be close to the data source:
HomeAssistant in another 2nd hand HP small form factor box
No, in a linux VM that then has a docker running in it.
I had the same problem, sorry to say i had to run it in a Linux Docker container instead to get it to work optimally.
Lovely dashboard, like that it is so easy to use. But, am I missing something with just having a folder with links to my services? It is searchable, portable (Firefox profiles), and easy to modify.
Sharing PVC’s seems like an anti pattern. My suggestion would be to share storage by having network storage instead like a NAS and share that with the same user in all Deployments. Generally for each *arr you need a /data and a /config so the data should be same location in the shared network solution. Check out https://hotio.dev/ for ready solutions which you only need to supply with the storage basically. Default settings works for me.