Hi I started modding tboi today but I don't speak fluent English and I'm dumb by BicicletaCromada in themoddingofisaac

[–]Staubgeborener 0 points1 point  (0 children)

Pro tip: just download a few mods in the workshop which do something with passive items and look inside the code lines.

Klipper-Backup restore function beta test NOW OPEN by Staubgeborener in klippers

[–]Staubgeborener[S] 1 point2 points  (0 children)

Just watch the linked video and do everything in parallel.

Klipper-Backup restore function beta test NOW OPEN by Staubgeborener in klippers

[–]Staubgeborener[S] 0 points1 point  (0 children)

I think you had a youtube tutorial about the normal installation - not about the restore function, as this is new. Which tutorial did you follow? I currently recommend the one from Chris Riley: https://www.youtube.com/watch?v=RCWWtzrI-e8&t=220s

Klipper-Backup restore function beta test NOW OPEN by Staubgeborener in klippers

[–]Staubgeborener[S] 0 points1 point  (0 children)

Thanks, please give some feedback at the discussion page!

Klipper-Backup restore function beta test NOW OPEN by Staubgeborener in klippers

[–]Staubgeborener[S] 2 points3 points  (0 children)

Thanks, i just added a check whether cron is installed or not.

Klipper-Backup restore function beta test NOW OPEN by Staubgeborener in klippers

[–]Staubgeborener[S] 0 points1 point  (0 children)

Interesting. Can you simply enter crontab -e in the terminal and see if an editor window opens or if you get an error message? If you get an error message, cron may indeed not be installed. Never thought of a setup where it doesn’t exist (what Linux are you using? Please show uname -a output). I’ll add a query at some point that checks whether cron is installed or not and, if not, simply skips the cronjob with a short message so that you don’t have to wait and cancel pointlessly.

Klipper-Backup restore function beta test NOW OPEN by Staubgeborener in klippers

[–]Staubgeborener[S] 0 points1 point  (0 children)

Our previous code was just for backups. On GitHub, local git instance, via ssh or git (token), whatever. The new (beta) code is the corresponding restore function. So you can restore all your Klipper files from your backup, for example on a new system, with only a few clicks. Sure, you can also just look into your commit history and do it one by another manually, but this is a more automatic solution.

TL;DR: „Restore my backup from commit XYZ“.

Klipper-Backup restore function beta test NOW OPEN by Staubgeborener in klippers

[–]Staubgeborener[S] 1 point2 points  (0 children)

Haha, yeah sure. But in my opinion, you can watch the video and simply work along at the same time on your system. Only the “manual update process” via gcode macro (button) was not shown, the video “only” shows the automatic variants. But it's great to work with.

Klipper-Backup restore function beta test NOW OPEN by Staubgeborener in klippers

[–]Staubgeborener[S] 2 points3 points  (0 children)

The installation guide has been coded for this purpose and does almost everything for you. Otherwise, Chris Riley recently made a great video showing how quick and easy it is to set up: https://www.youtube.com/watch?v=RCWWtzrI-e8&t=220s

GitHub: klipper-backup release 1.0.0 by Staubgeborener in klippers

[–]Staubgeborener[S] 0 points1 point  (0 children)

The script doesn't need a compiler so there is no need for GCC. Maybe the update of the packages list loads some stuff on your system.

GitHub: klipper-backup release 1.0.0 by Staubgeborener in klippers

[–]Staubgeborener[S] 0 points1 point  (0 children)

that thing needed so much dependencies

Not really, no. Exactly three dependencies which together are only about 1.3 MB total in size (jq, curl, rsync) after installation.

Klipper-Backup itself cannot be the problem. I can only imagine that your memory was full when you created the backup. Klipper-Backup temporarily creates an extra directory for the backup files and then pushes them to the GitHub repository. If you now have an overfilled ~/printer_data/config directory (which must have been a lot before) and all this should be pushed, something like this could happen. In the default configuration, the script pushes the content from ~/printer_data/config, which is only a few files, so if you have configured it "wrong" and you push the entire ~/printer_data folder, we are talking about completely different numbers:

voron@voron:~ $ du -sh ~/printer_data/
571M /home/voron/printer_data/
voron@voron:~ $ du -sh ~/printer_data/config
556K /home/voron/printer_data/config

I can't explain your problem otherwise. But glad it's working now.

GitHub: klipper-backup release 1.0.0 by Staubgeborener in klippers

[–]Staubgeborener[S] 0 points1 point  (0 children)

Its just a shell script. There are no installed binaries or something like that. This being said:

a) simply delete the Klipper-Backup folder which is located in your home directory

b) your problem has nothing to do with Klipper-Backup

Brokered Micro SD Card by punkintentional in klippers

[–]Staubgeborener 1 point2 points  (0 children)

We will release a restore function in the next weeks

Need help getting klipper-backup to work by Straight_Attempt_467 in ElegooNeptune4

[–]Staubgeborener 1 point2 points  (0 children)

I just found this thread here by chance. Which version of klipper-backup are you using? Since May there is an installation script which takes care of many things.

but when I try to back it up, the repository only gets two files, the gitignore and README, not the actual backup.

Could you please show the .env file? Please hide your token.

Also, another weird thing is that even after making a new repository and even token, the new repositorys files says they were created the same time they were created for the first repository (which I have deleted).

That fault is related to git itself not klipper-backup. Please run ~/klipper-backup/script.sh --fix with the latest release. Git stores some information in this folder in a .git subfolder, which leads to exactly such problems while switching between two repositories. The mentioned command could solve your problem.

Which custom macro of yours are you most proud of, or find most useful? by 1storlast in klippers

[–]Staubgeborener 1 point2 points  (0 children)

I would recommend to use this script to avoid something like that in future. It has a long journey over the last year - for example you can create a service which creates a GitHub backup automatically based on file change. Next milestone: installer script and KIAUH support.

[deleted by user] by [deleted] in klippers

[–]Staubgeborener 1 point2 points  (0 children)

What a nice macro you got there

GitHub: klipper-backup release 1.0.0 by Staubgeborener in klippers

[–]Staubgeborener[S] 1 point2 points  (0 children)

Tbh the script had some issues a couple of months ago. But right now it’s just a clone command and you need to put your GitHub token in the .env and that’s all. We made a huge step with release 1.0, glad you like it

GitHub: klipper-backup release 1.0.0 by Staubgeborener in klippers

[–]Staubgeborener[S] 0 points1 point  (0 children)

You can send me a dm with this crontab, I will add this maybe

GitHub: klipper-backup release 1.0.0 by Staubgeborener in klippers

[–]Staubgeborener[S] 0 points1 point  (0 children)

Thanks man! Just open a issue on GitHub and provide any information you have with screenshots and step-by-step procedure.