7
POWering through Rails/Rack Application Development Saving the world, one command at a time™ Jeremy Ebler © 2013

POWering Through Rails/Rack Application Development

Embed Size (px)

Citation preview

Page 1: POWering Through Rails/Rack Application Development

POWering through Rails/Rack Application

DevelopmentSaving the world, one command

at a time™

Jeremy Ebler © 2013

Page 2: POWering Through Rails/Rack Application Development

Developing sites has never been easier!● http://pow.cx/

Use Pow to painlessly develop:● Ruby on Rails● Any Rack Application● Static Sites (Nanoc/Stasis)

POW

Page 3: POWering Through Rails/Rack Application Development

Pow prevails over the forces of evil.

● Convention trumps configuration.● No maintenance required.● Tame multiple Rubies.● Integrated with OS X.

What is POW?

Page 4: POWering Through Rails/Rack Application Development

How to POW?

Install with a simple command:$ curl get.pow.cx | sh

Symlink your app into ~/.powVisit http://#{symlink}.dev/ in a web browser.

Nothing to start, no terminal windows, just browse and go!

Page 5: POWering Through Rails/Rack Application Development

Actually, yes!

$ gem install powder

$ powder link [name]

$ powder open

https://github.com/rodreegez/powder

Can it be Easier?

Page 6: POWering Through Rails/Rack Application Development

Bundle faster than a speeding SSD!(or 5400rpm HDD…)

Setup the Cache$ git clone git://github.com/akitaonrails/rubygems_proxy.git rubygems

$ cd rubygems; powder link

~/.bash_profile$ export LOCALGEMS='http://rubygems.dev'

Gemfile$ source ENV['LOCALGEMS'] || 'https://rubygems.org'

POW rubygems cache

Page 7: POWering Through Rails/Rack Application Development

https://github.com/mpapis/rubygems-bundler

Simply,$ gem install bundler rubygems-bundler$ gem regenerate_binstubs

It modifies gem wrappers shebang to load ruby_noexec_wrapper. Then, when you run gem binaries, it takes a look at your working directory, and every directory above it until it can find a Gemfile. If the executable is present in your Gemfile, it switches to using that Gemfile instead (via Bundle.setup).

No more bundle exec