Gitea minio storage for lfs
-
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.inito 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 = 50And 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.inithe correct place to add gitea custom configurations?
@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 - One question: is
-
@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 -
@Wirv Have you seen https://docs.cloudron.io/apps/gitea/#lfs already? Yes, you need an active minio server or external S3 provider.
-
@Wirv Have you seen https://docs.cloudron.io/apps/gitea/#lfs already? Yes, you need an active minio server or external S3 provider.
@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 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. -
@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?
@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 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.@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 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 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?
@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 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 -
@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 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.
-
@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
