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. Gitea
  3. Gitea minio storage for lfs

Gitea minio storage for lfs

Scheduled Pinned Locked Moved Gitea
27 Posts 7 Posters 23.1k Views 7 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.
  • marcusquinnM marcusquinn

    @robi I'm going with Gitier, as in Glacier. Can't imagine anyone would say Gitay?

    robiR Offline
    robiR Offline
    robi
    wrote on last edited by robi
    #5

    @marcusquinn for me the word is vocalized in a foreign language I speak, which sounds like Andre-a // Git-eh-ah

    Otherwise it's more something like Giddiup where the p is silent.

    Now Tea also some to mind.. the female name and the beverage.

    So maybe the Git coffee is really just a dark tea 😉

    Conscious tech

    infogulchI 1 Reply Last reply
    0
    • robiR robi

      @marcusquinn for me the word is vocalized in a foreign language I speak, which sounds like Andre-a // Git-eh-ah

      Otherwise it's more something like Giddiup where the p is silent.

      Now Tea also some to mind.. the female name and the beverage.

      So maybe the Git coffee is really just a dark tea 😉

      infogulchI Offline
      infogulchI Offline
      infogulch
      wrote on last edited by
      #6

      I've been struggling with how to pronounce it as well; so far my internal monologue has been settling in the direction of "Andre-a // Git-eh-ah", but stealing the t from git: "Gi-tee-ah". It doesn't sound like it has "git" anymore, but at least there's "tea". Have the devs given any talks on Gitea? I'd rather settle on something instead of sounding it out 4-5 times every time I read it lol

      1 Reply Last reply
      0
      • infogulchI infogulch

        Hi!

        I'm interested in using git LFS storage from my gitea app but I'm worried that my server could run out of space with many large files. Gitea supports any s3-like storage as a backend for LFS and attachments (see Gitea Config Cheat Sheet). So, using the gitea app terminal I edited /app/data/app.ini to add the following configuration and restarted gitea from the dashboard:

        [server]
        LFS_START_SERVER = true
        
        [storage.my-storage]
        STORAGE_TYPE = minio
        SERVE_DIRECT = true
        MINIO_ENDPOINT = s3.us-west-001.backblazeb2.com 
        MINIO_ACCESS_KEY_ID = {secret-id}
        MINIO_SECRET_ACCESS_KEY = {secret-key}
        MINIO_BUCKET = my-bucket
        MINIO_LOCATION = us-west-001
        MINIO_USE_SSL = true
        
        [lfs]
        STORAGE_TYPE = my-storage
        
        [attachment]
        STORAGE_TYPE = my-storage
        MAX_SIZE = 50
        

        And it seems to work, great! Yes, I'm actually using backblaze b2, because it's much more cost efficient than amazon's service. Yay compatibility!

        • One question: is /app/data/app.ini the correct place to add gitea custom configurations?
        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #7

        @infogulch said in Gitea minio storage for lfs:

        One question: is /app/data/app.ini the correct place to add gitea custom configurations?

        Yes, that's the correct place!

        infogulchI 1 Reply Last reply
        1
        • girishG girish

          @infogulch said in Gitea minio storage for lfs:

          One question: is /app/data/app.ini the correct place to add gitea custom configurations?

          Yes, that's the correct place!

          infogulchI Offline
          infogulchI Offline
          infogulch
          wrote on last edited by
          #8

          @girish Do you think it would be a good idea to document or link to this customization in particular in the Gitea docs?

          girishG 2 Replies Last reply
          0
          • infogulchI infogulch

            @girish Do you think it would be a good idea to document or link to this customization in particular in the Gitea docs?

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #9

            @infogulch Isn't the customization file already mentioned here - https://docs.cloudron.io/apps/gitea/#customizing-gitea ? Or are you referring to something else?

            1 Reply Last reply
            0
            • infogulchI infogulch

              @girish Do you think it would be a good idea to document or link to this customization in particular in the Gitea docs?

              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #10

              @infogulch Oh, I guess you meant the config that you posted as an example. Good idea, I put it at https://docs.cloudron.io/apps/gitea/#lfs

              infogulchI 1 Reply Last reply
              1
              • girishG girish

                @infogulch Oh, I guess you meant the config that you posted as an example. Good idea, I put it at https://docs.cloudron.io/apps/gitea/#lfs

                infogulchI Offline
                infogulchI Offline
                infogulch
                wrote on last edited by
                #11

                @girish Yes that's what I meant, thanks!

                1 Reply Last reply
                0
                • ? Offline
                  ? Offline
                  A Former User
                  wrote on last edited by A Former User
                  #12

                  @marcusquinn
                  For the pronunciation, I assumed it was Git-tea. Hence the logo. That aside, it turns out to be a much better sell than Gitlab. Sure, Gitlab has nice features but a simple comparison of the feature vs the resource usage makes it win for me. Gitlab is still a massive resource hog for what it offers.

                  Also Drone CI + Gitea make for a very powerful combo.

                  1 Reply Last reply
                  2
                  • robiR Offline
                    robiR Offline
                    robi
                    wrote on last edited by
                    #13

                    G I T ? <g i tea> 🙂

                    Conscious tech

                    1 Reply Last reply
                    0
                    • fbartelsF Offline
                      fbartelsF Offline
                      fbartels
                      App Dev
                      wrote on last edited by
                      #14

                      This is a fun but completely off topic discussion. And its something that the project clarifies in their own readme: https://github.com/go-gitea/gitea#faq

                      1 Reply Last reply
                      1
                      • infogulchI infogulch

                        Hi!

                        I'm interested in using git LFS storage from my gitea app but I'm worried that my server could run out of space with many large files. Gitea supports any s3-like storage as a backend for LFS and attachments (see Gitea Config Cheat Sheet). So, using the gitea app terminal I edited /app/data/app.ini to add the following configuration and restarted gitea from the dashboard:

                        [server]
                        LFS_START_SERVER = true
                        
                        [storage.my-storage]
                        STORAGE_TYPE = minio
                        SERVE_DIRECT = true
                        MINIO_ENDPOINT = s3.us-west-001.backblazeb2.com 
                        MINIO_ACCESS_KEY_ID = {secret-id}
                        MINIO_SECRET_ACCESS_KEY = {secret-key}
                        MINIO_BUCKET = my-bucket
                        MINIO_LOCATION = us-west-001
                        MINIO_USE_SSL = true
                        
                        [lfs]
                        STORAGE_TYPE = my-storage
                        
                        [attachment]
                        STORAGE_TYPE = my-storage
                        MAX_SIZE = 50
                        

                        And it seems to work, great! Yes, I'm actually using backblaze b2, because it's much more cost efficient than amazon's service. Yay compatibility!

                        • One question: is /app/data/app.ini the correct place to add gitea custom configurations?
                        W Offline
                        W Offline
                        Wirv
                        wrote on last edited by
                        #15

                        @infogulch forgive me I've been fighting it for days, but how does the connection work, do I need an active minio server? or just this setting in the app.ini is enough
                        Is there any git config command to do? If someone can help me I would be very grateful and happy

                        girishG 1 Reply Last reply
                        0
                        • W Wirv

                          @infogulch forgive me I've been fighting it for days, but how does the connection work, do I need an active minio server? or just this setting in the app.ini is enough
                          Is there any git config command to do? If someone can help me I would be very grateful and happy

                          girishG Offline
                          girishG Offline
                          girish
                          Staff
                          wrote on last edited by
                          #16

                          @Wirv Have you seen https://docs.cloudron.io/apps/gitea/#lfs already? Yes, you need an active minio server or external S3 provider.

                          W 2 Replies Last reply
                          0
                          • girishG girish

                            @Wirv Have you seen https://docs.cloudron.io/apps/gitea/#lfs already? Yes, you need an active minio server or external S3 provider.

                            W Offline
                            W Offline
                            Wirv
                            wrote on last edited by
                            #17
                            This post is deleted!
                            1 Reply Last reply
                            0
                            • girishG girish

                              @Wirv Have you seen https://docs.cloudron.io/apps/gitea/#lfs already? Yes, you need an active minio server or external S3 provider.

                              W Offline
                              W Offline
                              Wirv
                              wrote on last edited by
                              #18

                              @girish I did as you told me, and inserted the changes reported on app.ini, with the data of my bucket b2, but when I restart gitea with the following changes and minio server turned on, it gives me this error

                              2023/02/01 15:24:05 routers/init.go:59:mustInit() [F] code.gitea.io/gitea/modules/storage.Init failed: Malformed Access Key Id
                              Received signal 15; terminating.
                              
                              girishG 1 Reply Last reply
                              0
                              • W Wirv

                                @girish I did as you told me, and inserted the changes reported on app.ini, with the data of my bucket b2, but when I restart gitea with the following changes and minio server turned on, it gives me this error

                                2023/02/01 15:24:05 routers/init.go:59:mustInit() [F] code.gitea.io/gitea/modules/storage.Init failed: Malformed Access Key Id
                                Received signal 15; terminating.
                                
                                girishG Offline
                                girishG Offline
                                girish
                                Staff
                                wrote on last edited by
                                #19

                                @Wirv said in Gitea minio storage for lfs:

                                Malformed Access Key Id

                                In the docs, it says

                                MINIO_SECRET_ACCESS_KEY = {secret-key}
                                

                                You have to omit the curly braces . Maybe you put curly braces in your config? Could that be it?

                                W 1 Reply Last reply
                                0
                                • girishG girish

                                  @Wirv said in Gitea minio storage for lfs:

                                  Malformed Access Key Id

                                  In the docs, it says

                                  MINIO_SECRET_ACCESS_KEY = {secret-key}
                                  

                                  You have to omit the curly braces . Maybe you put curly braces in your config? Could that be it?

                                  W Offline
                                  W Offline
                                  Wirv
                                  wrote on last edited by Wirv
                                  #20

                                  @girish said in Gitea minio storage for lfs:

                                  You have to omit the curly braces . Maybe you put curly braces in your config? Could that be it?

                                  I actually tried both ways and the same error

                                  2023/02/01 16:20:39 ...les/storage/minio.go:91:NewMinioStorage() [I] Creating Minio storage at s3.eu-central-003.backblazeb2.com:build2bit with base path attachments/
                                  2023/02/01 16:20:39 routers/init.go:59:mustInit() [F] code.gitea.io/gitea/modules/storage.Init failed: Malformed Access Key Id
                                  Received signal 15; terminating.
                                  
                                  girishG 1 Reply Last reply
                                  0
                                  • W Wirv

                                    @girish said in Gitea minio storage for lfs:

                                    You have to omit the curly braces . Maybe you put curly braces in your config? Could that be it?

                                    I actually tried both ways and the same error

                                    2023/02/01 16:20:39 ...les/storage/minio.go:91:NewMinioStorage() [I] Creating Minio storage at s3.eu-central-003.backblazeb2.com:build2bit with base path attachments/
                                    2023/02/01 16:20:39 routers/init.go:59:mustInit() [F] code.gitea.io/gitea/modules/storage.Init failed: Malformed Access Key Id
                                    Received signal 15; terminating.
                                    
                                    girishG Offline
                                    girishG Offline
                                    girish
                                    Staff
                                    wrote on last edited by
                                    #21

                                    @Wirv It seems that error may be from backblaze b2 and not gitea - https://www.reddit.com/r/backblaze/comments/u9ivrh/malformed_access_key_id/ . The user there succeeded by regenerating the key. Which makes me wonder, does your key have fancy characters like "=" , "/" , "[" or something?

                                    W 2 Replies Last reply
                                    0
                                    • girishG girish

                                      @Wirv It seems that error may be from backblaze b2 and not gitea - https://www.reddit.com/r/backblaze/comments/u9ivrh/malformed_access_key_id/ . The user there succeeded by regenerating the key. Which makes me wonder, does your key have fancy characters like "=" , "/" , "[" or something?

                                      W Offline
                                      W Offline
                                      Wirv
                                      wrote on last edited by
                                      #22

                                      @girish unfortunately yes, what do I do, try to regenerate it until a key without special characters comes out?

                                      1 Reply Last reply
                                      0
                                      • girishG girish

                                        @Wirv It seems that error may be from backblaze b2 and not gitea - https://www.reddit.com/r/backblaze/comments/u9ivrh/malformed_access_key_id/ . The user there succeeded by regenerating the key. Which makes me wonder, does your key have fancy characters like "=" , "/" , "[" or something?

                                        W Offline
                                        W Offline
                                        Wirv
                                        wrote on last edited by Wirv
                                        #23

                                        @girish now it seems to work, the push takes a long time for a single file of less than a gb (for security inserted in the gitattribute as lfs) but the bucket is empty after the push, I don't understand where to throw it.
                                        I made sure I removed gitea's default lfs path from the app.ini

                                        girishG 1 Reply Last reply
                                        0
                                        • W Wirv

                                          @girish now it seems to work, the push takes a long time for a single file of less than a gb (for security inserted in the gitattribute as lfs) but the bucket is empty after the push, I don't understand where to throw it.
                                          I made sure I removed gitea's default lfs path from the app.ini

                                          girishG Offline
                                          girishG Offline
                                          girish
                                          Staff
                                          wrote on last edited by
                                          #24

                                          @Wirv OK, I don't really know that part since I have never tried LFS myself. I just wanted to get you over the configuration hurdle.

                                          W 2 Replies 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