impossible de démarrer le serveur de rails dans le cloud9 en utilisant un terminal de type "rails s -b $ IP -p $ port" - ruby-on-rails

/usr/local/rvm/gems/ruby-2.3.4/gems/railties-4.2.5/lib/rails/commands/server.rb:12:in parse!": invalid argument: -p -b (OptionParser::InvalidArgument) from /usr/local/rvm/gems/ruby-2.3.4/gems/rack-1.6.8/lib/rack/server.rb:316:inparse_options " à partir de /usr/local/rvm/gems/ruby-2.3.4/gems/rack-1.6.8/lib/rack/server.rb:191:in options" from /usr/local/rvm/gems/ruby-2.3.4/gems/railties-4.2.5/lib/rails/commands/server.rb:71:inset_environment " à partir de /usr/local/rvm/gems/ruby-2.3.4/gems/railties-4.2.5/lib/rails/commands/server.rb:55:in initialize" from /usr/local/rvm/gems/ruby-2.3.4/gems/railties-4.2.5/lib/rails/commands/commands_tasks.rb:75:inNouveau" à partir de /usr/local/rvm/gems/ruby-2.3.4/gems/railties-4.2.5/lib/rails/commands/commands_tasks.rb:75:in server" from /usr/local/rvm/gems/ruby-2.3.4/gems/railties-4.2.5/lib/rails/commands/commands_tasks.rb:39:inrun_command! " de /usr/local/rvm/gems/ruby-2.3.4/gems/railties-4.2.5/lib/rails/commands.rb:17:in <top (required)>" from /home/ubuntu/workspace/bin/rails:9:inexiger" à partir de / home / ubuntu / workspace / bin / rails: 9: in <top (required)>" from /usr/local/rvm/gems/ruby-2.3.4/gems/spring-2.0.2/lib/spring/client/rails.rb:28:incharge" de /usr/local/rvm/gems/ruby-2.3.4/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in call" from /usr/local/rvm/gems/ruby-2.3.4/gems/spring-2.0.2/lib/spring/client/command.rb:7:inappel" de /usr/local/rvm/gems/ruby-2.3.4/gems/spring-2.0.2/lib/spring/client.rb:30:in run" from /usr/local/rvm/gems/ruby-2.3.4/gems/spring-2.0.2/bin/spring:49:in" depuis /usr/local/rvm/gems/ruby-2.3.4/gems/spring-2.0.2/lib/spring/binstub.rb:31:in load" from /usr/local/rvm/gems/ruby-2.3.4/gems/spring-2.0.2/lib/spring/binstub.rb:31:in" de / home / ubuntu / workspace / bin / spring: 15: in require" from /home/ubuntu/workspace/bin/spring:15:in" à partir de bin / rails dans load" from bin/rails:3:in"

Réponses:

1 pour la réponse № 1

Ce sera server ou s ne pas -s comme ci-dessous

rails server -b $IP -p $PORT

ou

rails s -b $IP -p $PORT

0 pour la réponse № 2

J'ai eu cette réponse pour un autre forum et ça a fonctionné. Je viens de changer "$ port" en "$ PORT". Je ne sais pas si c'est à cause de la sensibilité à la casse.


Le plus populaire