How to back up scripts with kit?

[jsjoeio]

I know ~/.kenv is a git repo. Let's say I wanted to back up my /scripts and/or /lib directory, what's the suggested approach for that?

[johnlindquist]

The app only runs the initial clone for the .kenv repo. After that, the end-user can do whatever they like. (Unlike the .kit repo where the App keeps it up-to-date by pulling tags) I'm strongly considering using "degit" for .kenv so the user can git init themselves. The user just needs to respect the directory conventions. Advanced usage: .kit can generate multiple .kenv dirs anywhere on your machine, although 99% of people will only use the App .kenv, it's totally possible to manage many other headless .kenvs.

…

On Sun, Mar 21, 2021 at 8:45 AM Joe Previte ***@***.***> wrote: I know ~/.kenv is a git repo. Let's say I wanted to back up my /scripts and/or /lib directory, what's the suggested approach for that? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#70>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAIZ2JZP475F34MSVBVHJDTEYA7TANCNFSM4ZRT6SYQ> .

[jsjoeio]

Ah, gotcha!

I'm strongly considering using "degit" for .kenv so the user can git init
themselves.

Yeah, this would help I think. I was confused because the .kenv is already git initialized so it threw me off and I wasn't sure if could point it to my own remote or something.

[jh3y]

I'm about to write up my experience with this 😃

TL;DR I set up a separate remote which worked great. But, there are a couple of quirks that I'm not sure about. But, I'm sure @johnlindquist will straighten me out with what I could be doing better 😄

[jsjoeio]

@jh3y Will you link the post back here when you do? 😄 It would definitely help to piggyback off your approach!

[jh3y]

Sure thing! I wrote about it in a separate thread: #71

Some good actionable things from John to improve it. Overall, awesome experience and makes my machine set up a doddle. I'll refine it further, the scripts are very "rough". But, I was able to test it on three machines and it worked a treat once I worked out the steps I needed.

[lannonbr]

As I'm thinking it will be nice to store my scripts to share between my computers & have them publicly accessible, I'm saving my ~/.kenv/scripts/ folder up to git: lannonbr/scriptkit-scripts.

The one thing I think I will need to easily sync things up between machines is make sure that all of the scripts have a related shell script within ~/.kenv/bin. I am digging through the code and would ~/.kit/cli/create-all-bins.js help solve this after doing git pull?

[johnlindquist]

Yup, "generate bins" is an option in the help menu. It runs that 👍

[lannonbr]

As a followup, I did end up using this and it works wonderfully:

// Menu: Sync Scripts
// Description: Pull from backup scripts git repo & create shell scripts for ones that don't have one yet
// Author: Benjamin Lannon
// Twitter: @lannonbr

exec('cd ~/.kenv/scripts && git pull origin main')
await cli('create-all-bins')

This doesn't resolve cleaning up ~/.kenv/bin of scripts that no longer exist, but this is good enough to be able to quickly pull down scripts and have them ready to be used either in the terminal or the prompt

[cfritze64]

any advice on the proper way to remove the ~/.kenv/lib directory from tracking so I can set up may own repo sync for ~/.kenv/lib ? Presently, If I got to the ~/.kenv/lib directory and "git remote -v" I see john's main scriptkit repo as origin. I'm loathe to mess with things, worried I'll upset the overall kit update structure.

[johnlindquist]

@cfritze64 An an early-adopter, you have a very old .kenv.

The app now removes all .git info from both the .kenv and the .kit. You can safely delete .kenv/.git

.kenv: Change whatever you'd like, just not the directory structure
.kit: Don't touch anything, the app will completely wipe that dir with each update

[cfritze64]

That's great. I thought that might be the case. Thanks for the clear answer.