Time to consolidate static project pages into GitLab?

Erik Huelsmann ehuels at gmail.com
Sat May 20 08:30:29 UTC 2017

On Fri, May 19, 2017 at 4:50 PM, Raymond Toy <toy.raymond at gmail.com> wrote:

> On Wed, May 10, 2017 at 4:09 AM, Erik Huelsmann <ehuels at gmail.com> wrote:
>> One question does remain: would anybody be interested in having the
>> "easy" route for deploying static website content through Git*Lab* pages?
>> In other words, would there still be a benefit for us setting it up or is
>> there no demand?
> ​Is it a lot of work or on-going maintenance? Do the static pages also
> get a git repo so you can do revision control on them?

Yes: every project uses a git repository to develop its pages. you can push
to your pages repo, the pages feature builds your static content and pushes
it out to update the hosted site. I was studying the exact mechanics last

There is mostly the initial effort to get it set up. There doesn't seem to
me more effort involved in maintaining this additional bit of GitLab than
there already is with the rest of it.

> I'm considering moving the pages from www.cmucl.org to here (and having
> www.cmucl.org redirect).  But we're also considering just moving all the
> pages there to the wiki, so we then wouldn't need static pages.  There
> aren't a lot of pages and the pages are quite simple so the effort to move
> to the wiki isn't huge.​

Do you want to run an experiment with GitLab pages to see if it suits your



http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clo-devel/attachments/20170520/91cffd7f/attachment.html>

More information about the clo-devel mailing list