Go to file
John Bintz 66e584e37a it goes here, not where it was going 2011-11-04 13:42:42 -04:00
js initial commit 2011-11-04 11:51:22 -04:00
lib haha, fix a dumb bug: 2011-11-04 11:57:41 -04:00
spec haha, fix a dumb bug: 2011-11-04 11:57:41 -04:00
.gitignore initial commit 2011-11-04 11:51:22 -04:00
Gemfile initial commit 2011-11-04 11:51:22 -04:00
Guardfile initial commit 2011-11-04 11:51:22 -04:00
README.md it goes here, not where it was going 2011-11-04 13:42:42 -04:00
Rakefile initial commit 2011-11-04 11:51:22 -04:00
config.ru initial commit 2011-11-04 11:51:22 -04:00
rack-livereload.gemspec update gemspec to keep bundler from yelling 2011-11-04 13:29:13 -04:00

README.md

Hey, you've got LiveReload in my Rack! No need for browser extensions anymore! Just plug it in your middleware stack and go!

Use this with guard-livereload for maximum fun!

Using in...

Rails

In config/environments/development.rb:

MyApp::Application.configure do
  config.middleware.insert_before(Rack::Lock, Rack::LiveReload)
end

config.ru/Sinatra

require 'rack-livereload'

use Rack::LiveReload

How it works

The necessary script tag to bring in a vendored copy of livereload.js is injected right before the closing head tag in any text/html pages that come through. The script tag is built in such a way that the HTTP_HOST is used as the LiveReload host, so you can connect from external machines (say, to mycomputer:3000 instead of localhost:3000) and as long as the LiveReload port is accessible from the external machine, you'll connect and be LiveReloading away!

To-do

  • Specify the port
  • Override the host
  • Change the reload delays

As usual, super-alpha!