Gitea minio storage for lfs

[girish]

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

[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

[infogulch]

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

[A Former User]

@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.

[robi]

G I T ? <g i tea>

[fbartels]

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

[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

[girish]

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

[Wirv]

This post is deleted!

[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.

[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?

[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.

[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?

[Wirv]

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

[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

[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.

[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

[Wirv]

@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?

[Wirv]

@Wirv I did it by setting this to false

SERVE_DIRECT = true