You've already forked gitea-ubuntu-multi
Because reading the README is faster than debugging
This commit is contained in:
24
README.md
24
README.md
@@ -7,16 +7,24 @@
|
||||
[](#)
|
||||
[](./LICENSE)
|
||||
|
||||
Deploy **multiple isolated Gitea servers** on Ubuntu 24.04 — each with its own:
|
||||
✔ service
|
||||
✔ database
|
||||
✔ config
|
||||
✔ data directory
|
||||
✔ port
|
||||
Install multiple Gitea instances on Ubuntu 24.04 server.
|
||||
|
||||
All instances share one Gitea binary — upgrades are **single-file** replacements.
|
||||
This is not a demo environment.
|
||||
This is a production-focused installer built to scale cleanly and update centrally.
|
||||
|
||||
This is a **production installer**, not a test script.
|
||||
## Why this installer exists
|
||||
Running several Gitea installations shouldn't require manual setup each time. This script makes multi-instance hosting repeatable.
|
||||
|
||||
## What this installer does
|
||||
✔ Auto-numbers instances (gitea1, gitea2 …)
|
||||
✔ Creates isolated DB + service per instance
|
||||
✔ Assigns final ports safely post-install
|
||||
✔ Includes robots + sitemap generation
|
||||
✔ Shared binary — one upgrade updates all
|
||||
|
||||
## What this installer does *NOT* do
|
||||
It won’t stop you from running the script without reading the documentation like there’s no tomorrow.
|
||||
Skip the README, and whatever happens next is your headache, not a bug report.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user