Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

1_settings.rb

  • Patrick Bajao's avatar
    95ffd22f
    Set default authorized_keys_file · 95ffd22f
    Patrick Bajao authored
    This is the same as gitlab-shell's default. This is to ensure
    that it's always set.
    
    It needs to be the same as gitlab-shell's default because we
    don't set a default value in omnibus-gitlab. If users don't
    set the value of that config in their install and they upgraded,
    we must ensure that it's still going to point to the same
    authorized keys file.
    95ffd22f
    History
    Set default authorized_keys_file
    Patrick Bajao authored
    This is the same as gitlab-shell's default. This is to ensure
    that it's always set.
    
    It needs to be the same as gitlab-shell's default because we
    don't set a default value in omnibus-gitlab. If users don't
    set the value of that config in their install and they upgraded,
    we must ensure that it's still going to point to the same
    authorized keys file.