The script doesn't upload any of the conifg files

[Voron-Switchwire]

Code of Conduct

• I promise that i have used markdown syntax to make the code more readable which helps to fix the problem and that I have tested the --fix command mentioned above without success.

What happened

I install klipper-backup according to the documentation. At first, it worked, but after I had some difficulties trying to get the autoupdate to work, the script just deleted all the files from my GitHub repository. Since then, if tried to change the .env, uninstalled klipper-backup with kiauh and reinstall it with kiauh. With no success. I don't get, why klipper-backup doesn't see my config files?
I would appreciate any help!

What did you expect to happen

To get klipper-backup to recognize my files

How to reproduce

IDK

Debug

IDK

Additional information

No response

[Staubgeborener]

IDK why you wrote IDK everywhere. This makes it difficult to help.
First: Your old backup seems to be here, here and/or here.

Second: Please run ~/klipper-backup/script.sh --debug as explained in the issue template and post the output (with markdown syntax).

Third: Did you really run ~/klipper-backup/script.sh --fix? Show the output.

difficulties trying to get the autoupdate to work

Which "autoupdate" exactly? We offer different ones from systemd services to cronjobs. A link to the specific doc is enough.

It's hard to figure out what you did with such vague information. It sounds to me as if you have changed and overwritten your paths in the .env file several times to address other paths for the backup (that's what it looks like to me in your commit history) and because you actively deleted your “default path” in the .env, file, those data was not taken into the backup.

[Voron-Switchwire]

I had some issues with git. The there was a .git file in the config folder. Therefore, the script couldn't initialize the repository. After deleting it manually, it works like a charm. Thank you for your fast reply! Really appreciate your work!!

[Staubgeborener]

This is something that --fix does in the background, among other things. The parameter --fix deletes the config folder and thus the .git folder inside.

Most problems of this kind are caused by a misconfiguration of git, which is why the parameter was introduced (and is even mentioned in the issue template).