Documentation / installation from binary : keep the same directory in the examples #2211

New Issue

GiteaMirror · 2025-11-02T04:27:21-06:00

GiteaMirror commented

2025-11-02 04:27:21 -06:00

Originally created by @tcharlss on GitHub (Aug 17, 2018).

Gitea version: 280ebcb
Operating system: Linux
Installation: from binary

Description

The documentation is a bit confusing to newcomers such as myself regarding the installation directory, and thus the configuration.
There are 3 different installation directories given in the examples:

In Installation from binary, it's /usr/local/bin/
In Run as a service, it's home/git/gitea/
Then in the example supervisor configuration, it's /home/git/go/src/github.com/go-gitea/gitea/

After reading all this, I was a bit confused and kept asking myself "which one should I use in the end" ?
I think all the articles and all the examples should use the same directory to clear things up.

Originally created by @tcharlss on GitHub (Aug 17, 2018). - Gitea version: 280ebcb - Operating system: Linux - Installation: from binary ## Description The documentation is a bit confusing to newcomers such as myself regarding the installation directory, and thus the configuration. There are 3 different installation directories given in the examples: * In [Installation from binary](https://docs.gitea.io/en-us/install-from-binary/), it's `/usr/local/bin/` * In [Run as a service](https://docs.gitea.io/en-us/linux-service/), it's `home/git/gitea/` * Then in the [example supervisor configuration](https://github.com/go-gitea/gitea/blob/master/contrib/supervisor/gitea), it's `/home/git/go/src/github.com/go-gitea/gitea/` After reading all this, I was a bit confused and kept asking myself "which one should I use in the end" ? I think all the articles and all the examples should use the same directory to clear things up.

GiteaMirror added the type/docs issue/stale labels 2025-11-02 04:27:21 -06:00

GiteaMirror closed this issue

2025-11-02 04:27:22 -06:00

GiteaMirror commented

2025-11-02 04:27:22 -06:00

@lafriks commented on GitHub (Aug 17, 2018):

Installation from binary would be recommended one. Other places need to be updated to conform to that

@lafriks commented on GitHub (Aug 17, 2018): Installation from binary would be recommended one. Other places need to be updated to conform to that

GiteaMirror commented

2025-11-02 04:27:23 -06:00

@stale[bot] commented on GitHub (Jan 13, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 13, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:27:23 -06:00

@stale[bot] commented on GitHub (Feb 20, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 20, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 11:10:32 -06:00

Some translations are not correclty applied #14347

GiteaMirror referenced this issue

2025-11-02 12:06:48 -06:00

[PR #2211] [MERGED] Feature: Timetracking #16288

GiteaMirror referenced this issue