Ruby on Rails Wednesday, April 3, 2019



On Thu, Apr 4, 2019 at 11:30 AM <medright@gmail.com> wrote:
ExecStart=/home/pi/.rbenv/bin/rbenv bundle exec rails s -b 192.168.1.66
 
i havent used rbenv like that, but, have you tested that statement alone on a command line?
have you tried running without rbenv in that line?

any thoughts here? thinking the rbenv PATH is causing the issue, not sure how its needing to be structured to access that correct PATH to execute the 'rails' command.

you already have a working directory; and assumming that directory is a rails app dir, you can run bundle and rails among others in there.

--
many thanks and many regards,
--botp

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAAwHHQhYukfXmyjLJ6a5en%2BMyzix5y_mS2mFoHPXYVqrZTyxDQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment