Forum OpenACS Q&A: Project Manager Problems

can't use non-numeric string as operand of "!"
    while executing
"if {!$edit_p} {
        # now set up dependency options

        for {set j 1} {$j <= $number} {incr j} {
            if {![string equal $current_numb..."
    (procedure "pm::task::options_list" line 38)
    invoked from within
"pm::task::options_list  -edit_p $edit_p  -task_item_id $task_item_id_arr($i)  -project_item_id $project_item_id_arr($i)  -dependency_task_ids "$my_dep..."
    ("for" body line 63)
    invoked from within
"for {set i 1} {$i <= $number} {incr i} {

    # ----------------------------------------------------------------
    # reading this code, you may wond..."
    ("uplevel" body line 623)
    invoked from within
"uplevel {
          ad_page_contract {

    Add/edit form for tasks

I'm on vacation now, so I won't be able to get to this for a few days. If anyone else has commit access and wants to commit it, please do so.

There are only two or three cases in Jade's application that I found causing a problem so it would be a shame to take a hard line on it.

Personally I would like very much to upgrade my Aolserver but as yet I have not had time to test out the virtual hosting - and ad33.13 with nsunix is so reliable that there really has not been any imperitive.

Do you know whether Aolserver 4 can be configured as proxy to pass the requests direct to each domain server as with nsunix (so that each server can log the requests in full), or would I be stuck with the old limitations of nssock?

Regards
Richard

I've been using V3 Beta 17 on my development machine for some time now and it appears rock solid, but it is still officially beta so a move to AOLS 4 would mean that folks who want https would need to use the beta or stick to AOLS 3 and pre 5.2.

    - Steve

However, I am clearly not the only one using nsunix, and the two compelling reasons commonly cited for continuing to use ad33.13 with Jerry's patches are:

1) Independent server threads which means:
    i) Can restart each independently of the others
    ii) If one crashes for some reason (which does happen) it doesn't bring all of your sites crashing down with it.

2) Ability to log traffic by domain - essential if billing for bandwidth based on the server request logs.

I for one would be really grateful if someone who has implemented virtual hosting with Aolserver v4.0 can clarify whether or not these needs can be satisfied with v4.0. That would remove the obstacles to upgrading.

Andrew very kindly posted a comment on bugtracker:

'Richard, I don't think what you're saying about virtual servers is accurate. AFAIK, AOLserver 4.0 can do everything with virtual servers that 3.x, plus more. The "more" is the 1 process virtual server model, of course, but nothing forces you to do it that way. Again AFAIK, no virtual server functionality was lost with 4.0, only additional functionality gained. (I have not actually done it myself, but that's my understanding.) If you haven't already, try nsvhr/nssock first, not nsvhr/nsunix. nsunix has always been trickier and not very well supported.'

Has anyone actually done this yet? If not, looks like I'll be doing it and posting the results!!

Also, does anyone know when nsopenssl is going to become a released version?

In the meantime, while there are obstacles, and while applications such as the Project Manager are still developing at a rapid rate, it would be a shame to create major issues for people because of very minor syntactic incompatibilities. I do understand however that we would be better off exploiting Aolserver's built in internationalisation support asap.

Regards
Richard

First, you can start a separate instance for each OpenACS installation, using 1 IP per installation.  For this, if you are using daemontools, you can just specify the initial tcl script for each instance.

Second, you can do the above, but use multiple ports on the same IP -- still having separate instances.  Then, you use Pound, http://www.apsis.ch/pound/  This is the method that Bart Teeuwisse advocates.

https://openacs.org/forums/message-view?message_id=169655

Or, you can run multiple instances using multiple ports, and use a slick little fix by Jade Rubick.

http://www.rubick.com:8002/openacs/easy_virtual_hosting

Or, you can use the virtual hosting built into AOLServer

http://www.panoptic.com/wiki/aolserver/98
also referenced
https://openacs.org/forums/message-view?message_id=189026

There are benefits and pitfalls to each method.  Currently I run a separate instance for two OpenACS installations that each have their own IP.  Then, I have five OpenACS instances running under one AOLServer instance on a 512mb machine and might consider pushing it too six OpenACS instances which I think is about the maximum practical limit for low-volume personal sites.

Jon Griffin on Jul 07 2003 19:39:03  [ reply | forward ]

Pound doesn't play nice with OACS or, for that matter any server that allows html streaming. I would advise against using it (unless they changed this in the last couple of months which I doubt).
Your APM pages will break as well as some others. Sorry.

Bart Teeuwisse on Jul 07 2003 19:45:10  [ reply | forward ]

Jon,

you are absolutely right. While Pound is small and fast, it doesn't work well with HTML streaming. I merly pointed to Pound as an example of accepting SSL connections to virtual servers.

/Bart
_________________________________________________________

Does that mean that the package manager functionality breaks with pound? What is meant by HTML streaming? Is this still an issue or has it been fixed?

Regards
Richard

this problem has been fixed in Pound 1.7. A current version of Pound works flawlessly w/ OpenACS including tDAV. Pound releases and the current development snapshot are available as tarballs from http://www.apsis.ch/pound/ or as a GNU Arch (http://wiki.gnuarch.org/) archive from the Code Mill (see http://www.thecodemill.biz/publications/blog/one-entry?entry_id=10095).

/Bart

Which Linux distribution and version of OpenSSL are you using?

Thats sounds good - we can view beta17 as a release candidate and look forward to the production release so,eti,e soon. All we have to do now is document the config for OACS. As your aware its a bit more sophisticated than v2. 😊

I'm happy to post a snippet of my config if people want to crib it. Its a simple beast just using one sslcontext but it seems to work.

    - Steve