You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To do this, gitlab noly checks if the file '/etc/init.d/gitlab' is same with 'lib/support/init.d/gitlab"'. This is right when we use ubuntu. When we install gitlab on CentOS, we download the file from https://github.com/gitlabhq/gitlab-recipes/tree/master/init/sysvinit/centos/gitlab-unicorn, so it is not same with 'lib/support/init.d/gitlab', then the command 'bundle exec rake gitlab:check RAILS_ENV=production' said '/etc/init.d/gitlab' is not up-to-date.
The text was updated successfully, but these errors were encountered:
That is true, but not a problem with CentOS recipe rather than the rake task that runs that check. Keep in mind that the official installation supports debian/ubuntu only.
One thing I can think of is to inform the users about that issue in the README guide. Care to make a PR?
To do this, gitlab noly checks if the file '/etc/init.d/gitlab' is same with 'lib/support/init.d/gitlab"'. This is right when we use ubuntu. When we install gitlab on CentOS, we download the file from https://github.com/gitlabhq/gitlab-recipes/tree/master/init/sysvinit/centos/gitlab-unicorn, so it is not same with 'lib/support/init.d/gitlab', then the command 'bundle exec rake gitlab:check RAILS_ENV=production' said '/etc/init.d/gitlab' is not up-to-date.
The text was updated successfully, but these errors were encountered: