how to upgrade #1026

New Issue

GiteaMirror · 2025-11-02T03:45:47-06:00

GiteaMirror commented

2025-11-02 03:45:47 -06:00

Originally created by @MetaiR on GitHub (Aug 30, 2017).

hello,
I saw your doc about upgrading from Gogs but I couldn't find any references for upgrading to new version of your wonderful program.

we are using it in our server and it has projects, web hooks and etc and I want to upgrade it without any trouble or crashes (specially about losing data)

so how should I upgrade it?

Originally created by @MetaiR on GitHub (Aug 30, 2017). hello, I saw your doc about upgrading from Gogs but I couldn't find any references for upgrading to new version of your wonderful program. we are using it in our server and it has projects, web hooks and etc and I want to upgrade it without any trouble or crashes (specially about losing data) so how should I upgrade it?

GiteaMirror added the type/docs label 2025-11-02 03:45:47 -06:00

GiteaMirror closed this issue

2025-11-02 03:45:47 -06:00

GiteaMirror commented

2025-11-02 03:45:47 -06:00

@lafriks commented on GitHub (Aug 31, 2017):

I'm currently working on fix to make it possible

@lafriks commented on GitHub (Aug 31, 2017): I'm currently working on fix to make it possible

GiteaMirror commented

2025-11-02 03:45:48 -06:00

@MetaiR commented on GitHub (Sep 1, 2017):

@lafriks
it's very good to hear that.
you think when it will be available?

@MetaiR commented on GitHub (Sep 1, 2017): @lafriks it's very good to hear that. you think when it will be available?

GiteaMirror commented

2025-11-02 03:45:48 -06:00

@kmare commented on GitHub (Sep 3, 2017):

I didn't setup any webhooks etc, just the basics. I'm using gitea just for my personal git needs on a rpi3. The only thing I have to do to upgrade is replacing the current binary with the newest version. Of course before doing that, I always keep a backup just to be safe. When you first run the updated version (./gitea web), wait a little bit (just a few seconds just to upgrade whatever it needs to I guess ) and you're good to go.
I updated from 1.1.2 to 1.1.3 and now to 1.2.0 without any problems so far. Everything worked like a charm!

@kmare commented on GitHub (Sep 3, 2017): I didn't setup any webhooks etc, just the basics. I'm using gitea just for my personal git needs on a rpi3. The only thing I have to do to upgrade is replacing the current binary with the newest version. Of course before doing that, I always keep a backup just to be safe. When you first run the updated version (./gitea web), wait a little bit (just a few seconds just to upgrade whatever it needs to I guess ) and you're good to go. I updated from 1.1.2 to 1.1.3 and now to 1.2.0 without any problems so far. Everything worked like a charm!

GiteaMirror commented

2025-11-02 03:45:48 -06:00

@lafriks commented on GitHub (Sep 3, 2017):

Gogs -> 1.1 -> 1.2 does work but direct upgrade to 1.2 does not currently

@lafriks commented on GitHub (Sep 3, 2017): Gogs -> 1.1 -> 1.2 does work but direct upgrade to 1.2 does not currently

GiteaMirror commented

2025-11-02 03:45:48 -06:00

@MetaiR commented on GitHub (Sep 3, 2017):

so how should I upgrade? can the team create a doc at least?

@MetaiR commented on GitHub (Sep 3, 2017): so how should I upgrade? can the team create a doc at least?

GiteaMirror commented

2025-11-02 03:45:48 -06:00

@lafriks commented on GitHub (Sep 4, 2017):

@MetaiR There already is documentation on how to do that - https://docs.gitea.io/en-us/upgrade-from-gogs/

but if you want to upgrade directly to 1.2 than please wait for #2460 to merged to 1.2 branch and rc2/final version of 1.2.0

@lafriks commented on GitHub (Sep 4, 2017): @MetaiR There already is documentation on how to do that - https://docs.gitea.io/en-us/upgrade-from-gogs/ but if you want to upgrade directly to 1.2 than please wait for #2460 to merged to 1.2 branch and rc2/final version of 1.2.0

GiteaMirror commented

2025-11-02 03:45:49 -06:00

@MetaiR commented on GitHub (Sep 5, 2017):

@lafriks
is there any difference between upgrading from Gogs or from Gitea itself?
I mean, your doc is about upgrading from Gogs to Gitea but my case is upgrading from an old version of it to the new one, so is that be enough for my situation? (I mean the doc you mentioned)

@MetaiR commented on GitHub (Sep 5, 2017): @lafriks is there any difference between upgrading from `Gogs` or from `Gitea` itself? I mean, your doc is about upgrading from `Gogs` to `Gitea` but my case is upgrading from an old version of it to the new one, so is that be enough for my situation? (I mean the doc you mentioned)

GiteaMirror commented

2025-11-02 03:45:49 -06:00

@lunny commented on GitHub (Sep 5, 2017):

Since Gitea developed based on Gogs, so old Gods like an old gitea version. The both process should be the same.

@lunny commented on GitHub (Sep 5, 2017): Since Gitea developed based on Gogs, so old Gods like an old gitea version. The both process should be the same.

GiteaMirror referenced this issue

2025-11-02 11:52:58 -06:00

[PR #1026] [MERGED] fix: Admin can see all private repositories on Explore page. #15716

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#1026