github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 14:34:54 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Master to master replica #4845

New Issue
Closed
opened 2025-11-02 06:04:45 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 06:04:45 -06:00
Owner
Copy Link

Originally created by @Hemanthdev on GitHub (Feb 13, 2020).

Master to master replication is available for gitea.

Please guide me on this setup document

Originally created by @Hemanthdev on GitHub (Feb 13, 2020). Master to master replication is available for gitea. Please guide me on this setup document
GiteaMirror added the type/proposal label 2025-11-02 06:04:45 -06:00
GiteaMirror commented 2025-11-02 06:04:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 13, 2020):

Please give more detail.

@lunny commented on GitHub (Feb 13, 2020): Please give more detail.
GiteaMirror commented 2025-11-02 06:04:46 -06:00
Author
Owner
Copy Link

@Hemanthdev commented on GitHub (Feb 14, 2020):

We are having the 3 office. So will will install gitea in 3 office.
We need to replication all 3 server to each other...

1 office people will connect to 1 server -- Gitea Master1.
2 office people will connect to 2 server -- Gitea Master2
3 office people will connect to server 3 -- Gitea Master3.

Or

all will connect to Gitea Master1 to push the code.they will pull repo for local server.

@Hemanthdev commented on GitHub (Feb 14, 2020): We are having the 3 office. So will will install gitea in 3 office. We need to replication all 3 server to each other... 1 office people will connect to 1 server -- Gitea Master1. 2 office people will connect to 2 server -- Gitea Master2 3 office people will connect to server 3 -- Gitea Master3. Or all will connect to Gitea Master1 to push the code.they will pull repo for local server.
GiteaMirror commented 2025-11-02 06:04:46 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 15, 2020):

Why not share the same Gitea server?

@lunny commented on GitHub (Feb 15, 2020): Why not share the same Gitea server?
GiteaMirror commented 2025-11-02 06:04:46 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Feb 15, 2020):

Gitea does not support clustering currently

@lafriks commented on GitHub (Feb 15, 2020): Gitea does not support clustering currently
GiteaMirror commented 2025-11-02 06:04:47 -06:00
Author
Owner
Copy Link

@Hemanthdev commented on GitHub (Feb 17, 2020):

kubernetes clustering will work or anyother option.

3 office will connect via VPN

@Hemanthdev commented on GitHub (Feb 17, 2020): kubernetes clustering will work or anyother option. 3 office will connect via VPN
GiteaMirror commented 2025-11-02 06:04:47 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Feb 18, 2020):

Kubernates cluster will not work either currently

@lafriks commented on GitHub (Feb 18, 2020): Kubernates cluster will not work either currently
GiteaMirror commented 2025-11-02 06:04:47 -06:00
Author
Owner
Copy Link

@Hemanthdev commented on GitHub (Feb 20, 2020):

Why not share the same Gitea server?

This will impact the internet bandwidth to another office.
In each office, the employer is more 150+

@Hemanthdev commented on GitHub (Feb 20, 2020): > Why not share the same Gitea server? This will impact the internet bandwidth to another office. In each office, the employer is more 150+
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4845
Delete Branch "%!s()"

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?