mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

response

Browse source
This commit is contained in:
Joey Hess 2016-09-21 16:14:11 -04:00
parent 0de88a9b68
commit bd2cfe008c
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 25 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
doc/forum/manage_repository_connection_between_external_HDD_and_server/comment_1_ba8ed548bf228a7d1c82b68283f99a5b._comment Normal file
View file

@ -0,0 +1,25 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2016-09-21T20:06:28Z"
content="""
I'm not entirely sure I understand the question, but think you're
probably trying to make nhost be able to access data0 independant
of whether the external HDD is plugged into nhost or zhost
(or perhaps qhost, whatever that is?)
The way to do that is simply to set up one remote for each place
the HDD can be plugged into. If the HDD can be plugged in locally,
make a remote pointing at the local mount point. If the HDD can be
plugged into zhost, make a remote pointing at
zhost:/run/media/mee/data0/NIdata/ and so on.
git-annex will figure out that these different remotes are pointing
at the same repository. When running `git annex get` or `git annex sync
--content`, it will check if the HDD is mounted locally,
and will use it there if so; if not it will fall back to trying
to access it via the remotes that use zhost etc.
So in summary, git-annex is designed to just work in this kind of scenario.
Set up lots of remotes and let it figure out which ones to use.
"""]]