I installed NodeJs and it worked like a charm. Thank you Colin, Walter and everyone. The only issue I have now appears to be Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'. It never ends. LOL
n Sunday, March 10, 2019 at 5:57:48 PM UTC-4, Colin Law wrote: > > On Sun, 10 Mar 2019 at 20:30, <braini...@gmail.com <javascript:>> wrote: > > > > Hi Colin, > > > > I am not sure but I think the issue is that it is running on a desktop > right now rather than on a webserver. > > Shouldn't make any difference, provided you have run bundle install on > the desktop. Nowadays I do use nodejs but I used to use therubyracer. > You could post your Gemfile here for us to see. > Alternatively you could just install nodejs. If this is a Debian based > system (Ubuntu for example) then you can run > sudo apt-get install nodejs > and then I think you can remove therubyracer. > > Colin > > > > > Thanks, > > > > On Sunday, March 10, 2019 at 4:04:21 PM UTC-4, Colin Law wrote: > >> > >> On Sun, 10 Mar 2019 at 17:35, <braini...@gmail.com> wrote: > >> > > >> > Thank you Walter and Hasan. The gem is actually in the gem file but > this occurred in development on my desktop so my guess would be I would > need to install it there. > >> > >> If therubyracer is in your Gemfile then that should be enough. > >> > >> Colin > >> > >> > > >> > On Sunday, March 10, 2019 at 1:27:30 PM UTC-4, Walter Lee Davis > wrote: > >> >> > >> >> Correct. Your server does not have a JavaScript interpreter > available at the command line. These days, I just install whatever version > of NodeJS is in the package manager for that server. If you want to avoid > any server dependencies, you can just add therubyracer to your Gemfile and > bundle on the server will install that. That's a JS interpreter written > entirely in vanilla Ruby. > >> >> > >> >> Walter > >> >> > >> >> > On Mar 10, 2019, at 1:21 PM, braini...@gmail.com wrote: > >> >> > > >> >> > Yes I did. Where I was thrown off is in trying to understand what > the literal issue is so I could resolve it as my understanding was if there > were any outstanding issues with the app it wouldnt bundle I assumed the > issue to be OS related. I > >> >> > > >> >> > On Sunday, March 10, 2019 at 1:10:22 PM UTC-4, Hassan Schroeder > wrote: > >> >> > On Sun, Mar 10, 2019 at 9:45 AM <braini...@gmail.com> wrote: > >> >> > > >> >> > > Now that the bundle install has run successfully I have run into > the following error while running rake db:create. Does anyone have any > ideas how to resolve the issue? > >> >> > > >> >> > > rake aborted! > >> >> > > ExecJS::RuntimeUnavailable: Could not find a JavaScript runtime. > See https://github.com/rails/execjs for a list of available runtimes. > >> >> > > >> >> > Did you follow the link in the message? > >> >> > > >> >> > -- > >> >> > Hassan Schroeder ------------------------ hassan.s...@gmail.com > >> >> > twitter: @hassan > >> >> > Consulting Availability : Silicon Valley or remote > >> >> > > >> >> > -- > >> >> > 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-ta...@googlegroups.com. > >> >> > To post to this group, send email to rubyonra...@googlegroups.com. > > >> >> > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/c9b83824-b33c-4645-ba0b-84ec0d799494%40googlegroups.com. > > > >> >> > For more options, visit https://groups.google.com/d/optout. > >> >> > >> > -- > >> > 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-ta...@googlegroups.com. > >> > To post to this group, send email to rubyonra...@googlegroups.com. > >> > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/462f08c9-c75c-4d7c-9b0f-2c4674b45328%40googlegroups.com. > > > >> > For more options, visit https://groups.google.com/d/optout. > > > > -- > > 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-ta...@googlegroups.com <javascript:>. > > To post to this group, send email to rubyonra...@googlegroups.com > <javascript:>. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/rubyonrails-talk/4028b458-ae0c-485c-bd4d-9761b0b6828b%40googlegroups.com. > > > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@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/38df7585-8afa-4268-9e36-cbc0b8bb4050%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.