Hi Everybody

Happy (Hacking) Holidays.

Ok. I am back doing this. Thank you Erik and thank you Ray for the tutorial :)

Let me understand how I need to proceed. But first let me tell you how I was working before.

In the past I would load my docs to my local clnet home and the I would copy them to the /project/public_html.

As I use (shameless plug) HELambdaP to generate the documentation (* and ** below), I can keep everything in my folders and not use the .gitlab-ci.yml thingy.

Now I have the following problem, which I believe is affecting me (and others) either with or without .gitlab-ci.yml: the new projects do not have a "group" (a UN*X group) created automatically, which is what I was also hinting at with my first message. Cfr., my last project 'with-contexts'.

If I were to create a 'with-context-site' project in Gitlab, I would still have to ask you (the admins) for the creation of the 'with-context' group. My feeling is that the old ways were better, although I do not know what that entails about Gitlab "groups", which, I presume, are different from UN*X groups.

Now: is the move to Gitlab sites mandatory? If so, does that mean that we will need to have TWO projects going on separately? I.e. 'myproject' and 'myproject-site'?

If the move is not mandatory, will the old way of manually copying documentation to '/projects/myproject/public_html' still work (provided that the 'group' was there)?

Before I conclude let me ask something else. (*) HELambdaP lives in sourceforge.net (http://helambdap.sf.net); a leftover from the CLNET interregnum, when things ceased to work (same for CLAST); I want to move it to CLNET and I will get around to do it. The question (**) is whether it would be possible to set up a job/task/whatever in common-lisp.net that would run it unattended. Since CLNET has a SBCL available (***), I suppose I could run it with an init script and have it ready to go, but wouldn't it be nice if the CL instance(s) running on CLNET, had Quicklisp running, so that HELambdaP (shameless plug again!) were just a quickload away? Or better, had the quickload in the instance init file? Maybe that would create issues between "site" quicklisp and "user" quicklisp, but it'd be nice to have.

All the best

Marco

(***) Can we have ABCL, ECL, CMUCL etc also installed? Just asking...

On Sun, Dec 13, 2020 at 7:27 PM Erik Huelsmann <ehuels@gmail.com> wrote:

Hi Ray, Everybody,

On Sun, Dec 13, 2020 at 7:10 PM Raymond Toy <toy.raymond@gmail.com> wrote:

On Sun, Dec 13, 2020 at 9:51 AM Erik Huelsmann <ehuels@gmail.com> wrote:
Hi Marco,

As for deploying static pages, when you refer to "the instructions", do you mean the ones at https://common-lisp.net/faq/using-gitlab-deploy-project-pages ? If so, here's a working example of the simplest static site deployment you can get through GitLab for your project/group: https://gitlab.common-lisp.net/cl-couch/cl-couch-site

If, like me, you didn't know where the published site is: http://common-lisp.net:/projects/cl-couch. The cl-couch repository should include a link.

Added a description to the repository which includes a link to the site (I've tested the link and the one above has 2 typos; the correct link is: https://common-lisp.net/project/cl-couch ).

A slightly more complex example is at https://gitlab.common-lisp.net/cmucl/cmucl-site for a site you're probably familiar with. In addition to the site, this also regenerates all the cmucl docs in html, pdf, and info format if possible. Thanks to Erik for helping set this up years ago! It's made it much easier since everything is automatic now instead of doing it by hand like I used to.

Good to hear the setup works well for you!

I hope I can help Marco get set up in a similar fashion.

Regards,

Erik.

--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.