World: r3wp

Tryed stunnel once, had stability issues, but that may have been 
me or OSX implementation..

Wel I am afraid it won't be so easy with nginx either.. I need to 
take a break , I will try again in the evening.. if anyone succesfully 
setup chained ssl certs with stunnel .. any hint is more than welcome

I got the nginx running with my cert ... I got the same error as 
stunnel , but then I found that my cert must be first and other in 
chan are later .. reverse to some examples on net and to stunnel 
examples (maybe there is the same thing?)

now I need to make it reverse proxy to cebelca

Yay it works !!!

screenshot of latest version of cebelca btw: http://www.refaktor.si/blog/img/cebelca.biz.norm.png

I wrote a how to on setting up stunnel with cheyenne a couple of 
years ago ... it was easy.  Now i just have to find where I published 
it!

Could be useful to have on the cheyenne site.

Graham .. did you have multiple certificates (root intermediatte 
and yours) ?

nginx rules!

no.

SVN revision 12: Response/redirect default code changed to 302 (issuing 
a 303 could cause unwanted effect on HEAD requests). /TEMP option 
replaced by /STRICT for sending back code 303. RSP API documentation 
updated accordingly.

I use lighttpd and reverse proxy to Cheyenne. Works great.

Has anyone created a RSP site where every page can be edited via 
the browser?  I think rebol.com is like that ...

SVN r13, minor fixes :

 o RSP: fix for scripts not returning any data (test.rsp: <% 1 %>)	

 o RSP: words in sandbox context renamed to lower the risk of collision 
 with user script words.

Maybe a rebol-to-json function couldl be included into Cheyenne  
...

If we can get one that works!

:-)

working on it  ;-)

yess... done !

JSON built in Cheyenne: (replying in javascript channel)

I thought I'd just mention it here... a it's a bit odd, and perhaps 
not entirely reproducible.  But I got my JS calendar working.  But 
I could not see any data coming in from my rsp script that was pulling 
data from the db and sending it back as json until I put some debugging 
statements in .. and then it works.  Bizarre.  Or some browser cache 
issue.

Just using a few ?? to log to the trace.log file so it wouldn't even 
be seen by the calling script ...

You can test if it's a browser cache issue by requesting the script 
using the READ function from REBOL console. Can you make a small 
standalone RSP script that  shows this issue?

heh ..  I don't think 'read evaluates JS :)

the docs say you can set the timeout to whatever in the webapp httpd.cfg 
but when I set it to 2:00:00, it still times out well before that.

Where's the curecode for Cheyenne?

Not back online yet.

This works for me :
	webapp [
		virtual-root "/testapp"
		root-dir %www/testapp/
		auth "/testapp/login.rsp" 
		timeout 02:00:00
	]

ahhh.... mea culpa

I used timeout: 02:00:00  .. ie a set word

that should rise an error when starting with -v

SVN r15

FEAT: scheduler lib added
FEAT: 'job config keyword added (CRON-like jobs)

FIX: cheyenne freezing on exiting (only if config reloading was used)

Warning: the scheduler integration with Cheyenne is at beta stage, 
minimaly tested, so if you want to put it in production, take the 
time to test it well.

I've noted in my todo list to extend the RSP API to be able to add/delete 
jobs (for now, the list is static, loaded from config file and cannot 
be accessed from RSP).

FEAT ??

Do you mean "Done ?

FEAT[URE]

yes, means done

Doc - does Cheyenne already enable setting handlers for particular 
filetypes? I mean - equivalence to:

AddHandler rebol-cgi-dispatch .html
Action rebol-cgi-dispatch /cgi-bin/rebol-cgi-dispatch.cgi


For Cheyenne only users, it is not important, they can use RSP, but 
for those who want to have chance to migrate between Apache and Cheyenne 
in CGI mode, it might be usefull. I expect it not being a priority 
for you though ...

But the scheduler is still very fresh, no logging, not much tested,...

Need to check the sources, I don't remember how far we are now.

Currently there's only URL=>script aliasing available, but looking 
at the ALIAS code, I think that : 
	alias ".html" /cgi-bin/rebol-cgi-dispatch.cgi

might work (need to be tested). Do you really think that there's 
much users waiting for that feature?

Is this scheduler part of Cheyenne or Uniserve?  Just not sure what 
it has to do with Cheyenne

Is it to give those tasks hanging around something to do :)

Something I'd like to do is run a backup of my database, compress 
it and upload it to S3.  I use a script for that at the moment .. 
so maybe I can use the scheduler.

Doc - I don't know. But how I got myself to such a solution? Simply 
put - I never got past CGI usage. It is quite comfort and OK for 
small to middle sites. But I wanted to have also index.html being 
a dynamic site, not just some /cgi-bin/my-subpage.cgi?here ....

Your RSP solution might be fine, but if someone wants to feel secure 
= having ability to migrate back to Apache set-up, it will not work.

Petr, in any case, you can "extend" Cheyenne feature-set by using 
a front reverse-proxy (nginx, lighthttpd, stunnel, apache,...).

Scheduler is a standalone library. Cheyenne uses it to manage jobs 
defined in config file. UniServe will use it for example, to retry 
sending emails after x minutes.

The scheduler doesn't spawn any new process by itself. When you specify 
an action, you can use CALL or LAUNCH in the action code to run your 
task in background. You can also use a URL pointing to a local CGI 
or RSP script (making it run in the background using one of the task-master 
worker processes).