fa0b5b14c2
Replace #25580 Fix #19453 The problem was: when users set "GITEA__XXX__YYY" , the "install page" doesn't respect it. So, to make the result consistent and avoid surprising end users, now the "install page" also writes the environment variables to the config file. And, to make things clear, there are enough messages on the UI to tell users what will happen. There are some necessary/related changes to `environment-to-ini.go`: * The "--clear" flag is removed and it was incorrectly written there. The "clear" operation should be done if INSTALL_LOCK=true * The "--prefix" flag is removed because it's never used, never documented and it only causes inconsistent behavior.  |
||
|---|---|---|
| .. | ||
| autocompletion | ||
| backport | ||
| environment-to-ini | ||
| fhs-compliant-script | ||
| fixtures | ||
| gitea-monitoring-mixin | ||
| ide | ||
| init | ||
| launchd | ||
| legal | ||
| options/label | ||
| supervisor | ||
| systemd | ||
| README | ||
| update_dependencies.sh | ||
| upgrade.sh | ||
README
All files in subdirectories are templates, do modifications based on your environment first.