quicklisp-projects VS caveman

Where is it getting that system name from though? I thought quicklisp used project dir names: https://github.com/quicklisp/quicklisp-projects/blob/8aa3500e9c3c3c7e03e76675410008b7e4c4c42f/projects/jzon/source.txt

The tracking issue for adding cl-djula-svg to quicklisp is here. You may want to check it for any updates.

Why do you need to build them in when you can just load your favorite libraries that do these functions with https://www.quicklisp.org/ , especially for http the great libraries by Fukamachi: https://github.com/fukamachi parallel processing: https://lparallel.org/ etc.

I'm very grateful that common lisp does not version up (like python), but you can always load a new or newer version of libraries with no impact on your core production code. (Such as a rewrite when the language gets a new version - this never happens with Common Lisp)

QUICKLISP comes with a regularly updated software distribution, see quicklisp-projects. This software distribution is pulled once when QUICKLISP is installed and can be later updated with (ql:update-all-dists). Once a project is added to the QUICKLISP dist, its updates are also added regularly and are available to users who care of issuing (ql:update-all-dists).

Testing on quicklisp-projects

The Common Lisp bindings to GTK can be installed with Quicklisp. If you don't already have Quicklisp installed, it's painless. See the Quicklisp website for more details, but here's an example of installing Quicklisp on Debian and configuring SBCL. The steps should be the same for any Linux distro and macOS.

I've noticed that beta.quicklisp.org no longer resolves. Neither does https://www.quicklisp.org/. What's going on?

As for the packages themselves, you can look at the repository information for each package at https://github.com/quicklisp/quicklisp-projects and use that to get the packages yourself manually. Most of them just use the latest commit in the package's respective git repos. A few use specific tags. Some, have to be gotten by other means. It is always possible, by looking at the quicklisp update data listing all the packages, to get the url for the package tarballs on the quicklisp server and download them manually.

We are going to walk through the examples by building an online Warehouse management system using Caveman

Djula is a port of Python's Django template engine to Common Lisp. It's the default templating engine used by the framework Caveman for building web applications

Appreciate it. Can I ask one last thing. Between Snooze and Caveman2, which is the more current project?

This is interesting from a "look what we can do!" perspective, but practically speaking, I'm not sure there's a good reason for doing it this way. For all practical purposes, it would be better to use one of the "native" Common Lisp libraries for doing this, such as Caveman: http://8arrow.org/caveman/

Even as a big Common Lisp fan, I would really question using it in a situation where the project has strict requirements to use a particular framework for another language.

In this post, I am going to walk you through to setup Tailwind CSS for a Common Lisp web application using Caveman. If you want to know more about creating web applications using Common Lisp and Caveman, please check my previous posts on the topic.

We are going to use Caveman for scaffolding this project. Caveman is a lightweight web application framework created by Eitaro Fukamachi for Common lisp. Caveman is available on Quicklisp, so you can install it with:

Hence I chose Caveman for this project. After having been played around with and without Caveman for building web applications in Common Lisp, I found that it is the best framework out there for developing web apps in Lisp. Caveman is a lightweight web application framework created by Eitaro Fukamachi for Common lisp. Fukamachi has got some serious tools for doing web development in Lisp. Please feel free to check out his Github profile for more useful tools.

I have been trying to come up with a standard template using Caveman to deploy on Heroku. But I am struck with these issues, not quite getting it to work with the available buildpacks. Lot of the related articles are hopelessly outdated. Appreciate any help or pointers? https://github.com/fukamachi/caveman/issues/126 https://gitlab.com/duncan-bayne/heroku-buildpack-common-lisp/-/issues/6