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.
In, for example,
https://gitlab.common-lisp.net/cmucl/cmucl-site/-/jobs/1316, there's a
note on the right that the job artifacts expire in 3 mo. There's also
three buttons for keep, download, and browse.
So, if I run CI for the latest changes and don't touch the site again
for 3 mo, all the generated pages will disappear? That would be bad
if the webpages disappeared after 3 mo. It would also be annoying if
I had to make changes at least once every 3 mo to keep the site up.
How does this work? Googling for this didn't actually answer this
question, except to say I can set expiry_in to some large value to
preserve the artifacts.
--
Ray
