Documentation a bit...lacking? about cv4pve-autosnap HOT 9 CLOSED

Sorry was super busy yesterday and today, got hit with an emergency project, I'll get on it tomorrow 100%

I found the problem actually! [image: Screenshot 2021-04-28 143042.png] So the issue was the api token format wasnt clear, I set AUTOSNAPSHOT@PVE!BACKUPS!Tokenid=asdfghjkl-1234568799-qwertytuyi instead of the correct way which is ***@***.***!backups=asdfghjkl-1234568799-qwertytuyi With the Equals there I thought it was like a tokenid=apikey instead of the literal meaning of backups(tokenid)=1234568799-qwertytuyi(api token) so I just added an exclamation point to it. So yeah the instructions werent terribly clear, but i did figure it out this time. my recommendation would be to just be a tid bit more verbose on the installation bit. Also when you put that information in wrong it completely critically error's the application out so you need to use a snapshot to restore it to its pre-saved state. Restoring from your internal restore system does not fix it. you have to completely remove the docker container and rebuild the system to do it in any short order. Also:  The IP address and the IPMI address...there should be a note above it pointing out that it's for proxmox. I was confused about the IPMI as technically the cv4-pvetools is an ipmi...it manages and monitors the proxmox backups...so you can understand my confusion there. I actually kind of just guessed this time. outside of that  I know you have "login toolbox" above that however, might I recommend bolding those "login" portions to highlight that it's a section and you don't need the toolbox ssh? I thought this was a much bigger problem than I was having and I do apologise for causing a stir, however small usability changes that I have recommended could possibly stop this from happening in the future.