gamzinav/forgejo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

In administration documentation about environment variables, point to those for the Go runtime instead of Go compiler (#28859)

Browse Source 
The previous variables are used by the compiler and aren't too useful
for non-developers. The newly listed variables are more likely to be of
interest.

Apologies for this drive-by PR, I probably missed instructions from the
contributors guide. The patch can be regarded as a simple way to explain
the problem and solution. Feel free to close and possibly create a new
PR that does adhere to the contributors guide.
This commit is contained in:
Mechiel Lukkien 2024-01-20 03:12:20 +01:00 committed by GitHub
parent 62f995203a
commit b9d91694af
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/content/administration/environment-variables.en-us.md
View File

@ -27,14 +27,15 @@ GITEA_CUSTOM=/home/gitea/custom ./gitea web
## From Go language ## From Go language
As Gitea is written in Go, it uses some Go variables, such as: As Gitea is written in Go, it uses some variables that influence the behaviour of Go's runtime, such as:
- `GOOS` - `GOMEMLIMIT`
- `GOARCH` - `GOGC`
- [`GOPATH`](https://golang.org/cmd/go/#hdr-GOPATH_environment_variable) - `GOMAXPROCS`
- `GODEBUG`
For documentation about each of the variables available, refer to the For documentation about each of the variables available, refer to the
[official Go documentation](https://golang.org/cmd/go/#hdr-Environment_variables). [official Go documentation on runtime environment variables](https://pkg.go.dev/runtime#hdr-Environment_Variables).
## Gitea files ## Gitea files