^Triage: to submitter: we need more information.
Hello, I've been trying to install the "gitlab-ce" port which has a dependency to the gitlab-pages. After a fresh install I first got an error message about not present "shared/pages" folder: level=fatal msg="could not change directory into pagesRoot" error="chdir shared/pages: no such file or directory" Simply creating it in the ${gitlab_pages_dir} solved the problem, but then I instead got the warning: level=warning msg="failed to initialize GitLab client for `-domain-config-source=auto`" error="GitLab API URL or API secret has not been provided" Checking the gitlab-pages service I first noticed the startcmd function uses a variable not defined in the service file at all: ${gitlab_pages_args}. In order to be able to configure the pages daemon I set it to gitlab_pages_args="-config ${gitlab_pages_dir}/config.ini" and created this config file with the following content: internal-gitlab-server=http://<MY_LOCAL_IP> api-secret-key=/usr/local/www/gitlab-ce/.gitlab_shell_secret restarting the service now instead gives me the error message: level=fatal msg="Failed to load config" error="expected 32 bytes GitLab API secret but got 24 bytes Am a bit lost how I solve this issue. Do you have any ideas or something that I've done really wrong here? Best Regards, Michal
Have you tried setting: api-secret-key=SECRET_KEY_VALUE_HERE rather than the path to the file containing the secret key?
(In reply to fulder from comment #2) > Checking the gitlab-pages service I first noticed the startcmd function uses a variable not defined in the service file at all: ${gitlab_pages_args}. It's defined by /etc/rc.subr, see man 8 rc.subr, and defaults to empty. It's an optional thing you can set, if you need it. The service uses it order to honor that option. > In order to be able to configure the pages daemon I set it to gitlab_pages_args="-config ${gitlab_pages_dir}/config.ini" and created this config file with the following content: > > internal-gitlab-server=http://<MY_LOCAL_IP> > api-secret-key=/usr/local/www/gitlab-ce/.gitlab_shell_secret > > restarting the service now instead gives me the error message: > level=fatal msg="Failed to load config" error="expected 32 bytes GitLab API secret but got 24 bytes I think you're mixing up the gitlab shell secret and the gitlab pages secret. Reading: https://docs.gitlab.com/ee/administration/pages/source.html#wildcard-domains which shows an example like: api-secret-key=/home/git/gitlab/gitlab-pages-secret and the gitlab-pages-secret file being generated with openssl: sudo -u git -H openssl rand -base64 32 > /home/git/gitlab/gitlab-pages-secret This file is again referenced in gitlab.yml under the pages section: secret_file: /home/git/gitlab/gitlab-pages/gitlab-pages-secret Obviously our paths will differ from the documentation which is targeted at Linux users. For further info, see the source: https://gitlab.com/gitlab-org/gitlab-pages/-/blob/master/internal/config/config.go Hopefully this helps, please re-open if you're still having trouble.