<div dir="ltr"><div>Hi Ray</div><div><br></div><div>I just checked writing the /project/myproject/public_html.  It works for <b>old projects</b>.</div><div><br></div><div>Here are the specifics (I am running this on the clnet machine)<br></div><div><br></div><div><span style="font-family:monospace"><i>mantoniotti@common-lisp$</i> <b>ls -l /project/ | grep ook</b><br>drwxrwsr-x 1 orphaned-projects cl-hooks                 22 Mar 29  2015 cl-hooks/<br>drwxrwsr-x 1 eenge             hyperspec-lookup         22 May 12  2015 hyperspec-lookup/<br>drwxr-sr-x 1 mantoniotti       ook                      22 Oct  6  2018 ook/<br></span></div><div><span style="font-family:monospace"><i>mantoniotti@common-lisp$</i> <b>ls -l /project/ook</b><br>total 0<br>drwxrwsr-x 1 mantoniotti ook 252 Oct 12  2018 public_html/</span></div><div><br></div><div>As you can see the <span style="font-family:monospace">/project/ook</span> directory has its own UN*X group.  I am part of that group, therefore I can write it no problem.  What has changed is with the new projects, which do not get a UN*X group, as they are created via Gitlab.</div><div><br></div><div>The updated OOK doc pages get loaded as expected (as you can check).</div><div><br></div><div>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 <span style="font-family:monospace">.yml </span>one.</div><div>However, from what I understand from the cl-couch, cmucl-site and maxima-site examples, it should be sufficient for me to add</div><div>
<pre class="gmail-code gmail-highlight" lang="yaml"><span id="gmail-LC1" class="gmail-line" lang="yaml"><span class="gmail-na">pages</span><span class="gmail-pi">:</span></span>
<span id="gmail-LC2" class="gmail-line" lang="yaml">  <span class="gmail-na">stage</span><span class="gmail-pi">:</span> <span class="gmail-s">deploy</span></span>
<span id="gmail-LC3" class="gmail-line" lang="yaml">  <span class="gmail-na">script</span><span class="gmail-pi">:</span> <span class="gmail-s">mv docs/html public</span></span>
<span id="gmail-LC4" class="gmail-line" lang="yaml">  <span class="gmail-na">artifacts</span><span class="gmail-pi">:</span></span>
<span id="gmail-LC5" class="gmail-line" lang="yaml">     <span class="gmail-na">paths</span><span class="gmail-pi">:</span></span>
<span id="gmail-LC6" class="gmail-line" lang="yaml">       <span class="gmail-pi">-</span> <span class="gmail-s">public</span></span>
<span id="gmail-LC7" class="gmail-line" lang="yaml">  <span class="gmail-na">tags</span><span class="gmail-pi">:</span></span>
<span id="gmail-LC8" class="gmail-line" lang="yaml">    <span class="gmail-pi">-</span> <span class="gmail-s">site-gen</span></span>
<span id="gmail-LC9" class="gmail-line" lang="yaml">  <span class="gmail-na">only</span><span class="gmail-pi">:</span></span>
<span id="gmail-LC10" class="gmail-line" lang="yaml">    <span class="gmail-pi">-</span> <span class="gmail-s">master</span></span>
</pre>

</div><div><br></div><div>to, say, the with-context top directory?  Or could I add it to the docs subdirectory only (changing the <span style="font-family:monospace">script </span>entry)?<br></div><div><br></div><div>Just asking for reassurances before trying it out...</div><div><br></div><div>All the best</div><div>Thanks for your help<br></div><div><br></div><div>Marco</div><div><br></div><div><br></div><div>PS  I understand the issues with having more than one CL implementation installed.  No problems there...<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Dec 27, 2020 at 3:36 AM Raymond Toy <<a href="mailto:toy.raymond@gmail.com">toy.raymond@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
    Marco> Hi Everybody Happy (Hacking) Holidays.<br>
<br>
    Marco> Ok.  I am back doing this.  Thank you Erik and thank you Ray<br>
    Marco> for the tutorial :)<br>
<br>
    Marco> Let me understand how I need to proceed.  But first let me<br>
    Marco> tell you how I was working before.<br>
