Add a section in README.md describing how to upgrade from existing Gogs setup #168

New Issue

GiteaMirror · 2025-11-02T03:11:59-06:00

GiteaMirror commented

2025-11-02 03:11:59 -06:00

Originally created by @typeless on GitHub (Dec 27, 2016).

I used to have it done by

mkdir gitea as the working directory for the Gitea server.
Symlink the public and templates directories from the Gitea source tree under the gitea directory.
Symlink the data directory from the existing Gogs installation under the gitea direcotry.
Put the gitea executable under the gitea directory.

But it needs more testing and confirmations to ensure this is the correct.

It seemed to be possible to have both servers running simultaneously given that SQLite3 will manage the transactions properly under multi-process. Though I doubt this is still reliably feasible as the two project continue to diverge.

Anyway, a clear and reliable upgrading path is helpful.

Originally created by @typeless on GitHub (Dec 27, 2016). I used to have it done by 1. `mkdir gitea` as the working directory for the Gitea server. 2. Symlink the `public` and `templates` directories from the Gitea source tree under the `gitea` directory. 3. Symlink the `data` directory from the existing Gogs installation under the `gitea` direcotry. 4. Put the `gitea` executable under the `gitea` directory. But it needs more testing and confirmations to ensure this is the correct. It seemed to be possible to have both servers running simultaneously given that SQLite3 will manage the transactions properly under multi-process. Though I doubt this is still reliably feasible as the two project continue to diverge. Anyway, a clear and reliable upgrading path is helpful.

GiteaMirror added the reviewed/wontfix label 2025-11-02 03:11:59 -06:00

GiteaMirror closed this issue

2025-11-02 03:11:59 -06:00

GiteaMirror commented

2025-11-02 03:12:00 -06:00

@lunny commented on GitHub (Dec 27, 2016):

see https://docs.gitea.io/en-us/upgrade-from-gogs/

@lunny commented on GitHub (Dec 27, 2016): see https://docs.gitea.io/en-us/upgrade-from-gogs/

GiteaMirror commented

2025-11-02 03:12:00 -06:00

@perfaram commented on GitHub (Dec 27, 2016):

What are the main differences from Gogs, anyway ?

@perfaram commented on GitHub (Dec 27, 2016): What are the main differences from Gogs, anyway ?

GiteaMirror commented

2025-11-02 03:12:01 -06:00

@strk commented on GitHub (Dec 27, 2016):

Not many differences in functionality, yet.
Difference is in governance, which some of us think
will result in faster development.

@strk commented on GitHub (Dec 27, 2016): Not many differences in functionality, yet. Difference is in governance, which some of us think will result in faster development.

GiteaMirror commented

2025-11-02 03:12:01 -06:00

@tboerger commented on GitHub (Dec 27, 2016):

The upgrade path is documented in the docs page. We should keep the readme simple and push the people to the localized docs page.

@tboerger commented on GitHub (Dec 27, 2016): The upgrade path is documented in the docs page. We should keep the readme simple and push the people to the localized docs page.

GiteaMirror referenced this issue

2025-11-02 11:41:08 -06:00

[PR #168] [MERGED] fix gofmt error. #15199

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#168