
* add rules * join date on profiles * deprecate follow scope * deprecate identity proofs * familiar followers * use definition lists instead of tables for defining activitypub properties * reformat notifications page into markdown * fix broken links to publicKey header * Application website is now nullable * update environment variables added and removed * fix typo * fix heading level * min_id and max_id can be used at the same time (3.3) * fix typo * new tootctl options * reformat tootctl page to use definition lists for params * add rules and configuration to Instance * fix typo * refactor instance api page * 3.3.0 duration on mutes * 3.3.0 mute_expires_at * improve section headings * 3.4.0 resend email confirmation api * 3.4.0 policy on push subscriptions * 3.4.0 add details to account registration error * refactor accounts api page and start adding relrefs to entity pages * 3.4.0 accounts/lookup api * add see also to accounts methods * add more see-also links * 3.5.0 appeal mod decisions * 3.5.0 reformat reports and add category/rule_ids params * document report entity and missing responses * fix typos * fix relrefs and url schema, add aliases to old urls * add archetypes for new methods/entities * update archetypes with see-also stubs * clearer presentation of rate limits * announcements api methods * refactor apps methods * refactor bookmarks methods + some anchors * refactor conversations methods * custom_emojis methods refactor * anchors * refactor directory methods * refactor domain_blocks methods * add see also to emails methods * fix page relref shortcodes to specific methods + refactor endorsements methods * min_id max_id * refactor favourites methods * refactor featured_tags methods * refactor filters methods, make path params consistent, i18n required shortcode * follow_requests methods * lists methods * markers methods * forgot to add entity links * media methods, also fix formatting of some json errors * mutes methods, add more see-also links * oembed methods * preferences methods * proofs methods * push methods * suggestions methods * 3.5.0 add new trend types, fix formatting * refactor streaming methods * refactor oauth methods * note that streaming api casts payload to string * refactor search methods * refactor polls methods * remove unnecessary link * reformat scheduled_statuses methods * reformat timelines methods * reformat statuses methods * 3.5.0 editing statuses * consistent use of array brackets in form data parameters * update dev setup guide, add vagrant and clean up text * add admin/accounts methods * 3.6 role entity * admin/accounts methods v2 * minor fix * stub admin/reports methods * document admin reports * add 403 example to methods archetype * cleanup entities for admin reports and add new attrs * 3.6.0 domain allows methods + normalize admin entity namespace * fix search-and-replace error * add aliases for admin entities * 3.6.0 canonical email blocks entity * 3.5.0 admin/retention api * 3.5.0 add admin::ip doc * 3.5.0 admin/reports * 3.6.0 admin/domain_allows * 3.5.0 admin/dimensions * 3.6.0 permissions and roles * minor formatting fix * add anchor link to headings * checkpoint * add update commands to dev env setup guide * change mentions of v3.6 to v4.0 * tootctl now uses custom roles * fix formatting * v2 instance api * update frontmatter, add better titles to pages * minor wording change * consistency * add more aliases * add placeholders and WIP notices * explain link pagination and stub out todos * switch baseURL to https * 422 on reports with rules but category!=violation * document bug fixes * fix typo * remove duplicate API method definition * s/tootsuite/mastodon for github links * remove unnecessary escaping * s/tootsuite/mastodon in Entity archetype * add missing nullable shortcode * clarify oauth scope when requesting a user token * api/v2/media now synchronous for images * DISALLOW_UNAUTHENTICATED_API_ACCESS * add undocumented env variables * add instance domain blocks and extended description api * add SMTP_ENABLE_STARTTLS * add description to SMTP_ENABLE_STARTTLS * take suggestions from open PRs * normalize links and flavour language * Fully document streaming API based on source code * Add mention of MIME types * bump to ruby 3.0.4 * clarify how to check on async media processing * validation of replies_policy * remove TODOs on admin account action * EmailDomainBlocks * IpBlocks * Admin::DomainBlock * remove TODOs * following hashtags * followed_tags * remove reference to unused parameter * add new oauth scopes for admin blocks and allows * fix command signature for i18n-tasks normalize * reformat code structure page * document fixes for following tags (assume 4.0.3) * Add warning about pre-4.0 hardcoded roles * add note about case sensitivity * remove use of 'simply' from docs * remove reference to silencing * add reference to IDN normalization for verified links * add lang parameter
4.4 KiB
title | description | menu | ||||||
---|---|---|---|---|---|---|---|---|
迁移到新机器 | 在不损失任何东西的情况下,把你的Mastodon复制安装至新的服务器上。 |
|
有时,出于各种原因,你需要将你的Mastodon实例从一台服务器迁移至另一台。幸运的是,这个过程并不太困解,虽然这可能导致一段时间的下线。
{{< hint style="info" >}} 本篇指南基于Ubuntu Server编写;根据其他设置的不同,你的过程可能会有变化。 {{< /hint >}}
基本步骤
- 依照[产品指南]({{< relref "install" >}})安装新的Mastodon服务器(切记,不要运行
mastodon:setup
)。 - 停止旧服务器上的Mastodon(
systemctl stop 'mastodon-*.service'
)。 - 依照如下指示,导出并导入Postgres数据库。
- 依照如下指示,复制
system/
目录下文件。(注意:如果你使用S3存储,你可以跳过此步)。 - 复制
.env.production
文件。 - 运行
RAILS_ENV=production bundle exec rails assets:precompile
编译 Mastodon。 - 运行
RAILS_ENV=production ./bin/tootctl feeds build
重新构建每个用户的主页时间流。 - 启动新服务器上的Mastodon。
- 更新DNS设置,将其指向新服务器。
- 更新或复制你的Nginx设置,如果必要的话可重获取LetsEncrypt证书。
- 享受你的新服务器!
详细步骤
什么数据需要被迁移
你必须需要复制如下内容:
~/live/public/system
目录,里面包含了用户上传的图片与视频(如果使用S3,可跳过此步)- Postgres数据库(使用pg_dump)
~/live/.env.production
文件,里面包含了服务器配置与密钥
不太重要的部分,为了方便起见,你也可以复制如下内容:
- nginx配置文件(位于
/etc/nginx/sites-available/default
) - systemd配置文件(
/etc/systemd/system/mastodon-*.service
),里面可能包括一些你服务器的调优与个性化 - pgbouncer配置文件,位于
/etc/pgbouncer
(如果你使用pgbouncer的话)
导出并导入Postgres数据库
不要运行mastodon:setup
,而是创建一个名为template0
的空白Postgres数据库(当导入Postgres导出文件时,这是很有用的,参见pg_dump文档)。
在你的旧系统,使用mastodon
用户运行如下命令:
pg_dump -Fc mastodon_production -f backup.dump
使用 rsync
或 scp
复制 backup.dump
文件。然后在新系统,使用mastodon
帐户创建一个空数据库:
createdb -T template0 mastodon_production
然后导入它:
pg_restore -U mastodon -n public --no-owner --role=mastodon \
-d mastodon_production backup.dump
(注意:如果新服务器上的帐户名不是mastodon
,你应当修改上面命令中 -U
和 --role
参数。两台服务器的用户名不同也可以。)
复制文件
本操作可能花费一些时间,若你希望避免不必要重复制,建议使用rsync
。在你的旧机器上,使用mastodon
用户,运行:
rsync -avz ~/live/public/system/ mastodon@example.com:~/live/public/system/
如果旧服务器上任何文件有改动,你需要重运行此命令。
你同样需要复制.env.production
文件,该文件内含密钥。
可选的,你可以复制nginx、systemd、pgbouncer配置文件,或者从头开始重写它们。
迁移期间
你可以编辑旧机器上的~/live/public/500.html
页面,如果你希望展示一个优雅的错误信息,让现有用户知晓正在进行迁移。
你也应该提前一天将DNS TTL设置为较小数值(30-60分钟)。这样当你把DNS指向新IP后,新纪录可以很快扩散开来。
迁移后
你可以使用whatsmydns.net来查看DNS扩散的过程。为了跳过这个过程,你可以修改你自己的/etc/hosts
文件,将其指向你的新服务器,这样你可以尽早开始使用新服务器。
{{< translation-status-zh-cn raw_title="Migrating to a new machine" raw_link="/admin/migrating/" last_tranlation_time="2020-05-06" raw_commit="ad1ef20f171c9f61439f32168987b0b4f9abd74b">}}