Open karaolidis opened 3 months ago
Just had a read through #1, I think adding an option to specify the behavior when a file doesn't exist might be a good call?
I'm actually hitting an issue related to this behavior: a lot of software seems to replace symlink with raw files preventing those from being stored at all.
I could really use an option to specify the default content of the file if it doesn't exist in either place so it is ALWAYS bind-mounted.
Another option would be to create a oneshot .service
triggered by a PathExists=
to move the file into /persist
and create bind mount as soon as it appears for the first time.
The
README
says: "If the file exists in persistent storage, it will be bind mounted to the target path; otherwise it will be symlinked."Is there a specific reason for this behavior that I am missing out on? In my use case, some files spot the broken symlink, delete it, and replace it with their own file that ends up not being persisted. Wouldn't it make more sense to do:
Instead of:
I can open a PR if so :)
Thanks.