I use files and quicklisp when developing, but deliver and provision binary images.
Most of my apps are web based, and i run the lisp image behind runit, a service manager that handles logging as well as startup and shutdown, and restarting the image if it crashes. It also makes rolling back a release trivial, modulo database schema changes. I don't use anything like cl-launch or buildapp, if only because these tools didn't exist in a usable form when i started, and i haven't had a good reason to change. Quicklisp, OTOH, has changed the way i work significantly. With the exception of production instances, most of my code is deployed via a load.lisp script that explicitly lists and loads dependencies from QL, where before libraries were kept in version control. I'm also using more libraries these days. So, i'm both, but primarily a filer these days. Cheers, drewc On 20 January 2011 07:45, Ala'a Mohammad <amal...@gmail.com> wrote: > Hi, > > I'm continually learning Common-lisp and trying to find the best style > that suites me better. I've tried 'an imager' style (cooking a an > image with all required libraries loaded when required), and 'a filer' > style (loading files or systems each time I fire-up a CL > implementation). I'm interested to hear what others use CL. How do > they manage day to day work? how do their preferred style mesh into > their production pipeline (coding, debugging, deployment and > maintenance)? and what makes them prefer one way over another or the > mix if applicable? > > Regards, > > Ala'a Mohammad. > > _______________________________________________ > pro mailing list > pro@common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/pro > _______________________________________________ pro mailing list pro@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/pro
