On Thursday, October 12, 2017 at 9:55:24 AM UTC-7, Lisa Kachold wrote: > > SOLUTION: (thanks to ohadlevy)* > > Here's the Json version issue: Need to move to Json 1.8.6 from default > Json 2.0.4: > > gem list --local | grep json > > fog-*json* (1.0.2) > > *json* (1.8.6) > > multi_*json* (1.12.2) > > po_to_*json* (1.0.1) > > rack-*json*p (1.3.1) > > To remove a default gem and rebuild bundle: > > gem install json -v 2.0.4 > > gem uninstall json -v 2.0.4 > > bundle install > > locate json-2.0.4.gemspec > > mv json-2.0.4.gemspec /usr/local/src/oldgems/2.0.4/ > > bundle install > > Suggestion from ovahlevy that showed me the error output for Json. I was > using: bundle *exec* foreman start from > 'Setup Development Environment': > https://theforeman.org/contribute.html#SupportedRubyversions > > *BIND*=0.0.0.0 foreman start > > > Now webrick and rails for foreman listen on all ports! > > AND Javascript work GREAT! > > > On Thursday, October 12, 2017 at 8:50:04 AM UTC-7, Lisa Kachold wrote: >> >> ohadlevy - This will be the ultimate solution for Listening on all ports >> in 17.1 Development >> >> For "listening on all ports for Foreman 1.17.1" - starting up via: >> >> "BIND=0.0.0.0 foreman start" fails with Json errors for Bundler (which >> shines light on the Menu dropdown javascript issues). >> >> Strange that the tests didn't catch this? I will resolve the bundler >> version and ensure my Ruby stack. >> >> Thanks again! >> >>
-- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
