Re: Pages not deploying?

Hi Ray,

Fillip Marek checked out your problem report this morning. There was a configuration issue and https://cmucl.common-lisp.dev renders correctly now.

Regards,

Erik.

On Wed, Jan 19, 2022 at 5:57 AM Raymond Toy toy.raymond@gmail.com wrote:

Yeah, I've noticed that common-lisp.dev is doing something different now. cmucl.common-lisp.dev is not loading the JS files. Chrome console says the server is responding with a MIME type of "text/html" for the file js/common.js. Without JS, I can't navigate to the various pages.

Before it was moved, common-lisp.net/project/cmucl/ worked fine and loaded the JS files without problems.

On Tue, Jan 18, 2022 at 8:19 PM Eric Timmons etimmons@mit.edu wrote:

...

There seems to be something wrong with the Gitlab Pages hosted sites. It looks like the path is being dropped when the request is forwarded to the Pages daemon.

Compare https://cl-tar.common-lisp.dev/, https://cl-tar.common-lisp.dev/cl-tar/v0.2.1/manual/, and https://cl-tar.common-lisp.dev/theme.css

-Eric

On 1/18/22 18:33, Erik Huelsmann wrote:

...

Today i renamed all repositories that deploy a site, such as antiek/antik-site so that it deploys its site on antiek.common-lisp.dev http://antiek.common-lisp.dev.

All sites that used to be hosted under common-lisp.net/project/ http://common-lisp.net/project/ are now forwarded to common-lisp.dev http://common-lisp.dev too.

It would be absolutely great if we could get contributions from people who are comfortable with gitlab pages describing how to use it with CL site builder software as content for common-lisp.net http://common-lisp.net

Regards,

Erik

On Sat, Jan 15, 2022, 19:37 Raymond Toy <toy.raymond@gmail.com mailto:toy.raymond@gmail.com> wrote:

On Sat, Jan 15, 2022 at 10:21 AM Erik Huelsmann <ehuels@gmail.com
<mailto:ehuels@gmail.com>> wrote:

    Hi Ray,

     > Sorry for the delay.
    No problem!

     > I tried to look for the deployed pages, and
    https://common-lisp.net/project/cmucl
    <https://common-lisp.net/project/cmucl> no longer exists (404),
    and the new site cmucl.common-lisp.dev
    <http://cmucl.common-lisp.dev> doesn't exist either.

    The issue here is that the site correctly renders when you use
    https://common-lisp.net/project/cmucl/
    <https://common-lisp.net/project/cmucl/> but not without the
    trailing
    forward-slash. This is one of the reasons to want to implement the
    pages daemon and run the domains on common-lisp.dev
    <http://common-lisp.dev>.


Yes, when I use the trailing slash, I see the expected results.
Thanks so much for fixing this!


     > Gitlab CI thinks everything is working though.  I don't
    remember if this is the way it always was or not, but if you
    visit
    https://gitlab.common-lisp.net/cmucl/cmucl-site/-/pipelines/5765
    <https://gitlab.common-lisp.net/cmucl/cmucl-site/-/pipelines/5765>,
    the deploy stage has two steps: "pages" and "pages:deploy".  I
    can rerun "pages", but not "pages:deploy".

    I think the step "pages:deploy" is a built-in step in GitLab CI
    which
    you're not supposed to be able to re-run. However, it'll rerun when
    the last job gets rerun (or so I believe).


Looks that way.  I just reran the pipeline an hour or so ago, and
once I used the correct link, the expected changes are there.

Thanks!





    --
    Bye,

    Erik.

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



--
Ray

-- Ray