geminabox-release

This is for all users of a geminabox-server who do use bundler and rake, but do not want to install geminabox and all it's dependencies locally just to have a gem push command.

The gem is a dependency free option to add a rake inabox:release task to bundler gem_tasks for releasing a new gem to your geminabox server.

It only uses the ruby default libaries uri and net/http and expects you are using bundler.

You must no longer require "bundler/gem_tasks" as geminabox-release requires a modified version for you which supports all other functionality!

How to use

Simply load this gem and patch with your geminabox URL in your Rakefile.

E.g.

require 'geminabox-release'
GeminaboxRelease.patch(:host => "http://localhost:4000")

or use your geminabox config file (YAML file with key :host and host url as value in ~/.gem/geminabox)

require 'geminabox-release'
GeminaboxRelease.patch(:use_config => true)

Then you will get a rake inabox:release task.

If your geminabox server is using SSL/TLS, but you have an untrusted certificate, you can use the option ssl_dont_verify.

E.g.

require 'geminabox-release'
GeminaboxRelease.patch(:host => "https://localhost:4000", :ssl_dont_verify => true)

However, that is NOT recommended.

If you wish to remove the bundler/gem_tasks rake release task, you can by adding :remove_release to the patch options:

GeminaboxRelease.patch(:remove_release => true)

Ensure you do not require "bundler/gem_tasks" in your rakefile anymore!

The gem (theoretically) supports basic auth like geminabox in the host address. e.g. http://username:password@localhost:4000 It's untested as we didn't need it. Feel free to try it.

Additional tasks

The gem additionally provides tasks for build & push without all the overhead release produces (like git tag and git push):

$> rake inabox:push          # just builds gem and pushes to geminabox server
$> rake inabox:forcepush     # builds gem and pushes to geminabox server overwriting existing same version

Safety

To ensure you are not accidentally pushing your gem to rubygems there are two distinct safety measures.

The rake task has another name. Do not use rake release if you want to push to your geminabox server!
The gem is pushed via the HTTP POST file request geminabox expects and not via the gem push interface.
You can even fully remove the rake release task, if you wish to.

Troubleshooting

If the rake tasks do not show make sure you did not require "bundler/gem_tasks" anywhere (espacially before requiring geminabox-release).

LICENSE

see LICENSE

hilli / geminabox-release Goto Github PK