Klipper Backup #229
Replies: 10 comments 9 replies
|
What timezone are you? |
|
Basically, a very simple task, tracking your klipper config, is being offloaded to an outside package/repo, it's completely unnecessary. Begin by creating a repo on your github, can be public or private, called |
|
Is your klipper config working as it should at this point? |
|
|
Just the first page from this
|
|
Commit (save) your changes to your branchIt seems that the following files were modified and you're fine with how the settings are currently. # Stage all changes for commit.
git add --all
# Commit the changes
git commit -m "My klipper config is working as it should"Linking your settings to your repo# This will set your github repo as another remote available. `origin` is my repo, `myOrigin` is yours.
git remote add myOrigin https://github.com/FoxPhantomThief/klipper-config-SV06.git
# Make sure your branch is checked out.
git checkout my-settings
# Link your branch to `myOrigin` and push it to your repo. In the future, you can just do a `git push`
git push -u myOriginIn the future, when you make changes to your config, you can check the status, stage the changes, then commit, then push. |
|
Totally forgot about authentication. Many ways to tackle this, and of course it's easiest with linux. What OS is your |
|
On your klipper host, generate a very secure ssh key via Do not use a passphrase, unless you want to have to type it in every time. Just keep pressing enter and use defaults. View ssh Should be good to go. Something to note, if someone gets their hands on your klipper host, they will be push code to your github. |



Uh oh!
There was an error while loading. Please reload this page.
First off, I'd like to thank you for creating and maintaining this repo. Your extensive configurations and documentation have made it easy for newbies to get up and running with Klipper. I've been much happier with the performance of my SV06 since upgrading from Marlin using your instructions. So, thank you!
I'd like to backup my configuration using Klipper-Backup. The problem I'm running into is that the script fails because it attempts to include files in the backup repo that are already part of your repo. This manifests as ~/printer_data/config being treated as a symlink and nothing else being tracked. Could you offer any advice on a workaround, or perhaps provide instructions on how to get the backup functioning?
Thanks!
All reactions