clo-devel May 2019

clo-devel@common-lisp.net

6 participants
4 discussions

Proposal: project pages deployment through GitLab
by Erik Huelsmann 18 Nov '20

18 Nov '20

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.

5 8

GitLab says my account was blocked, how to unblock it?
by Alexander Artemenko 30 May '19

30 May '19

Hello, guys! When I try to sign in using my github account ( https://github.com/svetlyak40wt) it says it is blocked. Could you unblock it please? -- Alexander Artemenko Creating MVP and prototypes. Common Lisp & Python https://github.com/svetlyak40wt

2 1

aclocal, autoconf, autoheader and automake
by Raymond Toy 22 May '19

22 May '19

Can we get aclocal and the other tools above installed? I'm updating cmucl's site to use the latest dev version of texinfo (6.6dev) to get better support for multi-level indices. So I'm building 6.6dev locally in gitlab CI and therefore need all the autotools to build it. I guess the alternative is to make 6.6dev available somewhere on c-l.net, but that's a bit of a burden to have available on c-l.net. Hence, I"m building it myself for CI. -- Ray

2 4

(no subject)
by Dave Cooper 10 May '19

10 May '19

Hi, I just changed phones and installed Google Authenticator on the new phone, and migrated my Google code to the new authenticator. But my common-lisp.net code (and some other ones e.g. Cloudflare) are still on the old phone. But the common-lisp.net one (on the old phone) doesn't seem to work anymore. Is there a way to migrate this to a new phone without logging in (I doubt it). If not, can the admin temporarily disable my 2FA so I can get in and set it up on the new phone? -- My Best, Dave Cooper, david.cooper(a)gen.works genworks.com, gendl.org +1 248-330-2979

4 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel May 2019