You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried running foreman with bundler. Foreman without bundler. Both act the same. From within foreman I've tried statics: sh -c './tools/watch_static.rb', bundle exec ruby tools/watch_static.rb and any other combo I can think of. If I print PATH from before the running of the file on the 'statics' row, it prints a valid RBENV-based path which has FileWatcher in its downloaded set of gems. Any other program I run with Procfile works.
I'm on OS X, ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0], and this lockfile:
Hi, I haven''t had the time to try this out myself. But have you considered downgrading filewatcher til version 0.4? The latest version contains some stuff from a pull request, that I haven't tested fully.
This answer is a bit late, but I know what your problem is. Your watcher script works just fine, it just don't outputs to stdout, so you just don't see any output in your console.
If you add this line to the top of you watcher script, you should see some output in your console:
I have a procfile:
And the file:
And a Gemfile:
This is the output:
(nothing at the end, that is)
If I start it manually:
With appropriate output if I change a file...
I've tried running foreman with bundler. Foreman without bundler. Both act the same. From within foreman I've tried
statics: sh -c './tools/watch_static.rb'
,bundle exec ruby tools/watch_static.rb
and any other combo I can think of. If I print PATH from before the running of the file on the 'statics' row, it prints a valid RBENV-based path which has FileWatcher in its downloaded set of gems. Any other program I run with Procfile works.I'm on OS X, ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0], and this lockfile:
So I'm running out of ideas now. Do you have any pointers?
The text was updated successfully, but these errors were encountered: