You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2019. It is now read-only.
I don't completely understand how to get unison to work at boot time. I'm trying to keep my source folder syncing from local to container. When container starts, it expects the source to be there already. README suggests and my quick test confirms, that upon boot of the container, /unison is empty and needs to be synced to.
What is the suggested to way to work in this scenario? I feel this is a pretty standard setup.
The text was updated successfully, but these errors were encountered:
@alexgorbatchev What would we need to change about the initial state of the docker image to fix this? I'm happy to look into making this initial state easier.
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
I don't completely understand how to get unison to work at boot time. I'm trying to keep my source folder syncing from local to container. When container starts, it expects the source to be there already. README suggests and my quick test confirms, that upon boot of the container,
/unison
is empty and needs to be synced to.What is the suggested to way to work in this scenario? I feel this is a pretty standard setup.
The text was updated successfully, but these errors were encountered: