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.

Sign up for GitHub

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

Jump to bottom

High Availabilty or Disaster Recovery topology support would be nice #19371

Closed
cmpunches opened this issue Apr 11, 2022 · 1 comment
Closed

High Availabilty or Disaster Recovery topology support would be nice #19371

cmpunches opened this issue Apr 11, 2022 · 1 comment
Labels
issue/duplicate The issue has already been reported.

Comments

@cmpunches
Copy link

Feature Description

The ability to stand up another instance behind a load balancer or to stand up a disaster recovery instance in another datacenter would be nice.

This being missing has been a barrier to suggesting it as the SCM component in some of my clients' environments.

Screenshots

No response
@cmpunches cmpunches 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 Apr 11, 2022
@techknowlogick
Copy link
Member

techknowlogick commented Apr 11, 2022 •
edited
Loading

closing as dupe of either #13791 or #4114

@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 Apr 11, 2022
@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.
Assignees
No one assigned
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@techknowlogick @cmpunches