2019-12-27 19:49:42 -05:00
|
|
|
// Copyright 2019 The Gitea Authors. All rights reserved.
|
2022-11-27 13:20:29 -05:00
|
|
|
// SPDX-License-Identifier: MIT
|
2019-12-27 19:49:42 -05:00
|
|
|
|
|
|
|
package main
|
|
|
|
|
|
|
|
import (
|
|
|
|
"os"
|
|
|
|
|
|
|
|
"code.gitea.io/gitea/modules/log"
|
|
|
|
"code.gitea.io/gitea/modules/setting"
|
|
|
|
|
|
|
|
"github.com/urfave/cli"
|
|
|
|
)
|
|
|
|
|
|
|
|
func main() {
|
|
|
|
app := cli.NewApp()
|
|
|
|
app.Name = "environment-to-ini"
|
|
|
|
app.Usage = "Use provided environment to update configuration ini"
|
2023-07-10 17:17:39 -04:00
|
|
|
app.Description = `As a helper to allow docker users to update the forgejo configuration
|
2019-12-27 19:49:42 -05:00
|
|
|
through the environment, this command allows environment variables to
|
|
|
|
be mapped to values in the ini.
|
|
|
|
|
2023-07-10 17:17:39 -04:00
|
|
|
Environment variables of the form "FORGEJO__SECTION_NAME__KEY_NAME"
|
2019-12-27 19:49:42 -05:00
|
|
|
will be mapped to the ini section "[section_name]" and the key
|
|
|
|
"KEY_NAME" with the value as provided.
|
|
|
|
|
2023-07-10 17:17:39 -04:00
|
|
|
Environment variables of the form "FORGEJO__SECTION_NAME__KEY_NAME__FILE"
|
2023-05-23 23:37:22 -04:00
|
|
|
will be mapped to the ini section "[section_name]" and the key
|
|
|
|
"KEY_NAME" with the value loaded from the specified file.
|
|
|
|
|
2019-12-27 19:49:42 -05:00
|
|
|
Environment variables are usually restricted to a reduced character
|
|
|
|
set "0-9A-Z_" - in order to allow the setting of sections with
|
|
|
|
characters outside of that set, they should be escaped as following:
|
|
|
|
"_0X2E_" for ".". The entire section and key names can be escaped as
|
|
|
|
a UTF8 byte string if necessary. E.g. to configure:
|
|
|
|
|
|
|
|
"""
|
|
|
|
...
|
|
|
|
[log.console]
|
|
|
|
COLORIZE=false
|
|
|
|
STDERR=true
|
|
|
|
...
|
|
|
|
"""
|
|
|
|
|
2023-07-10 17:17:39 -04:00
|
|
|
You would set the environment variables: "FORGEJO__LOG_0x2E_CONSOLE__COLORIZE=false"
|
|
|
|
and "FORGEJO__LOG_0x2E_CONSOLE__STDERR=false". Other examples can be found
|
2019-12-27 19:49:42 -05:00
|
|
|
on the configuration cheat sheet.`
|
|
|
|
app.Flags = []cli.Flag{
|
|
|
|
cli.StringFlag{
|
|
|
|
Name: "custom-path, C",
|
|
|
|
Value: setting.CustomPath,
|
|
|
|
Usage: "Custom path file path",
|
|
|
|
},
|
|
|
|
cli.StringFlag{
|
|
|
|
Name: "config, c",
|
|
|
|
Value: setting.CustomConf,
|
|
|
|
Usage: "Custom configuration file path",
|
|
|
|
},
|
|
|
|
cli.StringFlag{
|
|
|
|
Name: "work-path, w",
|
|
|
|
Value: setting.AppWorkPath,
|
2023-07-10 17:17:39 -04:00
|
|
|
Usage: "Set the forgejo working path",
|
2019-12-27 19:49:42 -05:00
|
|
|
},
|
|
|
|
cli.StringFlag{
|
|
|
|
Name: "out, o",
|
|
|
|
Value: "",
|
|
|
|
Usage: "Destination file to write to",
|
|
|
|
},
|
|
|
|
}
|
|
|
|
app.Action = runEnvironmentToIni
|
|
|
|
err := app.Run(os.Args)
|
|
|
|
if err != nil {
|
|
|
|
log.Fatal("Failed to run app with %s: %v", os.Args, err)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
func runEnvironmentToIni(c *cli.Context) error {
|
2023-06-24 10:04:50 -04:00
|
|
|
setting.InitWorkPathAndCfgProvider(os.Getenv, setting.ArgWorkPathAndCustomConf{
|
Refactor path & config system (#25330) (#25416)
Backport #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.
2023-06-22 12:27:18 -04:00
|
|
|
WorkPath: c.String("work-path"),
|
|
|
|
CustomPath: c.String("custom-path"),
|
|
|
|
CustomConf: c.String("config"),
|
|
|
|
})
|
2019-12-27 19:49:42 -05:00
|
|
|
|
Refactor path & config system (#25330) (#25416)
Backport #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.
2023-06-22 12:27:18 -04:00
|
|
|
cfg, err := setting.NewConfigProviderFromFile(setting.CustomConf)
|
2020-11-27 21:42:08 -05:00
|
|
|
if err != nil {
|
2023-06-02 05:27:30 -04:00
|
|
|
log.Fatal("Failed to load custom conf '%s': %v", setting.CustomConf, err)
|
2020-11-27 21:42:08 -05:00
|
|
|
}
|
2019-12-27 19:49:42 -05:00
|
|
|
|
2023-07-10 07:51:05 -04:00
|
|
|
changed := setting.EnvironmentToConfig(cfg, os.Environ())
|
2021-05-13 19:01:05 -04:00
|
|
|
|
2023-05-23 23:37:22 -04:00
|
|
|
// try to save the config file
|
2019-12-27 19:49:42 -05:00
|
|
|
destination := c.String("out")
|
|
|
|
if len(destination) == 0 {
|
|
|
|
destination = setting.CustomConf
|
|
|
|
}
|
2021-05-13 19:01:05 -04:00
|
|
|
if destination != setting.CustomConf || changed {
|
2021-12-01 02:50:01 -05:00
|
|
|
log.Info("Settings saved to: %q", destination)
|
2021-05-13 19:01:05 -04:00
|
|
|
err = cfg.SaveTo(destination)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
2019-12-27 19:49:42 -05:00
|
|
|
}
|
2023-05-23 23:37:22 -04:00
|
|
|
|
|
|
|
return nil
|
2019-12-27 19:49:42 -05:00
|
|
|
}
|