Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running Gitea highly available #19700

Closed
garymoon opened this issue May 13, 2022 · 2 comments
Closed

Running Gitea highly available #19700

garymoon opened this issue May 13, 2022 · 2 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@garymoon
Copy link
Contributor

Feature Description

Hi all,

I'm sorry to knowingly post a dupe, but my hope is to avoid having this question asked again.

I am aware of numerous tickets, the Discord, and the Discourse. Everything I've gathered on this subject so far indicates there are some workarounds to enable such a deployment, but they're a mixed bag of tips and tricks, and spread over a very broad time period. There is also commentary indicating that gitea.com itself is being run in a HA manner, but that the process for its deployment remains undocumented.

Naturally a HA deployment would involve a shared file system (ala NFS) and a HA database, so I'm looking specifically for guidance on how to deploy and configure multiple instances Gitea itself in such an environment (I'm aware crons specifically would need to be addressed, but even on that subject it's unclear to me what the recommendation would be).

I would be happy for this issue to become a living document of sorts, or start one in a Discorse thread (or elsewhere) if preferred. I am also happy to take hints in a raw form, work through them myself, and post a more complete write-up at the end if that would be desired.

I would really appreciate any resources at all, no matter how raw.

Thank you for Gitea! 💙

Screenshots

No response

@garymoon garymoon added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels May 13, 2022
@techknowlogick
Copy link
Member

Closing as dupe of #13791 However you can see https://gitea.com/gitea/helm-chart/pulls/205 for more info about doing what you'd like right now as the helm chart would handle everything for you.

@techknowlogick techknowlogick added issue/duplicate The issue has already been reported. and removed type/proposal The new feature has not been accepted yet but needs to be discussed first. type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels May 13, 2022
@garymoon
Copy link
Contributor Author

Oh fantastic, thank you @techknowlogick! Is there anything I should know about running it HA outside of k8s that I wouldn't get from reading that repo please? (I'm expecting a "no", just can't hurt to ask)

Thanks again! 💙

@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Development

No branches or pull requests

2 participants