github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 04:42:51 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

HA configuration? #1171

New Issue
Closed
opened 2025-11-02 03:51:17 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 03:51:17 -06:00
Owner
Copy Link

Originally created by @zfLQ2qx2 on GitHub (Oct 20, 2017).

I realize that that gitea was probably not engineered for concurrent access by multiple frontends on different servers - however,

  • if I had a common database backend
  • and hosted the repos on a networked filesystem
  • and could guarantee that no two frontends would update the same repo at the same time
    then do you think it would be feasible to have multiple gitea instances running concurrently without corrupting?
Originally created by @zfLQ2qx2 on GitHub (Oct 20, 2017). I realize that that gitea was probably not engineered for concurrent access by multiple frontends on different servers - however, * if I had a common database backend * and hosted the repos on a networked filesystem * and could guarantee that no two frontends would update the same repo at the same time then do you think it would be feasible to have multiple gitea instances running concurrently without corrupting?
GiteaMirror added the type/question label 2025-11-02 03:51:17 -06:00
GiteaMirror commented 2025-11-02 03:51:17 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Oct 20, 2017):

Currently, Gitea cannot guarantee that. It's safety on a single machine.

@lunny commented on GitHub (Oct 20, 2017): Currently, Gitea cannot guarantee that. It's safety on a single machine.
GiteaMirror commented 2025-11-02 03:51:18 -06:00
Author
Owner
Copy Link

@zfLQ2qx2 commented on GitHub (Oct 20, 2017):

@lunny Ok, thanks for letting me know for certain

@zfLQ2qx2 commented on GitHub (Oct 20, 2017): @lunny Ok, thanks for letting me know for certain
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/question
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#1171
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?