Doesn't use port specifed in config

jc00ke / guard-puma

Restart puma when files change

MIT License

50 stars 19 forks source link

Doesn't use port specifed in config #17

Closed dsandstrom closed 8 years ago

dsandstrom commented 8 years ago

I set the port I want to use in puma's config file to 4010, then made guard-puma load that file. However, port 4000 is still used. I have to set the port using guard-puma's options.

Doesn't work

guard 'puma', config: 'config/puma/development.rb' do
...

Work around

guard 'puma', config: 'config/puma/development.rb', port: 4010 do
...

jc00ke commented 8 years ago

Thanks for the report. Can you set up a barebones repo that demonstrates this? Thanks!

dsandstrom commented 8 years ago

Looks like this was fixed by #15, you just need to release a new gem version.

jc00ke commented 8 years ago

@dsandstrom heh, you're right. Sorry for the slow release, it's been a long time since I've even looked at this project.

https://rubygems.org/gems/guard-puma