forgejo-federation/docs/content/doc/installation/upgrade-from-gogs.zh-cn.md
John Olheiser bb25f85ce8
Refactor docs (#23752)
This was intended to be a small followup for
https://github.com/go-gitea/gitea/pull/23712, but...here we are.

1. Our docs currently use `slug` as the entire URL, which makes
refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712).
Instead, this PR attempts to make future refactoring easier by using
slugs as an extension of the section. (Hugo terminology)
- What the above boils down to is this PR attempts to use directory
organization as URL management. e.g. `usage/comparison.en-us.md` ->
`en-us/usage/comparison/`, `usage/packages/overview.en-us.md` ->
`en-us/usage/packages/overview/`
- Technically we could even remove `slug`, as Hugo defaults to using
filename, however at least with this PR it means `slug` only needs to be
the name for the **current file** rather than an entire URL
2. This PR adds appropriate aliases (redirects) for pages, so anything
on the internet that links to our docs should hopefully not break.
3. A minor nit I've had for a while, renaming `seek-help` to `support`.
It's a minor thing, but `seek-help` has a strange connotation to it.
4. The commits are split such that you can review the first which is the
"actual" change, and the second is added redirects so that the first
doesn't break links elsewhere.

---------

Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-04-28 11:33:41 +08:00

1.1 KiB
Raw Blame History

date title slug weight toc draft aliases menu
2016-12-01T16:00:00+02:00 从 Gogs 升级 upgrade-from-gogs 101 false false
/zh-cn/upgrade-from-gogs
sidebar
parent name weight identifier
installation 从 Gogs 升级 101 upgrade-from-gogs

从 Gogs 升级

如果你正在运行Gogs 0.9.146以下版本你可以平滑的升级到Gitea。该升级需要如下的步骤

  • 停止 Gogs 的运行
  • 拷贝 Gogs 的配置文件 custom/conf/app.ini 到 Gitea 的相应位置。
  • 拷贝 Gitea 的 options/ 到 Home 目录下。
  • 如果你还有更多的自定义内容比如templates和localization文件你需要手工合并你的修改到 Gitea 的 Options 下对应目录。
  • 拷贝 Gogs 的数据目录 data/ 到 Gitea 相应位置。这个目录包含附件和头像文件。
  • 运行 Gitea
  • 登录 Gitea 并进入 管理面板, 运行 重新生成 '.ssh/authorized_keys' 文件(警告:不是 Gitea 的密钥也会被删除)重新生成所有仓库的 Update 钩子(用于自定义配置文件被修改)