e19916f54b
And use it to set annex-config-uuid in git config. This makes using the origin special remote work after cloning. Without the added Logs.Remote.configSet, instantiating the remote will look at the annex-config-uuid's config in the remote log, which will be empty, and so it will fail to find a special remote. The added deletion of files in the alternatejournaldir is just to make 100% sure they don't get committed to the git-annex branch. Now that they contain things that definitely should not be committed.
24 lines
877 B
Markdown
24 lines
877 B
Markdown
datalad-annex supports cloning from the web special remote,
|
|
using an url that contains the result of pushing to eg, a directory
|
|
special remote.
|
|
|
|
`datalad-annex::https://example.com?type=web&url={noquery}`
|
|
|
|
Supporting something like this in git-remote-annex would be good.
|
|
|
|
The httpalso special remote already exists to handle this kind of thing.
|
|
|
|
In fact, it just works with git-remote-annex!
|
|
|
|
Eg, this url on my laptop is a directory special remote
|
|
accessed via the web server:
|
|
|
|
annex::13c2500f-a302-4331-9720-6ec43cb8da2b?encryption=none&exporttree=yes&type=httpalso&url=http%3A%2F%2Flocalhost%2F~joey%2Ftmp%2Fd
|
|
|
|
But, while fetching from a httpalso special remote works, and cloning
|
|
works, after cloning, fetching again fails:
|
|
|
|
joey@darkstar:~/tmp/newp2>git fetch origin
|
|
git-annex: no url configured for httpalso special remote
|
|
|
|
> fixed that, [[done]] --[[Joey]]
|