@Wirv I did it by setting this to false
SERVE_DIRECT = true
@Wirv I did it by setting this to false
SERVE_DIRECT = true
@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?
@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
@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 unfortunately yes, what do I do, try to regenerate it until a key without special characters comes out?
@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 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.
@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