first tryout, can't start Gush server about gush HOT 4 CLOSED

Hi Andrea,

sorry about the confusion in Readme. Gush is not yet autoloading files when in Rails app. I corrected that in README.

That said I fixed your bug in 0.1.2 which I just pushed to Rubygems. Can you try it now?

from gush.

Hi @pokonski thanks for prompt reply
I did updated my bundle, now that error is gone but I still cannot run it :

/usr/lib/ruby/2.0.0/pathname.rb:389:in initialize': no implicit conversion of nil into String (TypeError) from /usr/lib/ruby/2.0.0/pathname.rb:389:innew'
from /usr/lib/ruby/2.0.0/pathname.rb:389:in join' from /var/lib/gems/2.0.0/gems/gush-0.1.2/lib/gush/cli.rb:129:ingushfile'
from /var/lib/gems/2.0.0/gems/gush-0.1.2/lib/gush/cli.rb:134:in load_gushfile' from /var/lib/gems/2.0.0/gems/gush-0.1.2/lib/gush/cli.rb:25:ininitialize'
from /var/lib/gems/2.0.0/gems/thor-0.19.1/lib/thor.rb:355:in new' from /var/lib/gems/2.0.0/gems/thor-0.19.1/lib/thor.rb:355:indispatch'
from /var/lib/gems/2.0.0/gems/thor-0.19.1/lib/thor/base.rb:440:in start' from /var/lib/gems/2.0.0/gems/gush-0.1.2/bin/gush:13:in<top (required)>'
from /usr/local/bin/gush:23:in load' from /usr/local/bin/gush:23:in

didn't change my Gushfile, error's the same with or without Rails

ty

A

from gush.

Thanks for the stacktrace, I will inspect on my existing projects and try to recreate it. Then get back to you :)

from gush.

@pokonski I think I've managed to move on...
had to specify "-f "

so it becomes :
bundle exec gush workers -f ./Gushfile.rb

I got other errors there but I think I can manage it...
I suppose Readme should be slightly improved ;)

from gush.