Store Gitea data (avatars, attachments, etc.) in Garage/S3 #451
No reviewers
Labels
No Label
service
accounts
service
discourse
service
drone-ci
service
email
service
garage
service
gitea
service
ipfs
service
mastodon
service
postgres
service
remotestorage
service
wiki
service
xmpp
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
release
major
release
minor
release
patch
security
ui/ux
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#451
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/gitea_s3"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This configures Gitea to use a local Garage gateway node to store and retrieve all non-git data in our new Garage cluster.
Also adds a new
garage_gateway
role, which only allows RPC (inter-node) traffic to Garage.Tested/running on
gitea-2
, and I have migrated the existing data to Garage usingmc mirror
(installed manually for this purpose, since it's easy enough and not necessary for other tasks at the moment). I have also tested taking down the node in DC4, which resulted in the expected behavior, i.e. Gitea will still be able to read all data, but not write new data while one zone is unavailable (until/unless the cluster's replication mode is changed if necessary).Looking good!