ok, I bit the bullet and created the "with-contexts-site" repository.

No pages generated. No joy.

I may have some other problem in my .yml file for sure (how do I debug that?), but re-reading the instructions (https://common-lisp.net/faq/using-gitlab-deploy-project-pages) I see that there may be a bit missing in the very first step, where a "group" is mentioned. Which brings me back to the initial question I had about gitlab vs Unix groups.

Now. I presume that to fix the current issue, a "with-contexts" group could be created somewhere (Gitlab and/or Unix) and maybe the pages will be generated. However, this raises some other questions (which I will address later).

All the best

Marco

On Tue, Feb 23, 2021 at 2:43 PM Marco Antoniotti <marco.antoniotti@unimib.it> wrote:

Hi

I got back to this after some time.

So. I added the .yml file to the 'with-context' project and hoped it worked. Alas, it did not.

Now the question is what went wrong.

Is it because I insist on trying NOT to have a separate repository for the documentation? Anything else I can do?

Thanks

All the best

MA
On Mon, Dec 28, 2020 at 8:22 PM Erik Huelsmann <ehuels@gmail.com> wrote:
Hi Marco, Ray,
On Sun, Dec 27, 2020 at 7:16 PM Marco Antoniotti <marco.antoniotti@unimib.it> wrote:
Hi Ray

I just checked writing the /project/myproject/public_html. It works for old projects.

That's correct. I've asked project owners to move their site maintenance to GitLab; not all have found the time or inclination to do that and one or two pointed out that the new way of working would pose a problem for them.
The current setup is to return pages from /project/*/public_html when that exists or to serve the pages from <project>-site alternatively.

[ snip ]
The updated OOK doc pages get loaded as expected (as you can check).

I will have a look at the alternative setup for the "new", Gitlab-started projects as you suggested. I kinda wanted to avoid peppering the source tree with exogenous stuff like the .yml one.
However, from what I understand from the cl-couch, cmucl-site and maxima-site examples, it should be sufficient for me to add
pages:
  stage: deploy
  script: mv docs/html public
  artifacts:
     paths:
       - public
  tags:
    - site-gen
  only:
    - master
to, say, the with-context top directory? Or could I add it to the docs subdirectory only (changing the script entry)?
Yes, that's how it works (from the top directory, that is). The name of the repository/project should be with-context-site. The text after the "script:" key can be any command that needs to be executed in order to produce a top-level directory named "public".

Just asking for reassurances before trying it out...

All the best
Thanks for your help

No problem. You're welcome. In case of more questions, don't hesitate to ask!

Marco

PS I understand the issues with having more than one CL implementation installed. No problems there...
We could look at having Docker images with the various CL implementations, which would allow you to choose your favorate implementation of the day. Not sure how easy it would be to make it available for CMUCL though.

--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
--
Marco Antoniotti, Associate Professor tel. +39 - 02 64 48 79 01
DISCo, Università Milano Bicocca U14 2043 http://bimib.disco.unimib.it
Viale Sarca 336
I-20126 Milan (MI) ITALY