Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help with cloud sync and Straight : whats the LEAST I need to sync to minimise traffic? #1133

Open
rileyrg opened this issue Nov 28, 2023 · 1 comment
Labels

Comments

@rileyrg
Copy link

rileyrg commented Nov 28, 2023

I'm using rclone/syncrclone to back up my Linux configs and apps. One of which is my emacs config which features a pretty standard straight directory.

My syncing is very very slow over sftp and I would like to minimise what goes over the wire : if I can only sync meta files which tells emacs/straight what to do on the other end of the sync all the better. So - ideally I would not sync repos and build, but rather only default.el? Or would I need to also sync modfied? Example:

eg suppose on laptop 1 I do a git pull and restart emacs - straight rebuilds loads of packages that the pull updated. Whats the least I can sync to the cloud to then be pulled down onto laptop B that will tell straight to also pull these packages and rebuild? Can that happen? Or MUST I sync the straight/repos directory, default.el and then straight will notice build is out of sync with repos and do the build ? Note that we can assume both laptops have the same emacs build installed at least.

Hopefully this is clear if not, ring the bell ;)

@rileyrg rileyrg changed the title Help with cloud sync and Straight : whats the LEAST I need to syncto minimise traffic? Help with cloud sync and Straight : whats the LEAST I need to sync to minimise traffic? Nov 28, 2023
@progfolio
Copy link
Contributor

You should only need your init file and any lockfiles in use to reproduce your setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants