Gitea v1.21.1 中文文档--fix 选项进行自动修复。 额外的日志可以通过 --log-file=... 进行设置。 有时,在迁移时,旧的列和默认值可能会在数据库模式中保持不变。这可能会导致警告,如下所示: 1. 2020/08/02 11:32:29 ...rm/session_schema.go:360:Sync() [W] Table user Column keep_activity_private db default 当用户的身份验证失败时,日志中会记录此类信息: 1. 2018/04/26 18:15:54 [I] Failed authentication attempt for user from xxx.xxx.xxx.xxx 1. 2020/10/15 16:08:44 [E] invalid credentials from xxx.xxx.xxx.xxx 添加日志过滤器规则到配置文件 /etc/fail2ban/filter 如果您报告了错误或问题,必须提供这些信息以恢复初始日志记录。 只有在完全配置了所有内容之后,您才应该设置此选项。 有时,在迁移过程中,旧列和默认值可能在数据库架构中保持不变。 这可能会导致警告,例如: 1. 2020/08/02 11:32:29 ...rm/session_schema.go:360:Sync() [W] Table user Column keep_activity_private db default0 码力 | 303 页 | 3.88 MB | 1 年前3
Pro Git 2nd Edition 2.1.413and references in detail. GitHub changed the default branch name from master to main in mid-2020, and other Git hosts followed suit. So you may find that the default branch name in some newly created0 码力 | 731 页 | 21.49 MB | 1 年前3
Pro Git 2nd Edition 2.1.413branches and references in detail. GitHub changed the default branch name from master to main in mid-2020, and other Git hosts followed suit. So you may find that the default branch name in some newly created0 码力 | 501 页 | 17.96 MB | 1 年前3
Pro Git 2nd Edition 2.1.413 and references in detail. GitHub changed the default branch name from master to main in mid-2020, and other Git hosts followed suit. So you may find that the default branch name in some newly created0 码力 | 691 页 | 13.35 MB | 1 年前3
共 4 条
- 1













