This is a collection of dirty, dirty patches for gem push
and gem yank
:
- When you do not supply an API key and you are not using
rubygems.org
, you are not prompted to sign intorubygems.org
gem yank
accepts--host [HOST]
and--key [KEY]
options
API keys should be stored in YAML format in $HOME/.gem/credentials
:
---
:rubygems_api_key: 198dbad38sadasd87
:another_key: 2897234987bsdb90834
Then specify --host
and --key
options when pushing/yanking:
$ gem push mygem-1.0.0.gem --host https://example.com --key another_key
$ gem yank mygem-1.0.0.gem --host https://example.com --key another_key
gem install rubygems-source-cli
or add it to your Gemfile
:
gem "rubygems-source-cli"
- Source hosted at GitHub
- Report issues/Questions/Feature requests on GitHub Issues
- CI at Travis
Pull requests are very welcome! Make sure your patches are well tested. Please create a topic branch for every separate change you make.
$ rake
- rubygems-source: remote source server for Rubygems that implements the core Rubygems gem source web API
- rubygems-source-features: Cucumber features for Rubygems sources
- rubygems.org: Daddy
- geminabox:
Very similar project, no
gem yank
, no tests of any kind - sinatra-rubygems:
Replacement for
gem server
- nogem push
,gem yank
or resolver