clo-devel July 2017

clo-devel@common-lisp.net

3 participants
5 discussions

Re: Maintenance of closure-html
by Erik Huelsmann 06 Sep '17

06 Sep '17

Hi David, Thanks for the quick response! Elias, looks like you got the job! Could you send us your SSH public key (through admin(a)common-lisp.net), please so I can create a user account for you to maintain the project website at common-lisp.net/project/closure-html ? Thanks! Regards, Erik. On Wed, May 3, 2017 at 7:50 PM, David Lichteblau <david(a)lichteblau.com> wrote: > (Cc: Elias) > > Quoting Erik Huelsmann (ehuels(a)gmail.com): > > You are listed as the current maintainer of closure-html. We (the > > common-lisp.net admins) have been approached by Elias Martenson who > wants > > to take over maintenance. > > He could not reach you (received no response?), so I'm trying to reach > out > > and see if you are ready to share or hand over maintenance. > > > > Please let us know what we can do. > > Sure, go ahead! Thanks for reaching out. > > For the future maintainer -- The canonical repo for closure-html used to > be, until now: > http://repo.or.cz/closure-html.git > > Let's instead move it to > https://github.com/bluelisp/closure-html > > where we have started to collect other projects that could use some > affection by other community members. You should have received an > invite to that team on github. > > We can inform Zach about the repo change once everything is in place. > > > d. > -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

3 3

Cannot log in as vsedach@common-lisp.net after added SSH key to Gitlab
by Vladimir Sedach 15 Jul '17

15 Jul '17

Hello, I ran into a strange problem: I added a new ed25519 key to authorized_keys2, which worked fine. Then I went to Gitlab web interface and tried adding the ed25519 key, which failed because Gitlab cannot handle ed25519 keys yet. I made a new RSA key and added that in the Gitlab web interface. After this I cannot log into vsedach(a)common-lisp.net with any of the keys that were in authorized_keys2. The error message is "Permission denied (publickey)" so something must have happened to the authorized_keys file. This seems very strange. I do not think I did anything as vsedach(a)common-lisp.net that would break log-ins, which leads me to believe that it was some script in Gitlab. OTOH the new RSA key does not work either, so it might be something I did through TRAMP by accident. Can you please put this SSH key into authorized_keys: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDc+4x1XblOzyfHAzOCbM00FB/VglYg0PvOSL8FuQKQ/ vas(a)t43.lan. Thank you, Vladimir

3 3

common-lisp.net maintenance: ugraded - what's new?
by Erik Huelsmann 15 Jul '17

15 Jul '17

With respect to the regular services, GitLab was already receiving at least one upgrade per month and security upgrades were being installed as they were released by Debian (automatically). With the upgrade, the system is running a recent version of the Debian distribution again (Stretch). Stretch comes with Apache and Nginx versions which support HTTP/2 out of the box and as we were running common-lisp.net on TLS for a long time already, HTTP/2 is now turned on for all common-lisp.net subdomains. Mail transmission has been configured to use the official common-lisp.net certificate. The new distribution comes with a kernel which is recent enough for container support. Among the next steps, we'll research moving to Mailman3, which comes - as an option - in Docker containers and a much more modern web front-end as well as internal architecture. For those who like to know about the migration strategy for the upgrade: over the past weeks we created a copy of the VM running common-lisp.net and other services. On that copy, we ran a script for an automated upgrade. When the upgrade didn't succeed or didn't complete automatically (that is, required manual intervention), we changed the server configuration and the script. This process went on until the upgrade completed successfully and without intervention. Once successful, the configuration was tested and adjusted for the target software versions. The adjusted configuration was automatically installed after the upgrade process today, followed by a reboot to return service. The migration interval of 3 hours was based on the experience gained from this exercise. In the mean time, a separate VM was installed on the IP pointed to by common-lisp.net, ensuring that even if services would temporarily be up during the migration, no users could accidentally access those services. Thank you for your attention! Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

Heads up: common-lisp.net unavailable tomorrow morning (CET)
by Erik Huelsmann 15 Jul '17

15 Jul '17

Due to major maintenance, common-lisp.net will be unavailable tomorrow between 9 and 12am CET on Saturday July 15. Regards, Erik

1 1

Migrating common-lisp.net to Debian Stretch
by Erik Huelsmann 09 Jul '17

09 Jul '17

Hi all, Over the past weeks, I've been working on a migration from our current OS version to the current stable version as recently released by the Debian project (Stretch). While the time hadn't come to migrate earlier, today I found that the GitLab project released its Stretch packages, meaning that now all the third-party prerequisites are in place to migrate. Today I worked to automate the migration and by the end of today, I'm now able to run an automated migration without manual intervention. I'll leave a copy of the current machine running for a few days to see if it remains stable. If all goes well, it's my intent to take common-lisp.net offline for a few hours coming Saturday (Saturday July 15) in order to run the migration script on the live system instead of on a backup. Before the upgrade starts, we'll take a snapshot of the drives and make sure users won't have access to the system during the migration. Although I've run through various tests already and will continue to do more testing over the coming week, the system might have some instabilities in the days after the migration. When you experience any of those, please report here or to the admins (admin@common dash lisp dot net). Thank you for your patience and continued support/use! Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

clo-devel July 2017