2020-12-26 22:34:19 -05:00
|
|
|
// Copyright 2020 The Gitea Authors. All rights reserved.
|
2022-11-27 13:20:29 -05:00
|
|
|
// SPDX-License-Identifier: MIT
|
2020-12-26 22:34:19 -05:00
|
|
|
|
|
|
|
package cmd
|
|
|
|
|
|
|
|
import (
|
2022-07-01 02:47:44 -05:00
|
|
|
"strings"
|
2020-12-26 22:34:19 -05:00
|
|
|
|
2021-05-10 02:57:45 -05:00
|
|
|
"code.gitea.io/gitea/modules/private"
|
2020-12-26 22:34:19 -05:00
|
|
|
"code.gitea.io/gitea/modules/setting"
|
|
|
|
|
2023-07-21 04:28:19 -05:00
|
|
|
"github.com/urfave/cli/v2"
|
2020-12-26 22:34:19 -05:00
|
|
|
)
|
|
|
|
|
|
|
|
// CmdRestoreRepository represents the available restore a repository sub-command.
|
2023-07-21 04:28:19 -05:00
|
|
|
var CmdRestoreRepository = &cli.Command{
|
2020-12-26 22:34:19 -05:00
|
|
|
Name: "restore-repo",
|
|
|
|
Usage: "Restore the repository from disk",
|
|
|
|
Description: "This is a command for restoring the repository data.",
|
|
|
|
Action: runRestoreRepository,
|
|
|
|
Flags: []cli.Flag{
|
2023-07-21 04:28:19 -05:00
|
|
|
&cli.StringFlag{
|
|
|
|
Name: "repo_dir",
|
|
|
|
Aliases: []string{"r"},
|
|
|
|
Value: "./data",
|
|
|
|
Usage: "Repository dir path to restore from",
|
2020-12-26 22:34:19 -05:00
|
|
|
},
|
2023-07-21 04:28:19 -05:00
|
|
|
&cli.StringFlag{
|
2020-12-26 22:34:19 -05:00
|
|
|
Name: "owner_name",
|
|
|
|
Value: "",
|
|
|
|
Usage: "Restore destination owner name",
|
|
|
|
},
|
2023-07-21 04:28:19 -05:00
|
|
|
&cli.StringFlag{
|
2020-12-26 22:34:19 -05:00
|
|
|
Name: "repo_name",
|
|
|
|
Value: "",
|
|
|
|
Usage: "Restore destination repository name",
|
|
|
|
},
|
2023-07-21 04:28:19 -05:00
|
|
|
&cli.StringFlag{
|
2020-12-26 22:34:19 -05:00
|
|
|
Name: "units",
|
2022-07-01 02:47:44 -05:00
|
|
|
Value: "",
|
|
|
|
Usage: `Which items will be restored, one or more units should be separated as comma.
|
2020-12-26 22:34:19 -05:00
|
|
|
wiki, issues, labels, releases, release_assets, milestones, pull_requests, comments are allowed. Empty means all units.`,
|
|
|
|
},
|
2023-07-21 04:28:19 -05:00
|
|
|
&cli.BoolFlag{
|
2022-01-26 04:45:51 -05:00
|
|
|
Name: "validation",
|
|
|
|
Usage: "Sanity check the content of the files before trying to load them",
|
|
|
|
},
|
2020-12-26 22:34:19 -05:00
|
|
|
},
|
|
|
|
}
|
|
|
|
|
2021-07-14 09:43:13 -05:00
|
|
|
func runRestoreRepository(c *cli.Context) error {
|
|
|
|
ctx, cancel := installSignals()
|
|
|
|
defer cancel()
|
|
|
|
|
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 00:50:26 -05:00
|
|
|
setting.MustInstalled()
|
2022-07-01 02:47:44 -05:00
|
|
|
var units []string
|
|
|
|
if s := c.String("units"); s != "" {
|
|
|
|
units = strings.Split(s, ",")
|
|
|
|
}
|
Refactor internal API for git commands, use meaningful messages instead of "Internal Server Error" (#23687)
# Why this PR comes
At first, I'd like to help users like #23636 (there are a lot)
The unclear "Internal Server Error" is quite anonying, scare users,
frustrate contributors, nobody knows what happens.
So, it's always good to provide meaningful messages to end users (of
course, do not leak sensitive information).
When I started working on the "response message to end users", I found
that the related code has a lot of technical debt. A lot of copy&paste
code, unclear fields and usages.
So I think it's good to make everything clear.
# Tech Backgrounds
Gitea has many sub-commands, some are used by admins, some are used by
SSH servers or Git Hooks. Many sub-commands use "internal API" to
communicate with Gitea web server.
Before, Gitea server always use `StatusCode + Json "err" field` to
return messages.
* The CLI sub-commands: they expect to show all error related messages
to site admin
* The Serv/Hook sub-commands (for git clients): they could only show
safe messages to end users, the error log could only be recorded by
"SSHLog" to Gitea web server.
In the old design, it assumes that:
* If the StatusCode is 500 (in some functions), then the "err" field is
error log, shouldn't be exposed to git client.
* If the StatusCode is 40x, then the "err" field could be exposed. And
some functions always read the "err" no matter what the StatusCode is.
The old code is not strict, and it's difficult to distinguish the
messages clearly and then output them correctly.
# This PR
To help to remove duplicate code and make everything clear, this PR
introduces `ResponseExtra` and `requestJSONResp`.
* `ResponseExtra` is a struct which contains "extra" information of a
internal API response, including StatusCode, UserMsg, Error
* `requestJSONResp` is a generic function which can be used for all
cases to help to simplify the calls.
* Remove all `map["err"]`, always use `private.Response{Err}` to
construct error messages.
* User messages and error messages are separated clearly, the `fail` and
`handleCliResponseExtra` will output correct messages.
* Replace all `Internal Server Error` messages with meaningful (still
safe) messages.
This PR saves more than 300 lines, while makes the git client messages
more clear.
Many gitea-serv/git-hook related essential functions are covered by
tests.
---------
Co-authored-by: delvh <dev.lh@web.de>
2023-03-29 01:32:26 -05:00
|
|
|
extra := private.RestoreRepo(
|
2021-07-14 09:43:13 -05:00
|
|
|
ctx,
|
|
|
|
c.String("repo_dir"),
|
|
|
|
c.String("owner_name"),
|
|
|
|
c.String("repo_name"),
|
2022-07-01 02:47:44 -05:00
|
|
|
units,
|
2022-01-26 04:45:51 -05:00
|
|
|
c.Bool("validation"),
|
2021-05-10 02:57:45 -05:00
|
|
|
)
|
Refactor internal API for git commands, use meaningful messages instead of "Internal Server Error" (#23687)
# Why this PR comes
At first, I'd like to help users like #23636 (there are a lot)
The unclear "Internal Server Error" is quite anonying, scare users,
frustrate contributors, nobody knows what happens.
So, it's always good to provide meaningful messages to end users (of
course, do not leak sensitive information).
When I started working on the "response message to end users", I found
that the related code has a lot of technical debt. A lot of copy&paste
code, unclear fields and usages.
So I think it's good to make everything clear.
# Tech Backgrounds
Gitea has many sub-commands, some are used by admins, some are used by
SSH servers or Git Hooks. Many sub-commands use "internal API" to
communicate with Gitea web server.
Before, Gitea server always use `StatusCode + Json "err" field` to
return messages.
* The CLI sub-commands: they expect to show all error related messages
to site admin
* The Serv/Hook sub-commands (for git clients): they could only show
safe messages to end users, the error log could only be recorded by
"SSHLog" to Gitea web server.
In the old design, it assumes that:
* If the StatusCode is 500 (in some functions), then the "err" field is
error log, shouldn't be exposed to git client.
* If the StatusCode is 40x, then the "err" field could be exposed. And
some functions always read the "err" no matter what the StatusCode is.
The old code is not strict, and it's difficult to distinguish the
messages clearly and then output them correctly.
# This PR
To help to remove duplicate code and make everything clear, this PR
introduces `ResponseExtra` and `requestJSONResp`.
* `ResponseExtra` is a struct which contains "extra" information of a
internal API response, including StatusCode, UserMsg, Error
* `requestJSONResp` is a generic function which can be used for all
cases to help to simplify the calls.
* Remove all `map["err"]`, always use `private.Response{Err}` to
construct error messages.
* User messages and error messages are separated clearly, the `fail` and
`handleCliResponseExtra` will output correct messages.
* Replace all `Internal Server Error` messages with meaningful (still
safe) messages.
This PR saves more than 300 lines, while makes the git client messages
more clear.
Many gitea-serv/git-hook related essential functions are covered by
tests.
---------
Co-authored-by: delvh <dev.lh@web.de>
2023-03-29 01:32:26 -05:00
|
|
|
return handleCliResponseExtra(extra)
|
2020-12-26 22:34:19 -05:00
|
|
|
}
|