You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2cdf260f42
# The problem
There were many "path tricks":
* By default, Gitea uses its program directory as its work path
* Gitea tries to use the "work path" to guess its "custom path" and
"custom conf (app.ini)"
* Users might want to use other directories as work path
* The non-default work path should be passed to Gitea by GITEA_WORK_DIR
or "--work-path"
* But some Gitea processes are started without these values
* The "serv" process started by OpenSSH server
* The CLI sub-commands started by site admin
* The paths are guessed by SetCustomPathAndConf again and again
* The default values of "work path / custom path / custom conf" can be
changed when compiling
# The solution
* Use `InitWorkPathAndCommonConfig` to handle these path tricks, and use
test code to cover its behaviors.
* When Gitea's web server runs, write the WORK_PATH to "app.ini", this
value must be the most correct one, because if this value is not right,
users would find that the web UI doesn't work and then they should be
able to fix it.
* Then all other sub-commands can use the WORK_PATH in app.ini to
initialize their paths.
* By the way, when Gitea starts for git protocol, it shouldn't output
any log, otherwise the git protocol gets broken and client blocks
forever.
The "work path" priority is: WORK_PATH in app.ini > cmd arg --work-path
> env var GITEA_WORK_DIR > builtin default
The "app.ini" searching order is: cmd arg --config > cmd arg "work path
/ custom path" > env var "work path / custom path" > builtin default
## ⚠️ BREAKING
If your instance's "work path / custom path / custom conf" doesn't meet
the requirements (eg: work path must be absolute), Gitea will report a
fatal error and exit. You need to set these values according to the
error log.
----
Close #24818
Close #24222
Close #21606
Close #21498
Close #25107
Close #24981
Maybe close #24503
Replace #23301
Replace #22754
And maybe more
|
1 year ago | |
|---|---|---|
| .. | ||
| actions | 1 year ago | |
| activities | 1 year ago | |
| admin | 1 year ago | |
| asymkey | 1 year ago | |
| auth | 1 year ago | |
| avatars | 1 year ago | |
| db | 1 year ago | |
| dbfs | 1 year ago | |
| fixtures | 1 year ago | |
| git | 1 year ago | |
| issues | 1 year ago | |
| migrations | 1 year ago | |
| organization | 1 year ago | |
| packages | 1 year ago | |
| perm | 1 year ago | |
| project | 1 year ago | |
| pull | 2 years ago | |
| repo | 1 year ago | |
| secret | 1 year ago | |
| shared/types | 1 year ago | |
| system | 1 year ago | |
| unit | 1 year ago | |
| unittest | 1 year ago | |
| user | 1 year ago | |
| webhook | 1 year ago | |
| error.go | 2 years ago | |
| fixture_generation.go | 2 years ago | |
| fixture_test.go | 2 years ago | |
| main_test.go | 1 year ago | |
| migrate.go | 2 years ago | |
| migrate_test.go | 2 years ago | |
| org.go | 2 years ago | |
| org_team.go | 1 year ago | |
| org_team_test.go | 2 years ago | |
| org_test.go | 2 years ago | |
| repo.go | 1 year ago | |
| repo_collaboration.go | 2 years ago | |
| repo_collaboration_test.go | 1 year ago | |
| repo_test.go | 2 years ago | |
| repo_transfer.go | 1 year ago | |
| repo_transfer_test.go | 2 years ago | |