- #COULD NOT CONNECT TO LIVERELOAD SERVER HOW TO#
- #COULD NOT CONNECT TO LIVERELOAD SERVER MAC OS#
- #COULD NOT CONNECT TO LIVERELOAD SERVER INSTALL#
- #COULD NOT CONNECT TO LIVERELOAD SERVER FREE#
guard(main) > 15:17:28 - INFO - Browser connected. → _siteġ5:17:26 - INFO - Jekyll watching and serving at 0.0.0.0:4000/ġ5:17:26 - INFO - LiveReload is waiting for a browser to connect.ġ5:17:26 - INFO - Guard is now watching at '/Users/Damien/Documents/LBSRF ' > (You can run `guard` with -no-bundler-warning to get rid of this message.)ġ5:17:19 - INFO - Guard is using to send notifications.ġ5:17:26 - INFO - Jekyll build complete. Otherwise, consider using `bundle exec guard` to ensure your > dependencies are loaded correctly.
#COULD NOT CONNECT TO LIVERELOAD SERVER FREE#
If this is your intent, feel free to ignore this > message. Please report a bug if this causes problems.ġ5:17:18 - INFO - Guard here ! It looks like your project has a Gemfile, yet you are running
#COULD NOT CONNECT TO LIVERELOAD SERVER MAC OS#
Im under Mac OS 10.9.3 with Ruby 2.0.0-p247 using rbenv. Then I can get back to my book on themes, including examples using Gulp.WARN: Unresolved specs during Gem::Specification.reset: When I try to connect guard-livereload to the LiveReload Chrome extension I get this error in Chrome. Next step – wrap it all up in a nice Docker image with some documentation to make it easier to play with Magento 2 development with minimal setup pain. Touch a Less source file on Windows, it copies to the container, it recompiles, and the web browser flickers as the change reloads. You can now run “gulp watch” (with LiveReload enabled in your Gulpfile) and have the Chrome extension connect successfully into your Docker container (VirtualBox is doing the port forwarding for you).
#COULD NOT CONNECT TO LIVERELOAD SERVER INSTALL#
Add a second port (click the “+” icon to the right) and enterĬlick OK and accept all the changes. You don't need to add gulp-connect for this to work - just do the following: Install the livereload chrome extension Configure your gulpfile and package.json (the OP had done so correctly) Go to chrome://extensions and check the box for 'Allow access to file URLs' Restart chrome Navigate to the. By default you should see one port forward for port 22, which I think is used by Kitematic to control Docker via SSH. Open up the VirtualBox GUI, select the VM you are using for Docker (“default” in my case), go to “Settings”, pick “Network” from the side menu, then click the “Port Forwarding” button near the bottom of the page.
#COULD NOT CONNECT TO LIVERELOAD SERVER HOW TO#
So how to set up a port forward? I am running Docker inside VirtualBox on Windows (which Docker Toolbox uses under the covers). If they were trying with a remote web server it would not work (with an error message including the remote web server host name – no hint that it was localhost that was being connected to). If they were using a local web server, it would just work. That explains the mixed reactions in the reviews I suspect. D’oh! Once I set up a port forward from Windows to the Docker container, it started working. The missing factoid was that the Chrome extension ALWAYS connects to 127.0.0.1, not the host name in the URL you are connecting to. The problem was I could not get the Chrome LiveReload plugin to connect. Easy right? But after lots of hair pulling, I just could not get it to work.
So I change a local file using my text editor, WinSCP copies the changes to the Docker container, this triggers Gulp to recompile the Less file, and notifies LiveReload of the new CSS file for the web browser to load. I am using WinSCP Ctrl-U (“Keeping remote files up to date”) with SFTP to copy local file changes into a remote container (OS X users might use lsyncd instead).
0 kommentar(er)
