That would probably the best practice. But as another post said, I don't trust myself (and I lack the skills, although that's pretty lame excuse).
Which prosody docker image are you using and why?
cross-posted from: https://lemmy.ml/post/26615546
The official docker image is still at v0.11 and was last updated in 2016. It looks like maybe
trunkis at 0.12, but, as far as I can tell, that a rolling release. My prosody install is too important to go with a rolling release.Both the alternatives that they point to are similarly old;
- v0.11.13 --- https://github.com/OpusVL/prosody-docker/
- v0.11.x (?) --- https://github.com/unclev/prosody-docker-extended
My server is langishing on the unclev image. I'd like to migrate to something with 0.12 and have a bit more confidence in its resiliance.
Which prosody docker image are you using and why?
The official docker image is still at v0.11 and was last updated in 2016. It looks like maybe trunk is at 0.12, but, as far as I can tell, that a rolling release. My prosody install is too important to go with a rolling release.
Both the alternatives that they point to are similarly old;
- v0.11.13 --- https://github.com/OpusVL/prosody-docker/
- v0.11.x (?) --- https://github.com/unclev/prosody-docker-extended
My server is langishing on the unclev image. I'd like to migrate to something with 0.12 and have a bit more confidence in its resiliance.
I use newsboat as well, though often feel like giving up on rss too---just too much stuff coming in even after unsubscribing to lots.
I used this as a solid base. It's more flexible than the AIO containers. Annoying thing about NC is that, as far as I can tell, none of the LDAP settings are exposed as environmental variables.
This is the part that gets me. I don't know how to automate this. I periodically retrieve something from the backups, which, so far, has worked. That's not really good insurance, though. Any suggests or resources, ideally for borg and/restic?