Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. GitLab
  3. Where to find "/etc/gitlab/gitlab.rb" path?

Where to find "/etc/gitlab/gitlab.rb" path?

Scheduled Pinned Locked Moved Solved GitLab
8 Posts 3 Posters 4.8k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • arshsahzadA Offline
      arshsahzadA Offline
      arshsahzad
      wrote on last edited by
      #1

      I have to configure GitLab sidekiq and puma for memory optimization in my cloudron server but I'm not able to find the path /etc/gitlab/gitlab.rb in the ubuntu 20.04. Where can I find the gitlab.rb file?

      nebulonN 1 Reply Last reply
      0
      • arshsahzadA arshsahzad

        I have to configure GitLab sidekiq and puma for memory optimization in my cloudron server but I'm not able to find the path /etc/gitlab/gitlab.rb in the ubuntu 20.04. Where can I find the gitlab.rb file?

        nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #2

        @arshsahzad the Cloudron package is using /app/data/gitlab.yml to configure GitLab. See https://docs.gitlab.com/omnibus/settings/gitlab.yml.html on how to map gitlab.rb key values to gitlab.yml ones.

        luckowL 1 Reply Last reply
        2
        • nebulonN nebulon

          @arshsahzad the Cloudron package is using /app/data/gitlab.yml to configure GitLab. See https://docs.gitlab.com/omnibus/settings/gitlab.yml.html on how to map gitlab.rb key values to gitlab.yml ones.

          luckowL Offline
          luckowL Offline
          luckow
          translator
          wrote on last edited by
          #3

          @nebulon ah good hint. Please add this to https://docs.cloudron.io/apps/gitlab/

          Pronouns: he/him | Primary language: German

          nebulonN 1 Reply Last reply
          0
          • luckowL luckow

            @nebulon ah good hint. Please add this to https://docs.cloudron.io/apps/gitlab/

            nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #4

            @luckow good point. Done now.

            arshsahzadA 1 Reply Last reply
            0
            • nebulonN nebulon

              @luckow good point. Done now.

              arshsahzadA Offline
              arshsahzadA Offline
              arshsahzad
              wrote on last edited by
              #5

              @nebulon, I recently switched from Gitea to GitLab and the GitLab instance have only 5 users but it is taking around 2.6GB RAM space in my cloudron server. I have to apply below these configurations in gitlab.yml because it will optimize and save around 500Mb RAM space:-

              #gitlab.rb configuration
              
              puma['worker_processes'] = 0
              sidekiq['max_concurrency'] = 10
              prometheus_monitoring['enable'] = false
              
              

              Translate for gitlab.yml

              puma:
                worker_processes: 0
              
              sidekiq:
                 max_concurrency: 10
              
              prometheus_monitoring
                enable: false
              
              

              6ec7c6a5-68d4-4b0b-b4a2-5728b6513bf2-image.png

              I put the sidekiq config in line 349 but don't know where to put puma and prometheus_monitoring?

              luckowL 1 Reply Last reply
              0
              • arshsahzadA arshsahzad

                @nebulon, I recently switched from Gitea to GitLab and the GitLab instance have only 5 users but it is taking around 2.6GB RAM space in my cloudron server. I have to apply below these configurations in gitlab.yml because it will optimize and save around 500Mb RAM space:-

                #gitlab.rb configuration
                
                puma['worker_processes'] = 0
                sidekiq['max_concurrency'] = 10
                prometheus_monitoring['enable'] = false
                
                

                Translate for gitlab.yml

                puma:
                  worker_processes: 0
                
                sidekiq:
                   max_concurrency: 10
                
                prometheus_monitoring
                  enable: false
                
                

                6ec7c6a5-68d4-4b0b-b4a2-5728b6513bf2-image.png

                I put the sidekiq config in line 349 but don't know where to put puma and prometheus_monitoring?

                luckowL Offline
                luckowL Offline
                luckow
                translator
                wrote on last edited by
                #6

                @arshsahzad From my experience: if you have to deal with RAM, don't use gitlab. Currently, one of my Gitlab instances uses 4.5 GB RAM with 10 users and it's slow.

                Pronouns: he/him | Primary language: German

                nebulonN arshsahzadA 2 Replies Last reply
                1
                • luckowL luckow

                  @arshsahzad From my experience: if you have to deal with RAM, don't use gitlab. Currently, one of my Gitlab instances uses 4.5 GB RAM with 10 users and it's slow.

                  nebulonN Offline
                  nebulonN Offline
                  nebulon
                  Staff
                  wrote on last edited by
                  #7

                  I can second @luckow 's statement here, GitLab base functionality requires a lot of memory already and if you are concerned about memory, then it is not the right tool for git repo/project management.

                  1 Reply Last reply
                  2
                  • luckowL luckow

                    @arshsahzad From my experience: if you have to deal with RAM, don't use gitlab. Currently, one of my Gitlab instances uses 4.5 GB RAM with 10 users and it's slow.

                    arshsahzadA Offline
                    arshsahzadA Offline
                    arshsahzad
                    wrote on last edited by arshsahzad
                    #8

                    @luckow @nebulon Thanks for ur valuable response, I will consider about this...

                    1 Reply Last reply
                    0
                    Reply
                    • Reply as topic
                    Log in to reply
                    • Oldest to Newest
                    • Newest to Oldest
                    • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search