Welcome to the culerity wiki!
if you get an error message from the jruby process that some gems could not be found, try setting this in your env.rb
Culerity.jruby_invocation = 'RUBYOPT="" ' + File.expand_path("~/.rvm/bin/celerity_jruby")
you are probably using the (old) rubyforge version of celerity. try the github version instead. (thanks to @jamescallmebrent)
this has been reported by @josevalim and i haven’t been able to reproduce this. here’s his solution: add an exit(0) call to the on_exit block in common_celerity.rb
at_exit do $browser.exit $server.close exit(0) end
I’ve also had this happen to me under 10.5.7 — @Caius
jRuby v1.5 (and, I think, v1.4) has an option called nailgun that spawns a JVM that all other instances of jruby then connect to. This saves the boot time for a JVM each time you run a jruby command. This can make culerity run significantly faster. To setup:
jruby --ng-serverin a separate shell
--ngflag. Perhaps the easiest way to do this is to set
--ngoption without first setting up the nailgun server will cause this error:
connect: Connection refused
jruby -S gem install culerity
config.action_mailer.delivery_method = :persistentinside your
environments/culerity.rb. You can find the rationale here: http://groups.google.com/group/culerity-dev/browse_thread/thread/6326c447c5d8706c .
Last edited by langalex,