github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Request: understanding binary updates #2025

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

Originally created by @flobee on GitHub (Jul 7, 2018).

Hi
Can you please help/ guide me to get in touch.
i have added [1] because of missing docs and i try to find a way to update related docs to sent a pull request and end up to this message.

My request: What happens at the DB side when upgrading to a new binary version when just using eg. [2]?

[1] https://github.com/flobee/public/blob/master/shell/gitea/INSTALL_gitea_README.md.sh
[2] https://dl.gitea.io/gitea/master/gitea-master-linux-amd64

Kind regard
Florian

Originally created by @flobee on GitHub (Jul 7, 2018). Hi Can you please help/ guide me to get in touch. i have added [1] because of missing docs and i try to find a way to update related docs to sent a pull request and end up to this message. My request: What happens at the DB side when upgrading to a new binary version when just using eg. [2]? [1] https://github.com/flobee/public/blob/master/shell/gitea/INSTALL_gitea_README.md.sh [2] https://dl.gitea.io/gitea/master/gitea-master-linux-amd64 Kind regard Florian
GiteaMirror added the type/question label 2025-11-02 04:21:34 -06:00
GiteaMirror commented 2025-11-02 04:21:35 -06:00
Author
Owner
Copy Link

@jonasfranz commented on GitHub (Jul 8, 2018):

If you will install the master version you linked, it's going to upgrade your database to the current database version. This includes some migrations which will run. These migrations may contain some refactoring, new columns etc.

@jonasfranz commented on GitHub (Jul 8, 2018): If you will install the master version you linked, it's going to upgrade your database to the current database version. This includes some migrations which will run. These migrations may contain some refactoring, new columns etc.
GiteaMirror commented 2025-11-02 04:21:35 -06:00
Author
Owner
Copy Link

@flobee commented on GitHub (Jul 8, 2018):

Hi, thx for reply.
hmm. Which event triggers the mirgration/setup for the configured db? ./gitea web ? or other action/s (also?) ?
Or is it just implemented in the master binary downloads? If so: Wouldnt it makes sence to have a './gitea [setup|mirgration|upgrade]' action then to skip those parts from the regulary work and offer it for all versions self build/ binary/ cross platforms?

@flobee commented on GitHub (Jul 8, 2018): Hi, thx for reply. hmm. Which event triggers the mirgration/setup for the configured db? ./gitea web ? or other action/s (also?) ? Or is it just implemented in the master binary downloads? If so: Wouldnt it makes sence to have a './gitea [setup|mirgration|upgrade]' action then to skip those parts from the regulary work and offer it for all versions self build/ binary/ cross platforms?
GiteaMirror commented 2025-11-02 04:21:35 -06:00
Author
Owner
Copy Link

@jonasfranz commented on GitHub (Jul 8, 2018):

Everything which uses the database will check which database version you're using and will upgrade automatically. This mechanism is implemented in all version / releases including master, and regualar releases like 1.5.0.

@jonasfranz commented on GitHub (Jul 8, 2018): Everything which uses the database will check which database version you're using and will upgrade automatically. This mechanism is implemented in all version / releases including master, and regualar releases like 1.5.0.
GiteaMirror commented 2025-11-02 04:21:35 -06:00
Author
Owner
Copy Link

@jonasfranz commented on GitHub (Jul 8, 2018):

This action will only be triggered if necessary. Where is the point of having a separate command for this since it is required for the upgrade?

@jonasfranz commented on GitHub (Jul 8, 2018): This action will only be triggered if necessary. Where is the point of having a separate command for this since it is required for the upgrade?
GiteaMirror commented 2025-11-02 04:21:35 -06:00
Author
Owner
Copy Link

@flobee commented on GitHub (Jul 9, 2018):

Hi, I'm just asking/wondering: If any user which logs in (ssh or web interface), an db migration event will be tiggered? Or only the none deamonized events? Then it would be "./gitea web"?

This action will only be triggered if necessary

A kind of unclear for me because: i have to connect to the Db first to check if its not up to date. If each request to the binay will trigger those events. its just a situation of time/number of users when the server crashes 👍 just a thought...
I think its not implemented in that way but i dont know and the docs not telling about upgrades... so i try to bring it up :)

@flobee commented on GitHub (Jul 9, 2018): Hi, I'm just asking/wondering: If any user which logs in (ssh or web interface), an db migration event will be tiggered? Or only the none deamonized events? Then it would be "./gitea web"? > This action will only be triggered if necessary A kind of unclear for me because: i have to connect to the Db first to check if its not up to date. If each request to the binay will trigger those events. its just a situation of time/number of users when the server crashes :+1: just a thought... I think its not implemented in that way but i dont know and the docs not telling about upgrades... so i try to bring it up :)
GiteaMirror commented 2025-11-02 04:21:36 -06:00
Author
Owner
Copy Link

@jonasfranz commented on GitHub (Jul 9, 2018):

@flobee The migration will be started after you exchanged to binary and after you start gitea's webserver via ./gitea web or ./gitea.

@jonasfranz commented on GitHub (Jul 9, 2018): @flobee The migration will be started after you exchanged to binary and after you start gitea's webserver via ./gitea web or ./gitea.
GiteaMirror commented 2025-11-02 04:21:36 -06:00
Author
Owner
Copy Link

@flobee commented on GitHub (Jul 10, 2018):

:) thx 👍

@flobee commented on GitHub (Jul 10, 2018): :) thx :+1:
GiteaMirror commented 2025-11-02 04:21:36 -06:00
Author
Owner
Copy Link

@flobee commented on GitHub (Sep 3, 2018):

Adds project support for debian (9)

@flobee commented on GitHub (Sep 3, 2018): Adds project support for [debian (9)](https://wiki.debian.org/Gitea#Install_gitea_using_binay_packages_from_orgin)
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#2025
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?