===> The following configuration options are available for gitlab-ce-19.4.2_1:
KERBEROS=on: Kerberos support
===> Use 'make config' to modify these settings
Gitlab was installed successfully.
You now need to set up the various components of Gitlab, so please
follow the instructions in the guide at:
https://gitlab.com/mfechner/freebsd-gitlab-docu/blob/master/install/19.4-freebsd.md
If upgrading from < 11.9.7:
!! WARNING: Please make sure you read in UPDATING entry 20190423 !!
If upgrading
If you just installed an major upgrade of GitLab, for example you
switched from 18.6.x to 18.7.x, please follow the instructions in the guide at:
https://gitlab.com/mfechner/freebsd-gitlab-docu/blob/master/update/19.3-19.4-freebsd.md
If you just installed an minor upgrade of GitLab please follow
the instructions in the guide at:
https://gitlab.com/mfechner/freebsd-gitlab-docu/blob/master/update/freebsd_patch_versions.md
Reason:
Make sure you compare your /usr/local/www/gitlab/config/puma.rb with
/usr/local/www/gitlab/config/puma.rb.sample and make sure you have the:
require "logger"
line in your puma.rb.
This fixes an error:
/usr/local/lib/ruby/gems/3.2/gems/activesupport-7.0.8.7/lib/active_support/logger_thread_safe_level.rb:12:in `<module:LoggerThreadSafeLevel>': uninitialized constant ActiveSupport::LoggerThreadSafeLevel::Logger (NameError)
Logger::Severity.constants.each do |severity|
Reason:
Make sure you upgrade first to 16.11.x before you upgrade to the today
released version 17.0.0.
For more details see:
https://gitlab.fechner.net/mfechner/Gitlab-docu/-/blob/master/update/16.11-17.0-freebsd.md
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-gettext_i18n_rails to
rubygem-gettext_i18n_rails-gitlab
- Change RUN_DEPENDS from rubygem-zeitwerk to rubygem-zeitwerk-gitlab
- Bump PORTREVISION for dependency change
www/gitlab: fix regression from d747b3e47669abac14d4808212f48455fbe3f3fe
www/rubygem-js-routes 2.4.x includes in incompatible API change which
breaks gitlab at runtime while e.g. loading projects.
The problem only appears if the asset for gitlab are recompiled with
this new version which makes it harder to spot the problem.
I will follow up the issue here:
https://gitlab.com/gitlab-org/gitlab/-/work_items/605464
Thanks a lot to Peter for finding the cause of that problem!
PR: 296698
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-json to rubygem-json-gitlab
- Change RUN_DEPENDS from rubygem-nkf to rubygem-nkf-gitlab
- Change RUN_DEPENDS from rubygem-sys-filesystem to
rubygem-sys-filesystem-gitlab
- Bump PORTREVISION for dependency change
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-connection_pool to
rubygem-connection_pool-gitlab
- Change RUN_DEPENDS from rubygem-rack-proxy to rubygem-rack-proxy-gitlab
- Bump PORTREVISION for dependency change
www/gitlab: fixed regressions from
9c7ec30e93f9d4bcf7dd7b213b582ac05138e31f
b38ff7a19b6c3dbe3007d1f88d12e600b5a288a8
Could not find compatible versions
Because every version of gitlab-backup-cli depends on bigdecimal ~> 3.1
and bigdecimal >= 3.1, < 4.A could not be found in locally installed gems,
gitlab-backup-cli cannot be used.
So, because Gemfile depends on gitlab-backup-cli >= 0,
version solving has failed.
*** Error code 6
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-loofah to rubygem-loofah-gitlab
- Change RUN_DEPENDS from rubygem-openssl to rubygem-openssl3
- Bump PORTREVISION for dependency change
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-bootsnap to rubygem-bootsnap-gitlab
- Change RUN_DEPENDS from rubygem-grape-swagger to rubygem-grape-swagger-gitlab
- Bump PORTREVISION for dependency change
www/gitlab: enable the gitlab secrets scanner in the standard pipeline
This makes it now possible to have a gitlab-runner with shell
and in the pipeline of the repository the default
gitlab pipeline can be used now, like:
include:
- template: Jobs/Secret-Detection.gitlab-ci.yml
www/gitlab: security and bugfix update to 18.5.2
With the upgrade of node from 22 to 24 I see the need of more memory
for the asset compilation.
Plan to provide one more GB memory to your gitlab instance.
Changes: https://about.gitlab.com/releases/2025/11/12/patch-release-gitlab-18-5-2-released/
Security: 5a1d6309-c04a-11f0-85d8-2cf05da270f3
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-hamlit to rubygem-hamlit-gitlab
- Change RUN_DEPENDS from rubygem-net-http to rubygem-net-http-gitlab
- Bump PORTREVISION for dependency change
www/gitlab: fix regression from 5028178941fc081cd43354ea03ceda365a12f73d
this fixes a depedency conflict with rubygem-logger which was added into
package security/rubygem-omniauth which conflicts with rubygem-logger-gitlab
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-fugit to rubygem-fugit111
- Change RUN_DEPENDS from rubygem-json to rubygem-json-gitlab
- Change RUN_DEPENDS from rubygem-typhoeus to rubygem-typhoeus14
- Bump PORTREVISION for dependency change
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-jwt to rubygem-jwt2
- Change RUN_DEPENDS from rubygem-puma to rubygem-puma6
- Bump PORTREVISION for dependency change
www/gitlab: decouple from www/rubygem-rqrcode
This makes it possible to upgrade www/rubygem-rqrcode to version 3
which unbreaks it due to update of www/rubygem-rqrcode_core.
PR: 286372
www/gitlab: Update RUN_DEPENDS
- Change RUN_DEPENDS from rubygem-devfile to rubygem-devfile-gitlab
- Change RUN_DEPENDS from rubygem-httparty to rubygem-httparty-gitlab
- Change RUN_DEPENDS from rubygem-logger to rubygem-logger-gitlab
- Bump PORTREVISION for dependency change
