Unless you use one of the supported remote workflows, LiveReload 2 won’t work when your changes never reach the local disk. Examples of unsupported workflows are:
However, if you have ssh access to your server and you can install Ruby gems on it, you still can get live reloading to work using our browser extensions and a command-line tool called guard-livereload.
Make sure Ruby 1.8.7+ and a recent version of RubyGems (perhaps 1.8+) is installed on the server.
Install guard and guard-livereload:
sudo gem install guard guard-livereload (whether you need sudo or not depends on your system configuration)
SSH into your server, cd into your project folder and run:
guard init guard init livereload
This will create a file named “Guardfile” which tells Guard what to do when files are modified. Guard has multiple plugins to handle all kinds of actions; guard-livereload is one of them.
guard command on the server (remember to do this from your project folder). You should get a line saying that LiveReload is now listening.
Make sure LiveReload 2 is not running. You need the corresponding TCP port to be free on the next step.
Forward LiveReload’s port to your server, so that local browser extensions can connect to guard-livereload running remotely. You need to run ssh with the following arguments:
ssh -L 35729:127.0.0.1:35729 …
where … is the usual stuff you type after
ssh. You need to keep this command running to be able to use LiveReload.
If things don’t work, and/or on the next step ssh says something about not being able to open a channel, please check that your server has SSH port forwarding enabled. Most shared hosts don’t, and even if you have your own server it may be disabled by default.
Now you can open the remote site in your browser and turn LiveReload on.
That should work. Please let us know if it does not.