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?
- One question: is
-
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 Great idea! I might do the same with Wasabi. Backblaze is a decent alternative too.
Well worth adding this gem to the instructions/documents.
I finally got around to trying out Gitea, and have to say; love it!
There's a big difference for be with software between like and love, but Gitea is one sweet nicely brewed cup of coffee.
- One question: is
-
@infogulch Great idea! I might do the same with Wasabi. Backblaze is a decent alternative too.
Well worth adding this gem to the instructions/documents.
I finally got around to trying out Gitea, and have to say; love it!
There's a big difference for be with software between like and love, but Gitea is one sweet nicely brewed cup of coffee.
@marcusquinn now the trick is to know how to pronounce it..
-
@marcusquinn now the trick is to know how to pronounce it..
@robi I'm going with Gitier, as in Glacier. Can't imagine anyone would say Gitay?
-
@robi I'm going with Gitier, as in Glacier. Can't imagine anyone would say Gitay?
@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

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

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
-
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 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!
- One question: is
-
@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!
-
@girish Do you think it would be a good idea to document or link to this customization in particular in the Gitea docs?
@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 Do you think it would be a good idea to document or link to this customization in particular in the Gitea docs?
@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 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
-
@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.
-
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.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login
