Closed wilmardo closed 3 years ago
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
Not stale.
With something like Sequelize it would be possible to maintain the current SQLite implementation as backwards compatible option.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
Still not stale though haha
+1 to this. But you mention a NAS - you could always mount the k8s container storage on a NFS shared drive. Or GlusterFS.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
I suppose there is still no support for external databases?
Same issue as https://github.com/Koenkk/zigbee2mqtt/issues/4947
As stated in the linked issue this would be a welcome addition for users who write on SD card like storage.
My usecase is a bit specific but nonetheless a bit of explanation. I am trying to get a stateless Zigbee2MQTT implementation so it can failover between Kubernetes nodes (external CC2530 TCP serial) without the need of a volume (since distributed storage is hard on low power devices). I am using Kubernetes configmaps for the configuration so only the
database.db
and thecoordinator_backup.json
are blocking a completely stateless approach. If these could be stored in an external database then the image can be run without a volume (stateless) which offloads the persistence to a NAS for example.