UCW is a beast to set up. Don't even think about getting it to run on a naive Debian Sarge installation with the shipped lisp libraries. Fortunately, they do provide a
boxset in the meantime, which eases the pain a considerable bit.
But even with the new
tutorial,that also ships with the boxset, I had to dig quite a bit around how I make my new test application known to ucw.
/etc/ucw/applications.d? No.
path-to-ucw-boxset/ucw_dev/etc/conf.lisp? No.
path-to-ucw-boxset/ucw_dev/etc/start.lisp? No. Finally, adding to
path-to-ucw-boxset/start.lisp did the trick, as should have been obvious to me as I fire up UCW by
sbcl --load path-to-ucw-boxset/start.lisp. Oh well. And I haven't even started to move the UCW configuration to use
mod_lisp.
And of course, the boxset messes around with your
ASDF settings, which it has to, otherwise it would run with the different versions of it's more common libraries. You'll not only need to add your private apps system file to where the boxset expects it (or mess around with the setting of the default-registry in (one of the) conf file) but you'll also need to additionally add (links) for all additional CL libraries (say CL-SQL) your app depends on. That's not funny but a royal PITA as it means you'll do very stupid Unix sysadmin tasks instead of fun web programming with UCW.
