Open tukanos opened 6 years ago
Thanks so much for leaving this.
For many, the simpler way to avoid this problem is to install Node.js, which includes a javascript runtime that is easily found on most systems and avoids the need for any special configuration in the Gemfile. This is why Node.js is listed among the System Requirements (https://github.com/decko-commons/decko/blob/master/decko/README.rdoc)
But that is kind of weak sauce, since the error message didn't help you much at all in solving this. I'll leave this issue open until we have better messaging and make various solutions, including yours, easier to find in cases where a deck is installed and run without a runtime on the ready.
You are welcome. I'm happy I could help a little.
The logic I followed: 1) Got an error - followed the error link https://github.com/rails/execjs 2) Took the first suggested run time 3) Made it work
The table you have at the link https://github.com/decko-commons/decko/blob/master/decko/README.rdoc is somewhat confusing to me.
I would prefer a style where you would specify the most tested version as being preferred. The alternatives should work too but you would write that they where not that extensively tested or deployed. (I don't know with database if MySQL is tested more than PostgreSQL).
System requirements:
Preferred |
Alternative |
|
version 2.3.0p0 |
> 2.3.0 |
|
1.13.x |
> 1.0 |
|
6.7.8.9 |
> 6.7.8.0 |
|
A database engine |
Either MySQL 5.7 OR PostgreSQL 9.4.x (equivalent) |
or newer (for both engines) |
Javascript engine |
any other any another javascript engine |
Cool, thanks for that. I'll update our README.
To answer your question, we do continuous integration testing on both MySQL and PostgreSQL, but the site driving development uses MySQL, so it's inevitably more thoroughly field tested.
I still haven't addressed the core remaining issue (error detection around missing JS runtimes), but I did add a Dependency versions card that gets to some of the issues we've been discussing. (linked to from the "get started") page.
It's not as pretty/handy as your table, but it's a lot easier to maintain, and given how small our team is and how far behind our docs are, that's probably a smarter way for us to go right now.
Do whatever is easiest for you to! I know it can be difficult to handle everything in small teams.
I'm glad that I could help a little.
My configuration:
This is for those who may encounter similar issues when installing
Decko
and for the developers so they can fix it.I wanted to create a testing decko installation and I'm getting a
ExecJS::RuntimeUnavailable: Could not find a JavaScript runtime. See https://github.com/rails/execjs for a list of available runtimes.
message.I have installed the javascript google's V8 runtime using:
gem install therubyracer
.When I test the testing code it in
irb
session I'm getting anwers:When running
decko seed
I'm getting this error:I have tried to export the variable
I got an error:
The solution:
Edit
Gemfile
and add dependencies:Now the
bundle rake
runs correctly: