Inconsistent config examples #11813

New Issue

GiteaMirror · 2025-11-02T09:48:34-06:00

GiteaMirror commented

2025-11-02 09:48:34 -06:00

Originally created by @drjswalker on GitHub (Oct 8, 2023).

Description

Hi,

I am a newbie trying to install gitea from binary, and failing badly so far. I'm finding the installation instructions poorly organised (e.g. installation from binary, packages and source are followed by creating services in windows and linux and then we return to installation from docker, kubernates etc. At least make the creating services subheadings, or if they apply to the docker installations put the services info after the installation of the gitea program. Another problem is that the config files, often offered as cut and paste, are inconsistent, especially when it comes to the working directory ( /var/lib/gitea, /home/git/gitea and even /home/git/go/src/github.com/go-gitea/gitea/ in the supervisor config file). I would strongly suggest that there be an unbroken line in the binary installation description that includes all necessary configuration files from the database preparation to installing and testing a single file repository. I'd offer to help, but I haven't yet managed to install it after spending about 5 hours so far.

Gitea Version

Gitea version 1.21.0+rc0-69-g44aca6a65 built with GNU Make 4.3, go1.21.1 : bindata, sqlite, sqlite_unlock_notify

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Raspberry Pi OS

How are you running Gitea?

Trying to install this on a raspberry pi to support my scriptwrting (stage not shell scripts) efforts. Not having much luck.

Database

PostgreSQL

Originally created by @drjswalker on GitHub (Oct 8, 2023). ### Description Hi, I am a newbie trying to install gitea from binary, and failing badly so far. I'm finding the installation instructions poorly organised (e.g. installation from binary, packages and source are followed by creating services in windows and linux and then we return to installation from docker, kubernates etc. At least make the creating services subheadings, or if they apply to the docker installations put the services info after the installation of the gitea program. Another problem is that the config files, often offered as cut and paste, are inconsistent, especially when it comes to the working directory ( /var/lib/gitea, /home/git/gitea and even /home/git/go/src/github.com/go-gitea/gitea/ in the supervisor config file). I would strongly suggest that there be an unbroken line in the binary installation description that includes all necessary configuration files from the database preparation to installing and testing a single file repository. I'd offer to help, but I haven't yet managed to install it after spending about 5 hours so far. ### Gitea Version Gitea version 1.21.0+rc0-69-g44aca6a65 built with GNU Make 4.3, go1.21.1 : bindata, sqlite, sqlite_unlock_notify ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Raspberry Pi OS ### How are you running Gitea? Trying to install this on a raspberry pi to support my scriptwrting (stage not shell scripts) efforts. Not having much luck. ### Database PostgreSQL

GiteaMirror commented

2025-11-02 09:48:34 -06:00

@eeyrjmr commented on GitHub (Oct 8, 2023):

see https://github.com/go-gitea/gitea/pull/27461

@eeyrjmr commented on GitHub (Oct 8, 2023): see https://github.com/go-gitea/gitea/pull/27461

GiteaMirror commented

2025-11-02 09:48:35 -06:00

@wxiaoguang commented on GitHub (Oct 9, 2023):

Put gitea binary into a directory, eg: /data/gitea/gitea
Change the owner, eg: chown git:git /data/gitea/gitea
Use git user to run it: sudo -u git /data/gitea/gitea
Finish the installation, and use the same user git in your systemd

Then everything should be fine. The "working directory" trick is not needed anymore.

@wxiaoguang commented on GitHub (Oct 9, 2023): 1. Put `gitea` binary into a directory, eg: `/data/gitea/gitea` 2. Change the owner, eg: `chown git:git /data/gitea/gitea` 3. Use `git` user to run it: `sudo -u git /data/gitea/gitea` 4. Finish the installation, and use the same user `git` in your systemd Then everything should be fine. The "working directory" trick is not needed anymore.

GiteaMirror commented

2025-11-02 09:48:35 -06:00

@lng2020 commented on GitHub (Oct 9, 2023):

The supervisor config file and relevant docs were from 6 years ago when even go mod was not available. Will update it later.

@lng2020 commented on GitHub (Oct 9, 2023): The supervisor config file and relevant docs were from 6 years ago when even go mod was not available. Will update it later.

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