Hi all,
As you all have noticed, I've been working to clean up common-lisp.net and
simplifying the administration process.
One of the things we have done is that we implemented a deployment pipeline
for the common-lisp.net main site using GitLab. It's been a great joy to
work with it so far and made deployment of new site content easier than
ever before.
*My proposal is to set up a GitLab CI based deployment pipeline* for *all
common-lisp.net <http://common-lisp.net> projects*. Meaning that I'm
proposing to import the current project pages (/project/*/public_html) into
GitLab repositories (<project-name>-site) with a gitlab-ci file which
causes the content to be published.
The approach above will mean simple import of the existing static content.
However, after import, the static output can be replaced by different input
and a static content generator, just like we did with the common-lisp.net
site.
Eager to hear your thoughts,
Erik.
Hey there folks.
I was browsing the community page of the website at noticed that the
link under "more" to "The Common Lisp Directory" (cl-user.net) seems to
now be a russian porn site.
I would suggest removing it since it no longer seems to be related to
common lisp to say the least.
// Eric Skoglund
The mailman process for <armedbear-devel@…> seems to be stuck, as my message from Thu Nov 14 14:20:35 2019 is still in the <file://common-lisp.net/var/lib/mailman/qfiles/in/> folder as
<file://common-lisp.net:/var/lib/mailman/qfiles/in/1573741236.036276+76a6544dfb6c1226d9e9765b78b199d910f4d0a7.pck>
If this in indeed the outstanding incoming queue for mailman, it contains 1729 messages that haven’t been processed since Oct 27 19:30.
I am now looking for how mailman processes this queue, slowly working through how to fix as I get the time, but if someone (Erik?) could step in to take a look to save me the unknown amount of time to figure this out, I would appreciate it.
We’ll see if this message gets delivered…
--
"A screaming comes across the sky. It has happened before but there is nothing
to compare to it now."