I’ve tried running the app in a more verbose mode, toggling things on/off, but I’ve not found any magic combo that gets this to work. You can see the hugo on port 80 and c9 on 81, but nothing is listening at the prescribed 35729 port. Unix 2 STREAM LISTENING 88537 /tmp/supervisor.sock.9 ![]() Unix 2 STREAM LISTENING 89646 /root/.c9/bridge.socket Proto RefCnt Flags Type State I-Node Path Proto Recv-Q Send-Q Local Address Foreign Address StateĪctive UNIX domain sockets (only servers) The site loads fine, but then Chrome starts complaining about: WebSocket connection to 'ws://192.168.52.1:35729/livereload' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSEDĪnd, sure enough, if I pop into the container and run a netstat, I see this: # yum install -y net-toolsĪctive Internet connections (only servers) The simplest way to add live reloading to all your watch targets is by setting livereload to true at the task level. Set the option livereload to true to enable on the default port 35729 or set to a custom port: livereload: 1337. ![]() ![]() My docker is version 1.11 and I’ve got it using real IP addresses instead of its normal 172 game, but I tried this in a VM with an older docker (1.6 – ancient, right?) with a more normal setup and I end up with the same thing. Live reloading is built into the watch task. Atom is a modern, powerful IDE, which can be used for many computer programming languages including C++. Usage Add as scene plugin, session plugin or to any atom which has your plugin (s) loaded. No more clicking on Reload every time just to see if you get an error. LiveReload Monitors the source files of local plugins for changes and auto-reloads them. I’m running hugo and cloud9 ide in a docker container and when I startup hugo, the live reload feature isn’t working. LiveReload - Tool for plugin developers to auto-reload when source files changed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |