Not compatible with Puma

vigetlabs / gulp-rails-pipeline

Ditch the Rails Asset Pipeline and roll your own with Gulp

MIT License

646 stars 64 forks source link

Not compatible with Puma #43

Closed rhbrb closed 8 years ago

rhbrb commented 8 years ago

We've noticed a strange issue when using the Puma webserver instead of Webrick. Browser-sync will try to run on port 3000 (the same port the rails app is already being served on). I've noticed on your sample app that browser-sync runs on 3001. Gulp recognizes changes to files but the app does not live reload. It also causes serious memory and cpu drain on the computer.

Maybe there is a configuration change we need to make to Puma?

rhbrb commented 8 years ago

It appears the issue is that when you allow Puma to run multiple threads. When max threads is set to 1, the app behaves as originally intended