Feature-Request: "rake release" instead of "gem inabox pkg/xxx" would be cool about geminabox HOT 10 CLOSED

I've been considering this for a while, if you fancy patching it in, that would be great! Otherwise, it's on my todo list.

from geminabox.

I was having a look at this issue today . . . this guy seems to have a fairly easy hacky way to do it: http://www.alexrothenberg.com/2011/09/16/running-a-private-gemserver-inside-the-firewall.html

I think it would be nice to patch bundler to make rake release work like this, but still have it as a per gem configuration option to push to geminabox or rubygems.org

It seems like rubygems 1.9.0 is going to have a metadata option for the .gemspec https://github.com/rubygems/rubygems/blob/master/lib/rubygems/specification.rb so that would be a nice way to switch this functionality on with something like s.metadata = { "geminabox" => "http://gems/" }

from geminabox.

Hmm. I quite like the idea of being able to require 'geminabox/tasks' in a Rakefile and have it just work. Having it do so if required after bundler would be doable (we can just delete the rake task and have a clean slate from there), but if bundler's tasks are loaded 2nd, death would occur.

I'll ponder, but that article is really handy for putting me on track.

from geminabox.

This seems like a cool feature, but I wouldn't want geminabox's rake tasks to replace bundler's (or the other way around). How about something like:

rake release:geminabox

from geminabox.

+1 for not replacing bundlers gemtasks. Geminabox should always have its own task-names.

The reason is simple: Type rake release on a Gem that was not properly patched (for whatever reason) and whoops, you've just released your gem to rubygems.org. It'd be an accident waiting to happen.

from geminabox.

Also agree with the not replacing the release command. We could optionally noop the release command, and add another in it's place for true paranoia.

Pull request anyone?

from geminabox.

What should be the command if i want to release gem to local server

from geminabox.

rake gib perhaps? 😄

I think the exact name is not so important as long as it's documented and different enough from release that no accidents happen. It's unfortunate that bundler uses release instead of e,g, release:rubygems here.

I guess the aesthetically cleanest solution would be for geminabox to rename release to release:rubygems and add release:gib of its own.

from geminabox.

Any progress on this (if not with the implementation, at least architecturally)? I miss being able to create a git tag and upload the gem in one automated step. If there is a consensus to how things should be handled, I'd be happy to lend a hand in the implementation.

from geminabox.

I didn't like the idea of including geminabox and all it's dependencies to a project just to provide a rake release task, so i made a dependency free gem to to that.

https://github.com/dfherr/geminabox-release

it adds rake inabox:release, inabox:push and inabox:forcepush tasks to the bundler gem_tasks by hacking into bundler gemtask interface and pushing via net/http. It can use the provided host in your geminabox config file or you can hardcode one in the initializer.

from geminabox.