Closed wezm closed 13 years ago
Did you add a route to the app.yaml file?
Also, I's avoid using a jruby rvm. Dubious does not use jruby at runtime, so this seems to complicate things.
The Unable to access https://appengine...
error is a red herring--that happens whenever there is no net connection and doesn't affect the local server.
It may be that you are running into a java incompatibility issue. 1.6.0_24 was causing issues for people using the appengine-sdk a month ago--it might be related to that http://groups.google.com/group/appengine-jruby/browse_thread/thread/d9fdf54b629ad46f
I did some more testing last night and tried running the java command that rake server ends up launching. It turns out that java is segfaulting as described by @baroquebobcat above. So I guess I'll put the dubious experimentation on hold until Apple push out a new java update.
This week, I hope to push out a work-around for that.
I installed jruby via rvm, then did gem install dubious, which went as planned. I created a new project and copied the InfoProperties controller from the examples and added a route for it. Running
rake server
(without an Internet connection, hence the update failure) outputs the following:A few seconds after that last line rake exists and I'm returned to my shell (zsh). I'm running Mac OS X 10.6.7, Java from Apple (Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326)),
rvm info
: