Hopbot log for 2009-04-10 - Helma IRC channel: #helma on irc.freenode.net

2009-04-10:

[7:07] <bard> hi, I was wondering, is there a way to start helma-ng apps interactively from the command line? i.e. instead of typing `java -jar run.jar apps/demo/main.js', type `java -jar run.jar' and then type something like `start('app/demo/main.js')' at the prompt
[7:14] <zumbrunn> that used to work
[7:14] <zumbrunn> I'm not sure if it still does in the same way
[7:15] <zumbrunn> before, you used to be able to pass the additional module path as argument
[7:15] <zumbrunn> (without pointing to a main.js)
[7:16] <bard> that still required knowing what you wanted to launch when starting the interpreter, right?
[7:17] <bard> I was looking for something that allowed to launch just `java -jar run.jar' and only later decide what app to launch
[7:17] <zumbrunn> hannesw: btw... the res.render problem gozala was talking about yesterday seems to indeed happen when following your instructions for running helma-ng on the google appengine
[7:18] <hannesw> zumbrunn: that's strange.
[7:18] <zumbrunn> bard: then you would only have the modules dir as your modulesPath
[7:18] <hannesw> bard: yes, but you have to set up the module path
[7:18] <zumbrunn> so, you would need to put your app code inside the modules dir
[7:18] <hannesw> starting with apps/demo/main implicitly adds apps/demo to the module path
[7:19] <bard> ok
[7:19] <hannesw> so you need to add that manually, or run from the application directory, or something like this.
[7:19] <zumbrunn> or is there a way to add to the modulePath from the command line?
[7:19] <hannesw> yes, i think it's in the README
[7:19] <hannesw> -Dhelma.modulePath=... i think
[7:19] <bard> yep
[7:19] * zumbrunn goes and reads the README
[7:20] <hannesw> zumbrunn: how do you know about the res.render issue?
[7:21] <hannesw> trying now...
[7:25] <hannesw> zumbrunn: shit! you're right.
[7:30] <hannesw> ok, fixed it now.
[7:30] <hannesw> not sure why this didn't happen in my tree... didn't have any uncommitted changes.
[16:36] <rsaccon1> hi all, trying out helma-ng on appengine, following the tutorial, but I get:
[16:36] <rsaccon1> Java class "org.mortbay.jetty.Response" has no public instance field or method named "charset".
[16:36] <rsaccon1> any idea what stupid thing I am doing wrong ?
[16:57] <rsaccon1> ok - I posted it on mailing list as well. Really interested in getting this running ..
[17:15] <zumbrunn> rsaccon: there was a problem before related to res.render, which was fixed
[17:15] <zumbrunn> and I haven't tried since then
[17:16] <zumbrunn> let me try to reproduce the problem you are seeing...
[17:16] <rsaccon> I checked it out again after I read about that
[17:17] <rsaccon> before I had a different error with wrong moduleName of the servlet, or something like that
[17:17] <rsaccon> zumbrunn: and thanks for looking into it ..
[17:23] <zumbrunn> hmm, nope, works fine for me now
[17:23] <zumbrunn> are you sure you replaced all the files with the new ones?
[17:24] <zumbrunn> http://objectengine.appspot.com/
[17:25] <rsaccon> zumbrunn: so any idea what one could do wrong ? I mean followed closely the steps in the tutorial, got other demos on apengine with eclipse running immediatley, I am mac OSX, it must be astupid little thing I misssed
[17:26] <zumbrunn> I'm on macosx as well
[17:26] <rsaccon> ok, will check, maybe I did not replace all ..
[17:28] <rsaccon> the tutorial says> js.jar, helma.jar and log4j.....jar
[17:28] <rsaccon> just these three, right ?
[17:28] <zumbrunn> yes
[17:28] <zumbrunn> maybe you forgot to rebuild helma-ng?
[17:28] <rsaccon> ant jar, I did
[17:28] <zumbrunn> ok
[17:28] <zumbrunn> plus the modules and demo dirs
[17:32] <rsaccon> ah, that I did not, let me do that as well (because again got that error)
[17:32] <zumbrunn> yeah, that will make the difference
[17:36] <rsaccon> yeah, thanks a lot, I knew it must have been a veeeeeeeery stupid thing I did wrong
[17:36] <zumbrunn> :-)
[17:37] <rsaccon> zumbrunn: you are swiss ? Your name sonds like
[17:37] <zumbrunn> yep
[17:37] <rsaccon> s/sonds/sounds/
[17:37] <rsaccon> where about
[17:37] <zumbrunn> http://zumbrunn.com/
[17:37] <zumbrunn> Mont-Soleil
[17:38] <rsaccon> I know
[17:38] <zumbrunn> bernese jura mountains
[17:38] <rsaccon> bin auch Schweizer, lebe zurzeit in Brasilien
[17:39] <rsaccon> sorry, cannot type fast in german anymore
[17:40] <zumbrunn> one would think helma could take off lake crazy in brasil
[17:40] <zumbrunn> people there seem to be crazy about javascript
[17:41] <rsaccon> things do not take off here, everything is slowly
[17:41] <zumbrunn> and with the hosting like google appengine and mosso.com, the cost barrier to jvm deployment is gone
[17:41] <rsaccon> how does it come you think so ? about javascript
[17:41] <rsaccon> yeah, that great
[17:42] <zumbrunn> my experience from orkut
[17:43] <rsaccon> as user or developer ?
[17:43] <zumbrunn> just from the javascript group there
[17:43] <rsaccon> ah, ok
[17:44] <zumbrunn> hannesw: mosso.com is pretty cool too for helma hosting, btw
[17:44] <rsaccon> yeah, they often don't join international comunities, form their own
[17:44] <rsaccon> but it is VM based, not ?
[17:45] <zumbrunn> a "cloud server" for something like $10 or $11 per month
[17:45] <zumbrunn> is what VM based?
[17:46] <zumbrunn> mosso.com?
[17:46] <zumbrunn> it's bassically like a virtual server
[17:46] <rsaccon> yes mosso.com
[17:47] <zumbrunn> where you can install an os (from a selection of linux distros) and have root access
[17:48] <rsaccon> like amazon EC2 ?
[17:49] <zumbrunn> kind of, yes
[17:49] <rsaccon> ok, looking at their site now ...
[17:52] <hannesw> zumbrunn: mosso.com doesn't seem that interesting to me
[17:52] <hannesw> looks quite expensive, from 100$/month upwards
[17:53] <zumbrunn> no the $100 are a flat fee option
[17:53] <zumbrunn> a 256MB instance with 10GB disk space is about $11 per month
[17:54] <zumbrunn> which I think could be interesting for small sites
[17:54] <zumbrunn> for people that would otherwise go with php
[17:55] <rsaccon> maybe. ec2 is about $70 per month
[17:55] <hannesw> hm, not sure
[17:56] <zumbrunn> the $100 option includes 24x7 phone support!
[17:56] <rsaccon> maybe just the sound of the waiting queue !
[17:57] <zumbrunn> lol, yes
[17:57] <zumbrunn> anyway, my point is, it is interesting for small sites, without that option
[17:57] <rsaccon> but rackspace has a good reputation for providing support
[17:57] <zumbrunn> yes
[17:58] <rsaccon> with their higher priced dedicated server offerings in the past, at least
[17:58] <bard> zumbrunn: 256MB with 10GB disk at 11$ but bandwidth isn't included iirc
[17:59] <zumbrunn> for small sites, bandwidth is not an issue
[17:59] <zumbrunn> not at 22 cents per GB, anyway
[18:02] <bard> true. still, used bandwidth being equal (assuming 100 in, 100 out) the same plan costs less with slicehost
[18:03] <zumbrunn> right
[18:03] <bard> (perhaps I should point out that an app on my server went crazy two months ago and made me exceed my monthly quota, thus I'm speaking out of paranoia :))
[18:03] <zumbrunn> :-)
[18:05] <bard> any opinions on the pro/cons in self-hosting a helma-ng app with couchdb as backend vs. hosting on google app engine?
[18:05] <zumbrunn> not yet
[18:21] <zumbrunn> of course, one thing that will not change with experience is the philosophical difference
[18:22] <zumbrunn> whether you want to be in control of your full software stack or whether you want to built on top of a proprietary platform
[18:25] <bard> zumbrunn: absolutely. what I'm trying to balance is the difference in getting to the point of deploying something and not being able to because of overhead eating away the already little available time. appengine _looks_ like it could cut on the overhead.
[18:28] <bard> bbl

 

 

In the channel now:

Logs by date: