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.
Hi,
It's been announced that Debian Buster will be released in the beginning of
July. While there's no immediate hurry to upgrade, there's definitely one
good reason to start working on an upgrade: Python 2 will be completely
decommissioned in 2020 and our mailing list infrastructure runs on Mailman
2 which runs on Python 2.
Debian Buster includes the new Mailman (Mailman 3) -- which runs on Python
3. Mailman 3 isn't just an upgrade to Python3, but a complete
re-architected Mailman. Mailman consists of 4 independent applications in
version 3. One of those is the mailing list archive manager.
Since we'll need to migrate our old mailing list archives to this new
infrastructure (and preferably keep the URLs stable), the migration may be
quite a bit of work to prepare. So, I'm looking for people who can help
out: find out which *exact* steps we have to go through to get minimal
downtime on an upgrade and get back to a stably running system on return.
Comments? Volunteers? Proposals?
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
