Services

Custom images

Configure a custom container based on the Common Lisp image of your choice: a free kit to build yourself, or built here for mites.

What is free, and what takes mites

A mite is the unit of the community pot: one pot for all the house's services, drawn on by everyone who uses them and topped up by anyone who can. Today USD 10 puts 1,000 mites in. What a service costs in mites, and what a mite costs, may change at any time.

Free: A kit from the form — fill in the form yourself and take the files: build them on your own machine, as often as you like.
Mites: Prompting the agent — each answer draws mites, by its length.
10 / arch: Build it to pull now — the site's runners build the kit, 10 mites for each architecture. Deleted after 2 days: pull it before then.
20 / arch: Build and keep it 30 days — the site's runners build the kit, 20 mites for each architecture. Kept in the registry 30 days.

The agent and the builds are not switched on here just now. Kits from the form are free, as always.

Fill in the form yourself

Pick a base, name the systems, and the site writes the kit's files.

Name

Base image

Architectures

amd64arm64

Quicklisp systems (names, separated by spaces or commas)

Quicklisp dist (a date, or latest; Gendl brings its own)

Debian packages (optional)

Run at start (optional: package:function)

Ports (optional)

Save a core with the systems loaded (SBCL and Clozure CL)

Also an overlay for a stack (Gendl bases)

Free: you get the files, to build on your own machine. The kit's page can also build them here, for mites.

Or prompt for it

The agent is not switched on here just now. The form above makes the same kits.

What a kit holds

image.sexp — the single source of truth (SSoT): what the image is
generate.lisp — makes every other file from it, with any Lisp
Dockerfile — the base pinned by digest, Quicklisp by dist
build.lisp — loads the systems, saves the core
build.sh — one machine, or both architectures joined
.gitlab-ci.yml — the same, on GitLab CI
README.md — what it is and how to reproduce it

The bases are the Lisp implementation images this site builds, and images contributed by the people who make them. Have one you would like listed? Offer it.

Proposed

Kept, and shared

A kit's page can already build it here, from the community pot. Under consideration next: keeping a built image in the registry month after month, on a subscription; rebuilding it when its base gets a security fix; and, if you choose, listing it here as a contributed base for others to build on.

Say you would use it

What you type to the agent is kept, with the kit it led to, to improve the service; your address is not. Card details and any receipt address go to Stripe, the site's payment processor, and are not kept here. More on privacy.

Something wrong or missing here? Edit this page on GitLab.