[17:59] <botic> is there a little "howto ringojs on debian" in a blog/wiki/mailinglist posting?
[18:24] <olegp> I havent seen one
[18:24] <olegp> what are you trying to do? just install it?
[18:49] <botic> installing and running. it's working, but i needed some time to get all infos. we use a custom fs scheme at work, so it was a little bit confusing to find all stuff in seperate directories
[18:50] <botic> would be good to have a small doc about it, just some lines. maybe a description how ringojs.org is set up. hannes wrote something, but i didn't find it in the wiki
[19:00] <botic> maybe someone of the creators of the packages ;)
[19:00] <botic> can help/write.
[19:54] <earl> botic: what do you need?
[20:08] <botic> earl: if i want to run my little ringocaster app, i have to edit /etc/default/ringojs and change the following variables:
[20:08] <botic> RINGO_MODULE_PATH=/var/ringoapps/Ringocaster and APPLICATION_OPTS="-p 2604" to switch to a free port
[20:10] <earl> ok
[20:10] <botic> or is this the wrong way? sorry, i was too long in the frontend team ;)
[20:10] <earl> (so you're using the ringojs-daemon package)
[20:10] <earl> nope, looks just about right
[20:11] <earl> the daemon package, per default, runs the ringo/webapp/daemon module
[20:11] <earl> which in turn basically just executes require('config').app as JSGI app
[20:12] <earl> so you use the RINGO_MODULE_PATH to point to your app
[20:12] <earl> and APPLICATION_OPTS to pass additional arguments to ringo/webapp/daemon
[20:29] <botic> merci! it was a little bit confusing, that all stuff is seperated in different directories. my server and the server-config in my comp is more monolithic, so everything for helma would be in /usr/local/helma.
[20:30] <botic> mod_proxy does the rest. or would you recommend a different way to bring ringo/jetty and apache together?
[20:40] <earl> nope, proxying is just fine
[20:41] <earl> the debian packages are trying to blend ringo into the system
[20:41] <earl> if you prefer a different configuration, nothing forces you to use the packages, of course :)
[20:46] <botic> i know, but apt-get is so easy to use for frontend guys ;)