The link to gitea.service in the docs points to the the main branch instead of the last released version #10888

New Issue

GiteaMirror · 2025-11-02T09:21:14-06:00

GiteaMirror commented

2025-11-02 09:21:14 -06:00

Originally created by @Equbuxu on GitHub (May 21, 2023).

Description

The page https://docs.gitea.io/en-us/installation/linux-service/ has a link to https://github.com/go-gitea/gitea/blob/main/contrib/systemd/gitea.service. It seems like this file was recently modified, adding

Type=notify
...
WatchdogSec=30s

From what I understand, the version of gitea that supports these watchdog notifications isn't released yet, meaning that the config is wrong if you are using the latest version. This gave me quite the headache, first trying to figure out why the service gets stuck in the "activated" state (no notification, no activation), and then why I'm getting random 502 errors (killed by watchdog every 30 seconds). So, maybe the link in the docs should be changed to point to a different branch, or somewhere else entirely? This will of course mean the link will need to be updated with the new releases, so feel free to close this issue as "won't do" if you'd rather keep it as is.

Gitea Version

1.19.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Installed the binary as described in https://docs.gitea.io/en-us/installation/install-from-binary/

Database

None

Originally created by @Equbuxu on GitHub (May 21, 2023). ### Description The page https://docs.gitea.io/en-us/installation/linux-service/ has a link to https://github.com/go-gitea/gitea/blob/main/contrib/systemd/gitea.service. It seems like this file was recently modified, adding ``` Type=notify ... WatchdogSec=30s ``` From what I understand, the version of gitea that supports these watchdog notifications isn't released yet, meaning that the config is wrong if you are using the latest version. This gave me quite the headache, first trying to figure out why the service gets stuck in the "activated" state (no notification, no activation), and then why I'm getting random 502 errors (killed by watchdog every 30 seconds). So, maybe the link in the docs should be changed to point to a different branch, or somewhere else entirely? This will of course mean the link will need to be updated with the new releases, so feel free to close this issue as "won't do" if you'd rather keep it as is. ### Gitea Version 1.19.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Installed the binary as described in https://docs.gitea.io/en-us/installation/install-from-binary/ ### Database None

GiteaMirror added the type/docs type/bug labels 2025-11-02 09:21:14 -06:00

GiteaMirror closed this issue

2025-11-02 09:21:14 -06:00

GiteaMirror commented

2025-11-02 09:21:15 -06:00

@lunny commented on GitHub (May 25, 2023):

Since versioned document site is up. I think this could be closed. see https://docs.gitea.com

@lunny commented on GitHub (May 25, 2023): Since versioned document site is up. I think this could be closed. see https://docs.gitea.com

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