<br>
    Marco> In the past I would load my docs to my local clnet home and<br>
    Marco> the I would copy them to the /project/public_html.  As I use<br>
    Marco> (shameless plug) HELambdaP to generate the documentation (*<br>
    Marco> and ** below), I can keep everything in my folders and not<br>
    Marco> use the .gitlab-ci.yml thingy.<br>
<br>
    Marco> Now I have the following problem, which I believe is<br>
    Marco> affecting me (and others) either with or without<br>
    Marco> .gitlab-ci.yml: the new projects do not have a "group" (a<br>
    Marco> UN*X group) created automatically, which is what I was also<br>
    Marco> hinting at with my first message.  Cfr., my last project<br>
    Marco> 'with-contexts'.<br>
<br>
    Marco> If I were to create a 'with-context-site' project in Gitlab,<br>
    Marco> I would still have to ask you (the admins) for the creation<br>
    Marco> of the 'with-context' group.  My feeling is that the old ways<br>
    Marco> were better, although I do not know what that entails about<br>
    Marco> Gitlab "groups", which, I presume, are different from UN*X<br>
    Marco> groups.<br>
<br>
    Marco> Now: is the move to Gitlab sites mandatory?  If so, does that<br>
    Marco> mean that we will need to have TWO projects going on<br>
    Marco> separately? I.e. 'myproject' and 'myproject-site'?  If the<br>
    Marco> move is not mandatory, will the old way of manually copying<br>
    Marco> documentation to '/projects/myproject/public_html' still work<br>
    Marco> (provided that the 'group' was there)?<br>
<br>
Copying documentation to /projects/myproject/public_html no longer works<br>
I think.  The http server doesn't look there any more.  It's somewhere<br>
else; I'd have to look at my old emails to find out exactly where.  But<br>
I think that also doesn't matter because I don't think it's writable by<br>
you.<br>
<br>
I don't think you really need two projects, but I find it rather nice to<br>
separate out the site from the code.  However, as a hack I have<br>
<a href="https://gitlab.common-lisp.net/maxima/maxima-site" rel="noreferrer" target="_blank">https://gitlab.common-lisp.net/maxima/maxima-site</a> which is a full copy<br>
of the maxima repo.  Except I only use it to build the docs<br>
automatically with each checkin.  I could build maxima if desired.<br>
<br>
But you do need admins to create the project group.  You can't use your<br>
personal group.<br>
<br>
    Marco> (***) Can we have ABCL, ECL, CMUCL etc also installed?  Just<br>
    Marco> asking...<br>
<br>
Cmucl requires 32-bit libraries.<br>
<br>
I think this is an unnecessary extra burden for the admins.  The problem<br>
is knowing exactly which version to have and when to update if needed.<br>
And managing the the versions because different projects may want<br>
different versions.<br>
<br>
I solve this myself in my CI config by downloading the appropriate<br>
version and using it.  Perhaps I could save some bandwidth by keeping it<br>
in an artifact so that it can just be reloaded from disk (?) instead of<br>
downloading it from <a href="http://c-l.net" rel="noreferrer" target="_blank">c-l.net</a> each time.<br>
<br>
--<br>
Ray<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;display:inline;float:none">Marco Antoniotti, Associate Professor</span><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:pre;word-spacing:0px;text-decoration:none">             </span><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:pre;word-spacing:0px;text-decoration:none"> </span><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;display:inline;float:none">tel.</span><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration:none;display:inline;float:none;white-space:pre"> </span><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;display:inline;float:none">+39 - 02 64 48 79 01</span><br style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;display:inline;float:none">DISCo, Università Milano Bicocca U14 2043</span><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:pre;word-spacing:0px;text-decoration:none">     </span><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:pre;word-spacing:0px;text-decoration:none"> </span><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:pre;word-spacing:0px;text-decoration:none"></span><a href="http://bimib.disco.unimib.it/" style="font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">http://bimib.disco.unimib.it</a><br style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;display:inline;float:none">Viale Sarca 336</span><br style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="color:rgb(0,0,0);font-family:Helvetica;font-size:14px;font-style:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;display:inline;float:none">I-20126 Milan (MI) ITALY</span><br></div></div></div></div>