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

"twine configure" verb for a guided setup #216

Open
glyph opened this issue Oct 5, 2016 · 3 comments
Open

"twine configure" verb for a guided setup #216

glyph opened this issue Oct 5, 2016 · 3 comments

Comments

@glyph
Copy link

@glyph glyph commented Oct 5, 2016

Writing config files by hand is so 1998. Twine should have a verb for configuring itself.

As per #208, this guided configuration should store secret materials responsibly, i.e., requiring the keyring.

@bhrutledge
Copy link
Contributor

@bhrutledge bhrutledge commented Jan 21, 2020

Could this be covered the twine accounts command proposed in #324?

@sigmavirus24
Copy link
Member

@sigmavirus24 sigmavirus24 commented Jan 21, 2020

@bhrutledge I believe the opposite is more accurate. configure is more general, one could configure repository which includes the account, url, etc. The opposite isn't as true.

@bhrutledge
Copy link
Contributor

@bhrutledge bhrutledge commented Jan 23, 2020

@sigmavirus24 It seemed to me that twine accounts had the benefit of a proposed spec, which covered the requirement to "store secret materials responsibly". This issue seems more vague.

It's my understanding that the only thing that's read from --config-file is repository, username, and password. Is there more to configure besides that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants