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

sync cache #2930

Open
jampy opened this issue Jan 17, 2025 · 2 comments
Open

sync cache #2930

jampy opened this issue Jan 17, 2025 · 2 comments
Labels
kind/feature New feature or feature request

Comments

@jampy
Copy link

jampy commented Jan 17, 2025

I'm using devspace dev extensively during development. Since my repository is rather large, the initial sync takes some time and also transfers a lot of data. I like to devspace purge quite often (especially when switching branches) in order to have a clean working environment.

dev:app sync  Upstream - Upload 4910 create change(s) (Uncompressed ~115253.59 KB)

Of course, most of these files do not change that often - especially not the large ones.

I was wondering if there is some way that the devspace sync process might use a persistent volume (that survives a purge) to cache these files remotely, avoiding the need for repeated transfer of the same data over and over again.

Or perhaps you can suggest some trick?

Thanks,!

@jampy jampy added the kind/feature New feature or feature request label Jan 17, 2025
@zerbitx
Copy link
Collaborator

zerbitx commented Jan 24, 2025

Have you tried configuring the persistence options?

@jampy
Copy link
Author

jampy commented Feb 10, 2025

Have you tried configuring the persistence options?

No, because I assume that this will persist the files even if I do a devspace purge and that's not what I'm looking for.

I regularly do devspace purge folowed by devspace dev to make sure I have a clean, deterministic environment, especially when switching git branches.

Also I mostly use one-way sync.

Or are you suggesting some trick I'm not seeing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or feature request
Projects
None yet
Development

No branches or pull requests

2 participants