forked from forgejo/forgejo
[BRANDING] Use forgejo
binary name
- Use `forgejo` binary name for migration suggestions. - Resolves https://codeberg.org/forgejo/forgejo/issues/869#issuecomment-944501 (cherry picked from commit418a0bed8f
) (cherry picked from commit734579ce9b
) (cherry picked from commit8b7cf605f2
) (cherry picked from commitc59e1a4e61
)
This commit is contained in:
parent
ee2cfd1cd0
commit
e3877892e1
2 changed files with 2 additions and 2 deletions
|
@ -540,7 +540,7 @@ func EnsureUpToDate(x *xorm.Engine) error {
|
|||
expected := ExpectedVersion()
|
||||
|
||||
if currentDB != expected {
|
||||
return fmt.Errorf(`Current database version %d is not equal to the expected version %d. Please run "gitea [--config /path/to/app.ini] migrate" to update the database version`, currentDB, expected)
|
||||
return fmt.Errorf(`Current database version %d is not equal to the expected version %d. Please run "forgejo [--config /path/to/app.ini] migrate" to update the database version`, currentDB, expected)
|
||||
}
|
||||
|
||||
return nil
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue