Reload config or Inform user to restart Gitea when settings change #4487

New Issue

GiteaMirror · 2025-11-02T05:52:27-06:00

GiteaMirror commented

2025-11-02 05:52:27 -06:00

Originally created by @mschoettle on GitHub (Dec 15, 2019).

Gitea version (or commit ref): 1.10.1
Git version: 2.22.2
Operating system: Raspian Buster (10)
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite

Description

I freshly installed Gitea 1.10.1 (with Docker if that makes a difference) on my Raspberry Pi. Upon accessing the web interface I got to see the setup page where I changed the (default) DB setting from SQLite to MySQL. Once the installation completed everything seemed to work. The one exception being the heat map which I saw in #6405 that if the settings changed the Gitea should be restarted (once I did it worked).

However, it would be great to either reload the config (it seems to know to use another DB for everything else), or simply tell the user to restart Gitea.

Originally created by @mschoettle on GitHub (Dec 15, 2019). - Gitea version (or commit ref): 1.10.1 - Git version: 2.22.2 - Operating system: Raspian Buster (10) - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite ## Description I freshly installed Gitea 1.10.1 (with Docker if that makes a difference) on my Raspberry Pi. Upon accessing the web interface I got to see the setup page where I changed the (default) DB setting from SQLite to MySQL. Once the installation completed everything seemed to work. The one exception being the heat map which I saw in #6405 that if the settings changed the Gitea should be restarted (once I did it worked). However, it would be great to either reload the config (it seems to know to use another DB for everything else), or simply tell the user to restart Gitea.

GiteaMirror added the issue/confirmed type/bug labels 2025-11-02 05:52:27 -06:00

GiteaMirror closed this issue

2025-11-02 05:52:27 -06:00

GiteaMirror commented

2025-11-02 05:52:27 -06:00

@lunny commented on GitHub (Dec 16, 2019):

That's a bug but we should not restart gitea just load the configuration correctly.

@lunny commented on GitHub (Dec 16, 2019): That's a bug but we should not restart gitea just load the configuration correctly.

GiteaMirror commented

2025-11-02 05:52:27 -06:00

@stale[bot] commented on GitHub (Feb 14, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 14, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:52:27 -06:00

@mschoettle commented on GitHub (Feb 14, 2020):

This is still valid.

@mschoettle commented on GitHub (Feb 14, 2020): This is still valid.

GiteaMirror commented

2025-11-02 05:52:28 -06:00

@stale[bot] commented on GitHub (Apr 14, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 14, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:52:28 -06:00

@insanemal commented on GitHub (Jul 14, 2020):

This doesn't look like it's been resolved yet.

It's causing issues with the k8's install I have. However because k8s likes to ensure containers are ready I can't just restart it and have things work.. It's a little, less than fun

@insanemal commented on GitHub (Jul 14, 2020): This doesn't look like it's been resolved yet. It's causing issues with the k8's install I have. However because k8s likes to ensure containers are ready I can't just restart it and have things work.. It's a little, less than fun

GiteaMirror commented

2025-11-02 05:52:28 -06:00

@Duality1k commented on GitHub (Jan 12, 2023):

this issue is still a thing

@Duality1k commented on GitHub (Jan 12, 2023): this issue is still a thing

GiteaMirror commented

2025-11-02 05:52:28 -06:00

@lunny commented on GitHub (Jan 13, 2023):

I think this has been resolved
ref https://github.com/go-gitea/gitea/blob/main/routers/install/install.go#L523

@lunny commented on GitHub (Jan 13, 2023): I think this has been resolved ref https://github.com/go-gitea/gitea/blob/main/routers/install/install.go#L523

GiteaMirror referenced this issue

2025-11-02 13:08:30 -06:00

[PR #4487] [MERGED] Accept 'Data:' in commit graph #17395

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