On Sun, Aug 8, 2010 at 10:23 PM, Bradley <bradleyrobert...@gmail.com> wrote:
> I'm writing a new app that uses a custom gem not publicly available on > gemcutter, or anywhere for that matter. I'm building both the app and > gem with Hudson CI, then I'd like the app pushed to heroku by somehow > installing this gem and pushing. > ... > I don't want these gems available publicly which is why I'm looking > for a good way to package the gem for my Heroku app to be able to use > it appropriately. > ... > Doe this make sense? Any suggestions/help is greatly appreciate. > Like it has been suggested, I think you can go the bundler route. Alternatively, if you maintain your public source repository, you can use the --source option to distribute your gems that way. Instructions on how to do this are here: http://docs.heroku.com/gems Running your own gem server in this fashion doesn't appear to be particularly hard: http://docs.rubygems.org/read/chapter/18#page80 You could then reference it from your .gems manifest with the --source argument But in your case, you do not want that distributed and it would need to be secure. There doesn't seem to be good documentation on how to use a https --source argument or how to pass authentication credentials. May not be possible. Which would be a shame, because the process you are describing, of using in house gems in this manner is a habit of very effective Ruby teams: you don't just DRY up your project code, you DRY up common code across projects by refactoring to gems. Bundler might be the future, but its a bit of a heavyweight solution for some people (not to mention being a bit beta) -- http://richardconroy.blogspot.com -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
