How To Build A Ruby Gem With Bundler, Test-Driven Development, Travis CI And Coveralls, Oh My! | Smashing Coding
Ruby is a great language. It was designed to foster happiness and productivity in developers, all the while providing tools that are effective and yet focused on simplicity. One of the tools available to the Rubyist is the RubyGems package manager. It enables us both to include “gems” (i.e. packaged code) that we can reuse in our own applications and to package our own code as a gem to share with
Using Bundler in Real Life
A lot of people have asked me what the recommended workflows for bundler are. Turns out, they're quite simple. Let's step through a few use-cases. You Get a Repo for the First Time You've just checked out a git (or other) repository for an application that uses bundler. Regardless of any other features of bundler in use, just run: bundle install This will resolve all dependencies and install the o
Gem Versioning and Bundler: Doing it Right
Recently, an upgrade to Rake (from version 0.8.7 to version 0.9.0) has re-raised the issue of dependencies and versioning in the Ruby community. I wanted to take the opportunity to reiterate some of the things I talked about back when working on Bundler 1.0. First, I'll lay out some basic rules for the road, and then go into some detail about the rationale. Basic Versioning Rules for Apps After bu
clarifying-the-roles-of-the-gemspec-and-gemfile
TL;DR Although apps and gems look like they share the concept of "dependency", there are some important differences between them. Gems depend on a name and version range, and intentionally don't care about where exactly the dependencies come from. Apps have more controlled deployments, and need a guarantee that the exact same code is used on all machines (dev, ci and production). When developing a
[bundler]Bunderを使ったGem管理のメモ | diary NET. 1.2mg
以前、つくったRVM環境をGemsetsをつかわない環境に作り直したのでメモ。 Rubyのバージョン管理ツール RVM は 複数バージョンのRuby と 各RubyのGemをGemsets で管理をするつもりで環境を作っていたのですが、この間、Rails勉強会＠東京 に行ったときに、Gemの管理はBundlerで、RVM では Rubyのバージョン管理のみに使うのがいいんじゃないかとアドバイスを頂いて、いろいろ試してみました。 まず、Gemの管理というのがいまいちイメージがつかめていなかったのですがGemfileという設定ファイルで RailsアプリなどをGithubなどからダウンロード、必要なGemをBundlerでインストール Rails2アプリを作る、Gemfileを作成する、バージョンを固定 Rails3アプリを作る、Gemfileは自動作成される、追記する、バージョンを固定 空
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
