Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Offer bootstrap after clone #45

Closed
TheLocehiliosan opened this issue Jan 13, 2017 · 3 comments
Closed

Offer bootstrap after clone #45

TheLocehiliosan opened this issue Jan 13, 2017 · 3 comments
Assignees
@TheLocehiliosan
Labels
feature
Milestone
1.07

Comments

@TheLocehiliosan
Copy link
Owner

After a successful clone, offer to run the bootstrap command (if it exists post-clone). Also add options to the clone command to force bootstrap to run or prevent bootstrap from running without any prompting.
@TheLocehiliosan TheLocehiliosan added this to the 1.07 milestone Jan 13, 2017
@TheLocehiliosan TheLocehiliosan self-assigned this Jan 13, 2017
TheLocehiliosan added a commit that referenced this issue Jan 25, 2017
@TheLocehiliosan
Tests for offering bootstrap during clone (#45)
12a2317
TheLocehiliosan added a commit that referenced this issue Jan 25, 2017
@TheLocehiliosan
Offer bootstrap after clone (#45)
08e6cd4
TheLocehiliosan added a commit that referenced this issue Feb 10, 2017
@TheLocehiliosan
Release 1.07
def7e73 
Update version number and update documentation

* Add `CLASS` to supported alt-link patterns (#21)
* Add bootstrap command (#42)
* Support wildcards for alt-links (#43)
* Stash conflicting data during clone (#44)
* Offer bootstrap after successful clone (#45)
* Display supported configs for `yadm config` (#46)
* Add "curl-pipe" program to clone without installation (#48)
* Fix bug in alt-link regular expressions (#49)
@mipimipi
Copy link

mipimipi commented Dec 3, 2018

Hi,
just a question about this feature: As far as I understand it from the posts above, the feature would allow to execute some logic after cloning. Could this be used to handle the config directories of Firefox and Thunderbird properly? Both programs store their config in a directory named <some-generated-8-letter-ID>.default. The generated ID is unique for each installation. So, in order to use a config directory from a yadm repo for a newly installed FF or TB, some logic is needed to rename the config folder.
Thanks, mipi

@mipimipi
Copy link

mipimipi commented Dec 3, 2018

Sorry, just saw, that the feature is already implemented. It would be nice if my question could still be answered. Thanks!

@TheLocehiliosan
Copy link
Owner Author

@mipimipi If you can program it (or script it) it can be done. If a bootstrap exists, it will be executed after a successful clone.

Perhaps symlinking your directory to the machine specific name would be a good solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TheLocehiliosan TheLocehiliosan

Labels
feature
Projects
None yet
Milestone
1.07
Development

No branches or pull requests
2 participants
@TheLocehiliosan @mipimipi