[Bese-devel] UCW on OSX with mod_lisp
lists at infoway.net
Fri Sep 1 22:29:23 UTC 2006
Well, I have to say, I guess this is what happens when you skim
through the text without reading everything carefully. In the same
tutorial link, the author writes:
"... As mentioned in the previous chapter, the ucwctl/applications.d
mechanism will probably disappear. A simpler way to start ucw is to
just load start.lisp in your lisp or directly through detachtty. You
can change beforementioned variables (for example which backend to
choose or on which port to listen) in /path/to/ucw/src/vars.lisp. ..."
Therefore, since I'm not using the ucwctl tool, I should have
modified the vars.lisp file.
I now modified that variable and everything works. Apache+mod-lisp
and by simply putting my applications in /etc/ucw/applications.d,
they are automatically loaded.
On Sep 1, 2006, at 6:11 PM, Daniel Salama wrote:
> Removing the quote didn't solve it. Still the same behavior.
> Just to be more detailed:
> I just downloaded the latest ucw version:
> ~/dev/lisp $ darcs get http://common-lisp.net/project/ucw/repos/ucw-
> ~/dev/lisp $ cd ucw-boxset
> ~/dev/lisp/ucw-boxset $ sh get-all.sh
> ~/dev/lisp/ucw-boxset $ vi ucw_dev/etc/conf.lisp
> ~/dev/lisp/ucw-boxset $ sbcl --load start.lisp
> On Sep 1, 2006, at 6:03 PM, Attila Lendvai wrote:
>>> (setf *ucw-backend-type* ':mod-lisp)
>> you don't need the quote there:
>> (setf *ucw-backend-type* :mod-lisp)
>> this may solve it, but looking at the code suggests that you should
>> have seen this error:
>> (error "~A does not specify a backend." backend-spec)
>> - attila
>> "- The truth is that I've been too considerate, and so became
>> unintentionally cruel...
>> - I understand.
>> - No, you don't understand! We don't speak the same language!"
>> (Ingmar Bergman - Smultronstället)
> bese-devel mailing list
> bese-devel at common-lisp.net
More information about the bese-devel