Closed ionutciordas closed 5 years ago
I think guard-teaspoon is officially unsupported at this point. I don't think many people were using it, and it's hard to maintain. I'd be happy to transfer it to you, or something if you're interested in maintaining it (like 2 years later). haha
Configuration:
Starting my development environment with guard starts Puma, then when the guard-teaspoon plugin starts, it tries to start Puma again and it fails due to same port conflict.
This issue started since our upgrade to Rails 4.2.