search

palantirnet / butler

MIT License
13 stars 2 forks source link

Kill process is breaking things #37

Open aCyborg opened 8 years ago

aCyborg commented 8 years ago

We think it needs and if statement, but it breaks if you run it on vagrant

froboy commented 7 years ago

I'm seeing this on a new vagrant box. Any workarounds that you've come up with?

Specifically, butler doesn't seem to watch files on vagrant and needs to be killed when code is updated (possibly related or maybe different issue). Once the process is killed, npm run butler gives the following error:

Error: Command failed: /bin/sh -c ../../vendor/bin/sculpin generate --watch --server --project-dir="../../styleguide/"

  [React\Socket\ConnectionException]                            
  Could not bind to tcp://0.0.0.0:8000: Address already in use
becw commented 7 years ago

@froboy you might try checking who's using the port? I think this should give you a pid:

fuser -n tcp 8000
froboy commented 7 years ago

@labbydev helped resolve this. We added the kill command and then removed it and everything was fine.