-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update examples #62
base: update-examples
Are you sure you want to change the base?
Update examples #62
Conversation
This is needed when one works with a clone and wants the clone to have the special remote readily available.
298094d
to
505ddf9
Compare
I looked at the current state and it looks pretty much as I would imagine it. There is very little, if anything, that would be missing from the narrative. We spoke off the list and it seems that the main thing missing now is the fMRIPreped dataset to be cloned, which would provide a remake target (in general it would be good to have one, so that the tutorial can be completed without having to go through a full fMRIPrep run first). And this is the only reason for the PR being kept in the draft state. Whoever gets to it first can set it up; I am personally stuck with a provisioning problem for prospective execution (#69 - it seems noone else has experienced it before) and will prioritize understanding what happens there. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. There are just two comments that should be addressed before merging (remove the instructions to start the remake-remote).
Add a `datalad-remake` special remote: | ||
|
||
```bash | ||
> git annex initremote datalad-remake type=external externaltype=datalad-remake encryption=none allow-untrusted-execution=true | ||
> git annex initremote datalad-remake type=external externaltype=datalad-remake \ | ||
encryption=none allow-untrusted-execution=true autoenable=true | ||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not necessary anymore because datalad make
will automatically start remotes
Add a `datalad-remake` special remote: | ||
|
||
```bash | ||
> git annex initremote datalad-remake type=external externaltype=datalad-remake encryption=none allow-untrusted-execution=true | ||
> git annex initremote datalad-remake type=external externaltype=datalad-remake \ | ||
encryption=none allow-untrusted-execution=true autoenable=true | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is no longer required (see above)
If you're working with your own dataset, make sure to configure a `datalad-remake` special remote: | ||
|
||
```bash | ||
> git annex initremote datalad-remake type=external externaltype=datalad-remake \ | ||
encryption=none allow-untrusted-execution=true autoenable=true | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove this section, manual datalad-remake start is not necessary anymore
@m-wierzba The current examples will not work because the remote needs a special git configuration to run in If that seems too complicated: we can do
|
The previous PR was accidentally merged using
push --force
. This one continues the work started in the previous one.