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.

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

cmd/gitannex: Add config parameter synonyms for compat, update command documentation #7854

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

dmcardle
Copy link
Contributor

@dmcardle dmcardle commented May 18, 2024

What is the purpose of this change?

The main purpose is to simplify setup for users.

First, this PR adds aliases to the existing config parameters so users can use the same config names as https://github.com/git-annex-remote-rclone/git-annex-remote-rclone.

Secondly, this updates the command documentation.

  • It mentions that new versions of git-annex support type=rclone, so it's possible to skip the whole symlink business.
  • It drops duplicative description of config parameters, instead showing users how to use the --whatelse option of git annex initremote.
  • It rewrites setup steps for clarity, improves formatting, etc.

Was the change discussed in an issue or in the forum before?

Issue #7625

Checklist

  • I have read the contribution guidelines.
  • I have added tests for all changes in this PR if appropriate.
  • I have added documentation for the changes if appropriate.
  • All commit messages are in house style.
  • I'm done, this Pull Request is ready for review :-)

@dmcardle
Copy link
Contributor Author

@ncw, PTAL!

FYI, looks like there's an unrelated lint error in backend/googlephotos/.

Mentioned the possibility of skipping the symlink for new versions of
git-annex. (Probably deserves a test once the new git-annex trickles
down to CI platforms.)

I stopped trying to explain each config parameter here. Rather, the doc
now shows the user how to ask git-annex to describe config parameters
with `--whatelse`.
@dmcardle
Copy link
Contributor Author

Friendly ping, @ncw :)

@dmcardle
Copy link
Contributor Author

@yarikoptic FYI, this should make porting over a little simpler — no need to manually translate each config name any more. I'd appreciate feedback on the markdown changes, too, if you have any thoughts!

I'd like to spell out in detail how to recover the configuration parameters originally used to make one's git-annex-remote-rclone remote, but I still haven't figured out exactly what command(s) would do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant