![Avatar](/_next/image?url=%2Flemmy-icon-96x96.webp&w=3840&q=75)
ShortN0te
Use unit files and add on failure a notification per mail or whatever.
You still should test the backups periodically.
Oh yeah, sorry i know. Was too lazy to type it out. They number the created compose files in numbered directories instead of naming it after the stack.
The problem is, that they do not support at all the direct modification of those files and the abstraction of numbering them instead of giving them real names is annoying when you want to start them via cli.
I used portainer only as fancy docker dashboard and to start stop services. It was buggy and even with the git implementation really frustrating to use. Also that they do not store the compose files is simply not ok.
Dockge fully replaced portainer for my needs.
I recommend, reading the release changelogs actively. For most services you can just put the github release page in an RSS reader to get a notification when a new release hits, so you can quickly look for any breaking changes, also this will give you info about new features.
I have been using watchtower for a few years. No problems with auto updates so far, but keep your backup handy.