/guard-livereload

Guard::LiveReload automatically reload your browser when 'view' files are modified.

Primary LanguageJavaScriptMIT LicenseMIT

Guard::LiveReload

Gem Version Build Status Dependency Status Code Climate Coverage Status

LiveReload guard allows to automatically reload your browser when 'view' files are modified.

Support

For any support question/issue related to livereload please ask on support@livereload.com.

Install

Please be sure to have Guard installed before continuing.

Install the gem:

$ gem install guard-livereload

Add it to your Gemfile (inside development group):

group :development do
  gem 'guard-livereload', require: false
end

Add guard definition to your Guardfile by running this command:

$ guard init livereload

Use rack-livereload or install LiveReload Safari/Chrome extension

Usage

Please read Guard usage doc and rack-livereload how it works readme section or LiveReload extension usage doc from version 1.x

Guardfile

You can adapt your 'view' files like you want. Please read Guard doc for more info about Guardfile DSL.

guard 'livereload' do
  watch(%r{app/views/.+\.(erb|haml|slim)})
  watch(%r{app/helpers/.+\.rb})
  watch(%r{public/.+\.(css|js|html)})
  watch(%r{config/locales/.+\.yml})
  # Rails Assets Pipeline
  watch(%r{(app|vendor)(/assets/\w+/(.+\.(css|js|html))).*}) { |m| "/assets/#{m[3]}" }
end

Options

LiveReload guard has 6 options that you can set like this:

guard 'livereload', grace_period: 0.5, override_url: true do
  # ...
end

Available options:

notify: true          # default false
host: '127.3.3.1'     # default '0.0.0.0'
port: '12345'         # default '35729'
apply_css_live: false # default true
override_url: false   # default false
grace_period: 0.5     # default 0 (seconds)

notify uses Guard's system notifications. See LiveReload configuration doc from version 1.x for more info about other options.

Development

Pull requests are very welcome! Please try to follow these simple "rules", though:

  • Please create a topic branch for every separate change you make.
  • Make sure your patches are well tested.
  • Update the README (if applicable).
  • Please do not change the version number.

For questions please join us on our Google group or on #guard (irc.freenode.net).

Author

Thibaud Guillaume-Gentil