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

Collection cache stores expanded filestorage path #1067

Open
tbrk opened this issue May 13, 2023 · 4 comments
Open

Collection cache stores expanded filestorage path #1067

tbrk opened this issue May 13, 2023 · 4 comments

Comments

@tbrk
Copy link

tbrk commented May 13, 2023

Thank you for such a useful and well thought out tool.

I use unison to synchronize a laptop running macOS (HOME=/Users/me) with a desktop running Linux (HOME=/home/me) and I want to be able to run vdirsyncer on either machine against the same set of files. In .vdirsyncer/config, I use ~ to abstract over the difference in the HOME directories, but unfortunately vdirsyncer discover expands ~ before caching the filestorage path. Would it please be possible to cache the unexpanded path and to expand in every vdirsyncer sync?

@WhyNotHugo
Copy link
Member

This should be doable. You're not running vdirsyncer on both devices, are you?

@WhyNotHugo
Copy link
Member

If you run it on both devices, and unison is running too, this might result in unison copying vdirsyncer's state file and leaving things in an inconsistent state.

@tbrk
Copy link
Author

tbrk commented May 14, 2023

My use case is as follows:

  1. Run vdirsyncer on the laptop while not at work.
  2. Run unison in the morning when I arrive at work.
  3. Run vdirsyncer on the desktop at work.
  4. Run unison in the evening before leaving work.

The idea is thus to run vdirsyncer on both devices, but never at the same time. Should this work?

@WhyNotHugo
Copy link
Member

Yeah, as long as vdirsyncer and unison never run at the same time you should be safe.

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

No branches or pull requests

2 participants