Package Details: gitlab-pages 1.7.0-2

Git Clone URL: (read-only)
Package Base: gitlab-pages
Description: GitLab Pages daemon used to serve static websites for GitLab users
Upstream URL:
Licenses: MIT
Submitter: melvinvermeeren
Maintainer: melvinvermeeren (caleb)
Last Packager: caleb
Votes: 3
Popularity: 0.858845
First Submitted: 2017-11-16 21:30
Last Updated: 2019-08-17 09:09

Latest Comments

melvinvermeeren commented on 2019-08-18 14:51

Thanks for the updated fix. The configuration file is indeed based upon the output of gitlab-pages --help, minus the --config option. So far I do it manually with a macro in vim, but I think a script is a much better idea.

caleb commented on 2019-08-17 09:15

Thanks for applying the patch and adding me as a maintainer. I've just updated the patch (based on upstream discussions) to a more though fix that solves both the fork and the chroot in one go (the other patch fixed the fork issue but still didn't allow the chroot with permission dropping. The fix will likely be obsolete on the next release, so I made it conditional and the prepare() section can be dropped again when it's confirmed to be included.

For future reference, do you have a script for updating the default configuration file? I assume it's based on the output of gitlab-pages --help or something like that, no?

melvinvermeeren commented on 2019-08-10 01:01

Thanks for the patch, applied it and updated config. Also added you as a co-maintaine for in the future. Cheers!

caleb commented on 2019-08-07 13:34

I submitted a fix for the fork/exec issue upstream:

Until that is accepted, this patch will fix this package build:

@melvinvermeeren Can you please add me as contributor and/or apply that patch with:

curl -s | git am


caleb commented on 2019-08-07 11:46

This issue appears to be a problem on Arch Linux by default:

Edit 1: scratch that. It's actually this problem:

Even with the default CGO_ENABLED=0 being set in the makefile I'm ending up with a /usr/bin/gitlab-pages that is not statically compiled and thus fails the chroot maneuver.

Edit 2: Opened upstream issue:

melvinvermeeren commented on 2018-04-28 19:21

with the update to 0.9.0 chroot support has been added and is enabled by default

you probably need to update your config.cfg or you may end up with pages running as root without chrooting!

melvinvermeeren commented on 2017-11-16 21:35

make sure you set the config in /etc/gitlab-pages/config.cfg before starting/enabling the service.
also need to edit the main gitlab yaml to point to pages.
other info in GitLab help itself.

P.S. single subdomain is possible if you reverse proxy: