gitea/models/migrations
wxiaoguang 2cdf260f42
Refactor path & config system (#25330)
# 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
2023-06-21 13:50:26 +08:00
..
base Refactor path & config system (#25330) 2023-06-21 13:50:26 +08:00
fixtures Remove wrongly added column on migration test fixtures (#23456) 2023-03-14 19:49:59 +08:00
v1_6 Update go dev dependencies (#22064) 2022-12-08 16:21:37 +08:00
v1_7 Update go dev dependencies (#22064) 2022-12-08 16:21:37 +08:00
v1_8 Update go dev dependencies (#22064) 2022-12-08 16:21:37 +08:00
v1_9 Update go dev dependencies (#22064) 2022-12-08 16:21:37 +08:00
v1_10 Fix all possible setting error related storages and added some tests (#23911) 2023-06-14 11:42:38 +08:00
v1_11 Fix all possible setting error related storages and added some tests (#23911) 2023-06-14 11:42:38 +08:00
v1_12 Refactor `setting.Database.UseXXX` to methods (#23354) 2023-03-07 18:51:06 +08:00
v1_13 Remove most path-based golangci exclusions (#24214) 2023-04-19 22:08:01 -04:00
v1_14 Remove most path-based golangci exclusions (#24214) 2023-04-19 22:08:01 -04:00
v1_15 Refactor `setting.Database.UseXXX` to methods (#23354) 2023-03-07 18:51:06 +08:00
v1_16 Refactor `setting.Database.UseXXX` to methods (#23354) 2023-03-07 18:51:06 +08:00
v1_17 Drop migration for ForeignReference (#23605) 2023-03-23 15:01:55 -04:00
v1_18 Refactor `setting.Database.UseXXX` to methods (#23354) 2023-03-07 18:51:06 +08:00
v1_19 Refactor `setting.Database.UseXXX` to methods (#23354) 2023-03-07 18:51:06 +08:00
v1_20 Redesign Scoped Access Tokens (#24767) 2023-06-04 20:57:16 +02:00
v1_21 Support configuration variables on Gitea Actions (#24724) 2023-06-20 22:54:15 +00:00
migrations.go Support configuration variables on Gitea Actions (#24724) 2023-06-20 22:54:15 +00:00