Permalink
Browse files

installs node.js as ExecJS runtime

The Gemfile generated for new apps has therubyracer commented out
so you need to edit the Gemfile, and run bundle again, for every
test application you generate.

ExecJS picks node.js directly if it is installed in the system,
so new applications just work.
  • Loading branch information...
1 parent 6490676 commit 77ce5125b616b4a168ab8f50a254e5b4ef7a331e @fxn fxn committed Sep 30, 2012
Showing with 8 additions and 7 deletions.
  1. +1 −1 README.md
  2. +7 −6 puppet/manifests/default.pp
View
@@ -43,7 +43,7 @@ Port 3000 in the host computer is forwarded to port 3000 in the virtual machine.
* Databases and users needed to run the Active Record test suite
-* therubyracer
+* Node.js for the asset pipeline
* Memcached
@@ -107,12 +107,6 @@
user => 'root',
require => Package['ruby1.9.3']
}
-
- exec { '/usr/bin/gem install therubyracer --no-rdoc --no-ri':
- unless => '/usr/bin/gem list | grep therubyracer',
- user => 'root',
- require => [Package['ruby1.9.3'], Package['build-essential']]
- }
}
class { 'install_ruby': }
@@ -123,4 +117,11 @@
}
class { 'install_nokogiri_dependencies': }
+class install_execjs_runtime {
+ package { 'nodejs':
+ ensure => installed
+ }
+}
+class { 'install_execjs_runtime': }
+
class { 'memcached': }

0 comments on commit 77ce512

Please sign in to comment.