A TTY Command Line Interface for interacting with OAuth 1.0 services.
Federated DVCS Repository | Status | Issues | PRs | Wiki | CI | Discussions |
---|---|---|---|---|---|---|
🧪 oauth-xx/oauth-tty on GitLab | The Truth | 💚 | 💚 | 💚 | 🏀 Tiny Matrix | ➖ |
🧊 oauth-xx/oauth-tty on CodeBerg | An Ethical Mirror (Donate) | ➖ | 💚 | ➖ | ⭕️ No Matrix | ➖ |
🐙 oauth-xx/oauth-tty on GitHub | A Dirty Mirror | 💚 | 💚 | ➖ | 💯 Full Matrix | ➖ |
🤼 OAuth Ruby Google Group | “Active” | ➖ | ➖ | ➖ | ➖ | 💚 |
🎮️ Discord Server | Let’s | talk | about | this | library! |
This library was written originally by Thiago Pinto in 2016 and bundled with the oauth gem. It was extracted into a separate library by Peter Boling in 2022 as part of the move to a stable version 1.0 for the oauth gem.
Tokens to Remember | |
---|---|
Source | |
Documentation | |
Compliance | |
Style | |
Support | |
Enterprise Support | 💡Subscribe for support guarantees covering all FLOSS dependencies! 💡Tidelift is part of Sonar! 💡Tidelift pays maintainers to maintain the software you depend on! 📊 @ Pointy Haired Boss: An enterprise support subscription is “never gonna let you down”, and supports open source maintainers! |
Comrade BDFL 🎖️ | |
... 💖 |
Install the gem and add to the application’s Gemfile by executing:
$ bundle add oauth-tty
If bundler is not being used to manage dependencies, install the gem by executing:
$ gem install oauth-tty
NOTE: You might see a warning like:
oauth-tty's executable "oauth" conflicts with oauth
Overwrite the executable? [yN] y
The oauth
executable from this gem is the extracted and repackaged executable from an old
version of the oauth
gem, so you should overwrite it.
In a shell run oauth
to start the console.
For now, please see the tests for other usage.
See SECURITY.md.
If you need some ideas of where to help, you could work on adding more code coverage, or if it is already 💯 (see below) check issues, or PRs, or use the gem and think about how it could be better.
We so if you make changes, remember to update it.
See CONTRIBUTING.md for more detailed instructions.
See CONTRIBUTING.md.
None yet!
Everyone interacting with this project’s codebases, issue trackers,
chat rooms and mailing lists agrees to follow the .
Made with contributors-img.
Also see GitLab Contributors: https://gitlab.com/oauth-xx/oauth-tty/-/graphs/main
</a>
This Library adheres to .
Violations of this scheme should be reported as bugs.
Specifically, if a minor or patch version is released that breaks backward compatibility,
a new version should be immediately released that restores compatibility.
Breaking changes to the public API will only be introduced with new major versions.
Yes. But I’m obligated to include notes…
SemVer should, but doesn’t explicitly, say that dropping support for specific Platforms is a breaking change to an API. It is obvious to many, but not all, and since the spec is silent, the bike shedding is endless.
dropping support for a platform is both obviously and objectively a breaking change
To get a better understanding of how SemVer is intended to work over a project’s lifetime, read this article from the creator of SemVer:
As a result of this policy, and the interpretive lens used by the maintainer, you can (and should) specify a dependency on these libraries using the Pessimistic Version Constraint with two digits of precision.
For example:
spec.add_dependency("oauth-tty", "~> 1.0")
See CHANGELOG.md for a list of releases.
The gem is available as open source under the terms of
the MIT License .
See LICENSE.txt for the official Copyright Notice.
You made it to the bottom of the page, so perhaps you’ll indulge me for another 20 seconds. I maintain many dozens of gems, including this one, because I want Ruby to be a great place for people to solve problems, big and small. Please consider supporting my efforts via the giant yellow link below, or one of the others at the head of this README.