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.3k 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.
  • 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
                • girishG girish

                  @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 Offline
                  W Offline
                  Wirv
                  wrote on last edited by
                  #25

                  @girish thank you very much anyway, thanks to you anyway I solved a big problem, I hope someone on the forum can help me conclude or be able to find a solution

                  W 1 Reply Last reply
                  0
                  • girishG girish

                    @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 Offline
                    W Offline
                    Wirv
                    wrote on last edited by
                    #26

                    @girish I finally succeeded! Do you happen to know how multiple repos are managed? Is there a way to diversify buckets per repo or does it handle it well with one bucket for all repos?

                    1 Reply Last reply
                    1
                    • W Wirv

                      @girish thank you very much anyway, thanks to you anyway I solved a big problem, I hope someone on the forum can help me conclude or be able to find a solution

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

                      @Wirv I did it by setting this to false

                      SERVE_DIRECT = true
                      
                      1 Reply Last reply
                      2
                      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