
In [Ghost on Fly.io for Free](/blog/ghost-on-fly-io-for-free/), we mentioned that the root environment of fly.io is temporary and will be restored when the app is redeployed or restarted, which was [confirmed](https://community.fly.io/t/will-restarting-the-app-reset-the-environment-configured-in-ssh-console/11167/2?u=pathsis) by the fly.io forum. This article shows how to wrap the Git environment into Docker to avoid the problem of Git environments being destroyed.

In fact, there are many ways to backup Ghost, besides the one we have described in the past using SFTP, there are [some](https://chlee.co/how-to-automatically-backup-a-self-hosted-ghost-blog-and-upload-to-aws-s3/) others , but these methods are really slow in transferring and backing up the full amount each time, compared to using Git, which is more elegant because it uses incremental backups and is extremely fast at copying! It's a little tedious to set up a Git environment, but it's a one-off.

## 1. Prepare the deployment files

We need to deploy a local Dockerfile instead of letting fly.io pull the official image automatically.

1.Go to Github and download the [official image](https://github.com/docker-library/ghost/tree/533294af2135d3b4e64e3620e66a4f4e314e0a44/5/debian). Download both of two files:

- docker-entrypoint.sh
- Dockerfile

  2.Open a terminal and run

```shell
mkdir blog
```

3.Copy the above two files to the `blog` folder, which is located under `/Users/<ComputerUserName>/blog`, your user folder.

4.Run

```shell
ssh-keygen -t rsa -C "<GithubEmail>"
```

Press enter continuously. Follow the prompts to see where the key is saved. Here is my example.

```shell
 ssh-keygen -t rsa -C "<GithubEmail>"
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/<ComputerUserName>/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /Users/<ComputerUserName>/.ssh/id_rsa
Your public key has been saved in /Users/<ComputerUserName>/.ssh/id_rsa.pub
The key fingerprint is:
SHA256:siVmLMku/3BAem2ruRt44dEgdQsUBrKSAztU6HT1FIs k<GithubEmail>
The key's randomart image is:
+---[RSA 3072]----+
|o.++Bo.o.        |
|oB + o+..        |
|X o oE.o         |
|.+ = *           |
|  . O X S        |
|   = O *         |
|  o * +          |
|   + *           |
|    *+.          |
+----[SHA256]-----+
```

Go to the file `/Users/<ComputerUserName>/.ssh/` and copy the id_rsa and id_rsa.pub files to the blog folder.

Open id_rsa.pub with a text editor and add its contents to Github's SSH keys.

5.Continue to run

```shell
nano auto_backup.sh
```

Then, put the following code

```shell
#! /bin/sh

cd /var/lib/ghost/content # Switch to the directory
git config --global init.defaultBranch master
git config --global --add safe.directory /var/lib/ghost/content
git config --global pull.rebase false
git pull # Pull the repository
git add . # Add all
git commit -m "auto backup" # Commit
git push --force # Force a commit
```

Add to it. Press `CTRL`+`O` to save; press `CTRL`+`X` to exit the nano editor.

6.Open the Dockerfile and edit a few places. I recommend opening the blog folder with vs code.

Find `COPY docker-entrypoint.sh /usr/local/bin`, then, above it, paste the following code.

```shell
COPY id_rsa /root/.ssh/
COPY id_rsa.pub /root/.ssh/
COPY auto_backup.sh /usr/local/bin/auto_backup.sh
```

Find `ENV GHOST_VERSION`, then add the following code to the next line.

```shell
RUN apt-get update -y && apt-get upgrade -y && apt-get install -y  git nano
```

7.Refer to [previous post](https://pathos.page/blog/ghost-on-fly-io-for-free-en#2-install-ghost:~:text=This%20will%20create%20a%20fly.toml%20file%20in%20the%20blog%20directory.%20Open%20it%20with%20a%20text%20editor%20and%20overwrite%20it%20with%20the%20following%20code.) to prepare the fly.toml file. Note to remove

```toml
[build]
  image = "ghost:5"
```

8.This way, several local files that we use for deployment are ready, they are

- auto_backup.sh
- docker-entrypoint.sh
- Dockerfile
- fly.toml
- id_rsa
- id_rsa.pub

## 2. Deployment

Login:

```shell
flyctl auth login --email=<FlyMail> --password=<FlyPassword> --otp=<any letter>
```

Launch an app:

```shell
flyctl launch --image=Decokerfile --name=<AppName> -r hkg --no-deploy
```

Follow the prompts and press y to continue.

Create a volume:

```shell
flyctl volumes create data -r hkg --no-encryption --size 1
```

Deploy.

```shell
flyctl deploy
```

**NOTE**: If you have installed Ghost in the standard way, you should simply deploy.

## 3.Initialize Ghost

Refer to [previous post](https://pathos.page/blog/ghost-on-fly-io-for-free-en#3-initialize-ghost:~:text=show%20successful.-,3.%20Initialize%20Ghost,-Visit).

## 4. Backup

1.Verify the github connection

```shell
ssh git@github.com
```

Get the `successfully` prompt, that's it.

2.Initialize Git, run

```shell
cd /var/lib/ghost/content
git init
git config --global user.name "<GithubUsername>"
git config --global user.email <GithubMail>
git config --global --add safe.directory /var/lib/ghost/content
git remote add origin git@github.com:<GithubUsername>/<YourRepo>.git
git add .
git commit -m "auto backup"
git push -u origin master --force
```

Check for changes to the contents of the Github repository.

If there is an error, then run

```shell
cd /var/lib/ghost/
rm -rf content
```

It will prompt its BUSY, don't worry about it, it's already cleared.

After that, try to initialize Git again.

## 5.Restore

Assuming you have a fresh install of Ghost, you need to restore an existing backup in Github.

Unlike a backup, we need to pull rather than push the contents from Github.

```shell
rm -rf /var/lib/ghost/content
cd /var/lib/ghost/content
git init
git config --global user.name "<GithubUsername>"
git config --global user.email <GithubMail>
git config --global --add safe.directory /var/lib/ghost/content
git pull --force git@github.com:<GithubUsername>/<YourRepo>.git
```

If the repository is brand new, i.e. you copied your files directly into it but haven't connected to the remote repository yet, you may be prompted to run

```shell
git push --set-upstream origin master
```

Just execute the action.

## 6.Daily back up

First, give the automatic backup script execution privileges to, **in ssh console** run

```shell
chmod a+x /usr/local/bin/auto_backup.sh
```

Then, **in local machine**, run the following command

```shell
flyctl auth login --email=<FlyMail> --password=<FlyPassword> --otp=<any letter>
flyctl ssh console
sh /usr/local/bin/auto_backup.sh
```

You can write a script to automatically log into console and run it from **local machine** terminal

```shell
nano fly.sh
```

Paste the following code into it

```shell
cd blog
flyctl auth login --email=<FlyMail> --password=<FlyPassword> --otp=<any letter>
flyctl ssh console
```

Save and exit, then run

```shell
chmod a+x fly.sh
```

Put it into an aspect, like the desktop. To use it, drag it to the terminal, press enter, and it will go directly to the console.


This article shows how to package the Git environment into Docker to avoid the problem of Git environments being destroyed, to use Github backup Ghost.

Package Git into Ghost Docker Image


在《[在 fly.io 免费运行 Ghost 博客](/blog/ghost-on-fly-io-for-free/)》中，我们提到，fly.io 的 root 环境是临时的，会在重新部署或重启 app 时复原，这得到了 fly.io 论坛的[确认](https://community.fly.io/t/will-restarting-the-app-reset-the-environment-configured-in-ssh-console/11167/2?u=pathsis)。这篇文章介绍如何将 Git 环境封装到 Docker 中，以避免 Git 环境被销毁的问题。

实际上，备份 Ghost 的方法有很多，除了我们过去介绍的使用 SFTP 的方法，还有其他[一些](https://chlee.co/how-to-automatically-backup-a-self-hosted-ghost-blog-and-upload-to-aws-s3/)，但这些方法传输速度实在太慢，而且每次都是全量备份，相比而言，使用 Git 更为优雅，因为它采用增量备份，而且复制速度极快！虽然搭建 Git 环境稍微繁琐，但一劳永逸。

## 1.准备部署文件

我们需要部署本地的 Dockerfile，而不是让 fly.io 自动拉取官方映像。

1.到 Github 下载[官方映像](https://github.com/docker-library/ghost/tree/533294af2135d3b4e64e3620e66a4f4e314e0a44/5/debian)。将这两个文件都下载。

2.打开终端，运行

```shell
mkdir blog
```

3.将上面两个文件复制到 blog 文件夹。blog 文件夹位于`/Users/<ComputerUserName>/blog`，也就是你的用户文件夹下。

4.运行

```shell
ssh-keygen -t rsa -C "<GithubEmail>"
```

连续回车。根据提示，查看密钥保存位置。以下是我的示例。

```shell
 ssh-keygen -t rsa -C "<GithubEmail>"
Generating public/private rsa key pair.
Enter file in which to save the key (/Users/<ComputerUserName>/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /Users/<ComputerUserName>/.ssh/id_rsa
Your public key has been saved in /Users/<ComputerUserName>/.ssh/id_rsa.pub
The key fingerprint is:
SHA256:siVmLMku/3BAem2ruRt44dEgdQsUBrKSAztU6HT1FIs k<GithubEmail>
The key's randomart image is:
+---[RSA 3072]----+
|o.++Bo.o.        |
|oB + o+..        |
|X o oE.o         |
|.+ = *           |
|  . O X S        |
|   = O *         |
|  o * +          |
|   + *           |
|    *+.          |
+----[SHA256]-----+
```

到 `/Users/<ComputerUserName>/.ssh/` 这个文件中，将 id_rsa 和 id_rsa.pub 文件复制到 blog 文件夹。

用文本编辑器打开 id_rsa.pub，将其内容添加到 Github 的 SSH keys 中。

5.继续运行

```shell
nano auto_backup.sh
```

然后，将如下代码

```shell
#!/bin/sh

cd /var/lib/ghost/content/
git config --global init.defaultBranch master
git config --global --add safe.directory /var/lib/ghost/content
git config --global pull.rebase false
git pull
git add .
git commit -m "auto backup"
git push -u origin master --force
```

添于其中。按`CTRL`+`O`键，以保存；按`CTRL`+`X`键以退出 nano 编辑器。

6.打开 Dockerfile，编辑几个地方。我建议用 vs code 打开 blog 文件夹。

找到`COPY docker-entrypoint.sh /usr/local/bin`,然后，在其上方贴上如下代码：

```shell
COPY id_rsa /root/.ssh/
COPY id_rsa.pub /root/.ssh/
COPY auto_backup.sh /usr/local/bin/auto_backup.sh
```

找到`ENV GHOST_VERSION`,然后在其下一行添加如下代码：

```shell
RUN apt-get update -y && apt-get upgrade -y && apt-get install -y  git nano
```

7.参考[上一篇文章](https://rercel.com/blog/ghost-on-fly-io-for-free#2%E5%AE%89%E8%A3%85-ghost:~:text=ps1%20%2Duseb%20%7C%20iex-,2.%E5%AE%89%E8%A3%85%20Ghost,-%E4%B8%8B%E9%9D%A2%E7%9A%84%E5%91%BD%E4%BB%A4)准备好 fly.toml 文件。请删除

```toml
[build]
  image = "ghost:5"
```

8.这样，我们用于部署的几个本地文件都已准备好了，它们是：

- auto_backup.sh
- docker-entrypoint.sh
- Dockerfile
- fly.toml
- id_rsa
- id_rsa.pub

## 2.部署

登录

```shell
flyctl auth login --email=<FlyMail> --password=<FlyPassword> --otp=<任意字母>
```

发起一个 App:

```shell
flyctl launch --image=Decokerfile --name=<AppName> -r hkg --no-deploy
```

按照提示，按 y，以继续。

创建一个卷:

```shell
flyctl volumes create data  -r hkg --no-encryption --size 1
```

部署：

```shell
flyctl deploy
```

**注意**：若你已以标准方法安装了 Ghost，则你应该直接部署。

## 3.初始化 Ghost

参考[上篇文章](https://pathos.page/blog/ghost-on-fly-io-for-free#3-%E5%88%9D%E5%A7%8B%E5%8C%96-ghost:~:text=%E6%98%BE%E7%A4%BAsuccessful.-,3.%20%E5%88%9D%E5%A7%8B%E5%8C%96%20Ghost,-%E8%AE%BF%E9%97%AE)。

## 4.备份

1.验证 Github 链接

```shell
ssh git@github.com
```

得到 `successfully` 的提示，即可。

2.初始化 Git，运行

```shell
cd /var/lib/ghost/content
git init
git config --global user.name "<GithubUsername>"
git config --global user.email <GithubMail>
git config --global --add safe.directory /var/lib/ghost/content
git remote add origin git@github.com:<GithubUsername>/<YourRepo>.git
git add .
git commit -m "auto backup"
git push -u origin master --force
```

检查 Github 的仓库的内容变化。

若出现错误，则运行

```shell
cd /var/lib/ghost/
rm -rf content
```

会提示其 busy，不用管它，已经清空。

之后，再次尝试初始化 Git。

## 5.还原

假设你全新安装了 Ghost，需要还原 Github 中已有的备份。

与备份不同的是，我们需要从 Github 中 pull 而不是 push 内容。

```shell
rm -rf /var/lib/ghost/content
cd /var/lib/ghost/content
git init
git config --global user.name "<GithubUsername>"
git config --global user.email <GithubMail>
git config --global --add safe.directory /var/lib/ghost/content
git pull --force git@github.com:<GithubUsername>/<YourRepo>.git
```

假如这个仓库是一个全新的仓库，也就是说，你把你的文件直接复制到其中，但还没有和远程仓库连接过，那么系统可能会提示你运行

```shell
git push --set-upstream origin master
```

执行操作即可。

## 6.日常备份

首先，赋予自动备份脚本执行权限，**在 ssh console 中**，运行一次

```shell
chmod a+x /usr/local/bin/auto_backup.sh
```

以后，**在本地机器上**，运行如下命令

```shell
flyctl auth login --email=<FlyMail> --password=<FlyPassword> --otp=<任意字母>
flyctl ssh console
sh  /usr/local/bin/auto_backup.sh
```

以日常备份。

可以编写一个自动登录 console 的脚本，在**本机**终端运行

```shell
nano fly.sh
```

将如下代码粘贴进去

```shell
cd blog
spawn flyctl auth login --email=<FlyMail> --password=<FlyPassword> --otp=<任意字母>
flyctl ssh console
```

保存并退出，然后运行

```shell
chmod a+x fly.sh
```

将其放到一个方面的地方，比如桌面。使用时，将其拖到终端，按回车，会直接进入 console。


这篇文章介绍如何将Git环境封装到Docker中，以避免Git环境被销毁的问题，以更好地用Github备份Ghost博客。

将 Git封 装到 Ghost 的 Docker 中


This article introduce how to install, backup and restore ghost on [fly.io](https://fly.io/) for free. Backing up and restoring data is a reference for use cases on other servers. With the use of cron, the full site data is regularly backed up to github, so to speak, you can really feel at ease with ghost and give up static blogs.

## 1. Pre-requisites

1. To register for a fly.io account,install flyctl command line, you need a credit card. (**required**)
2. be familiar with basic git commands. (not required)
3. Understand fly.io's [pricing](https://fly.io/docs/about/pricing/). (not required)
4. Understand Mailgun. (not required)

Install the command line

```shell
curl -L https://fly.io/install.sh | sh
```

For Windows，run

```shell
iwr https://fly.io/install.ps1 -useb | iex
```

## 2. Install Ghost

The following command is common on Linux and Mac.

Open a terminal and execute.

```shell
mkdir blog #Create a directory
cd blog #Enter this directory
flyctl auth login #Log in, then the browser will pop up the login session
flyctl launch --image=ghost:5 -r hkg --name=<AppName> --no-deploy
```

An explanation of the last command:

- The docker image used is `ghost:5`, indicating that the 5.x major version will be updated automatically on every deployment, and if you intend to check a specific version, such as 5.36.0, then replace 5 with it. [The official image is here](https://hub.docker.com/_/ghost).

- `- r hkg` means that the node of the selected server is Hong Kong (the node closest to us). [The region code of fly.io is here](https://fly.io/docs/reference/regions/#fly-io-regions).

- `--name=<AppName> ` means the name of the created app, replace `<AppName> ` with your own, and note that the default URL generated in the future is `<AppName>.fly.dev`, so please take a unique name.

- `--no-deploy` means don't deploy for now.

This will create a fly.toml file in the blog directory. Open it with a text editor and overwrite it with the following code.

```toml
app = "<AppName>"
kill_signal = "SIGINT"
kill_timeout = 5
processes = []

[build]
  image = "ghost:5"

[env]
  url = "https://<AppName>.fly.dev"
  database__client = "sqlite3"
  database__connection__filename = "content/data/ghost.db"
  database__debug = "false"
  database__useNullAsDefault = "true"
  mail__from = "noreply@example.com"
  mail__options__auth__pass = "<YourMailgunPassword>"
  mail__options__auth__user = "postmaster@example.com"
  mail__options__host = "smtp.mailgun.org"
  mail__options__port = "465"
  mail__transport = "SMTP"

[experimental]
  auto_rollback = true

[mounts]
  destination = "/var/lib/ghost/content"
  source = "data"

[[services]]
  http_checks = []
  internal_port = 2368
  processes = ["app"]
  protocol = "tcp"
  script_checks = []
  [services.concurrency]
    hard_limit = 25
    soft_limit = 20
    type = "connections"

  [[services.ports]]
    force_https = true
    handlers = ["http"]
    port = 80

  [[services.ports]]
    handlers = ["tls", "http"]
    port = 443

    [services.ports.http_options.response.headers]
      Referrer-Policy = "strict-origin"
      Strict-Transport-Security = "max-age=63072000; includeSubDomains; preload"
      X-Content-Type-Options = "nosniff"
      X-Frame-Options = "SAMEORIGIN"
      x-xss-protection = "1; mode=block"
      Permissions-Policy = "camera=(), microphone=(), geolocation=(), browsing-topics=()"

  [[services.tcp_checks]]
    grace_period = "1s"
    interval = "15s"
    restart_limit = 0
    timeout = "2s"
```

Please replace `<AppName>` with your own, and, if you don't use [Mailgun](https://ghost.org/docs/faq/mailgun-newsletters/), please remove all code starting with `mail__` below `[env]`.

The `[services.ports.http_options.response.headers]` section is **optional** and is used to set the http header. You can search item by item, `Strict-Transport-Security`, for example, to determine if you want to add them. After the deployment, you may go to the http header test [site](https://securityheaders.com/).

When you are done checking, save and close the fly.toml file. Then go back to the terminal and continue executing.

```shell
  flyctl volumes create data -r hkg --no-encryption --size 1 # Create a volume of size 1Gb with region hkg and no encryption (helps improve performance). The free amount is 3GB in total.
  flyctl deploy #deploy
```

Wait a few moments, the deployment is successful! It will show `successful`.

## 3. Initialize Ghost

Visit

```shell
https://<AppName>.fly.dev/ghost/
```

to initialize ghost. After this, you are free to use ghost to publish content. Binding domain names, backing up and restoring data are optional operations.

## 4. Bind the domain name

Run

```shell
  flyctl ips list
```

to see the IP address of your app. Then create A records for ipv4 and AAAA records for ipv6 on your DNS server, pointing to your domain name `example.com` (required). Create CNAME, `<AppName>.fly.dev`, pointing to your `www.example.com` (not required). Also known as

| type  | record | value               |
| ----- | ------ | ------------------- |
| A     | @      | ipv4 address        |
| AAAAA | @      | ipv6 address        |
| CNAME | www    | `<AppName>.fly.dev` |

**Note**: **Before** binding the domain name, make sure to create the DNS records correctly.

Then run

```shell
flyctl certs create example.com
flyctl certs create www.example.com
```

wait a moment and run

```shell
flyctl certs check example.com
flyctl certs check www.example.com
```

to check the certificate enactment, which usually takes about a minute or two as long as the DNS **advance** configuration is correct. Run

```shell
flyctl ips list
```

to check the certificate issuance status.

**Note**: Don't install certificates repeatedly because there is a limit, [only 5 certificates can be issued every 7 days](https://community.fly.io/t/awaiting-certification-11-hours/7635/8?u=pathsis). It is recommended to bind them after debugging the app.

## 5. Redeploy

Notice that in the fly.toml,

```toml
[env]
  url = "https://<AppName>.fly.dev"
```

is the address assigned by fly.io, and if you click on the home page title of the ghost site, it will redirect to this address, so when you bind your own domain, change it to

```toml
[env]
  url = "https://example.com"
```

Save and close, then run `flyctl deploy`.

## 6. Back up and restore

Every time in the future you need to go into your local configuration directory to use flyctl correctly.

### 6.1 Method 1: Use SFTP to bacup Ghost

The advantage is that no complicated configuration is needed, but the copy speed is slow.

#### 6.1.1 Back up

First login (assuming you need to back up later).

```shell
cd blog
flyctl auth login
```

Then run

```shell
flyctl ssh sftp shell -r -a <AppName>
```

When it succeeds, it will show `>>` (red), then run

```shell
get /var/lib/ghost/content/
```

This will backup the whole site data, including themes, images, videos, articles, etc. It's very slow, please be patient.

You can also backup only images and videos by running

```shell
get /var/lib/ghost/content/images/
get /var/lib/ghost/content/media/
```

This will generate a `content.zip`, or, `images.zip` and `media.zip` in the blog directory. back them up elsewhere, or name them `content-YYYY-MM-DD.zip`.

#### 6.1.2 Restore

Now suppose you reinstall a new ghost, assuming it is still on fly.io, then the installation directory will remain as `/var/lib/ghost/content/`. If you install ghost somewhere else in the future, like on AWS, make sure you create this directory instead of the usual tutorial `/var/www/ghost/content/`, otherwise you will have trouble recovering your data by **first** method.

Still run

```shell
cd blog
flyctl auth login
flyctl ssh sftp shell -r -a <AppName>
```

Then run

```shell
put content.zip /var/lib/ghost/content.zip
```

After success, create a new tab in the terminal and run

```shell
flyctl ssh console
```

again, in ssh, run

```shell
apt-get update && apt-get upgrade && apt-get install unzip
```

to install `unzip`. Then run

```shell
cd /var/lib/ghost/
unzip content.zip
```

It will overwrite the content folder directly.

To verify that the unzip was successful, run

```shell
cd /var/lib/ghost/content/images/
ls #List all the files in the current folder
```

to see if there is any new data.

To fix permissions, run

```shell
chown -R node:node /var/lib/ghost/content/
```

**Note**: Possible scenario, can't overwrite the content folder correctly, then try to backup only `/var/lib/ghost/content/images/` and `/var/lib/ghost/content/media/` instead. At this point run

```shell
put images.zip /var/lib/ghost/content/images.zip
put media.zip /var/lib/ghost/content/media.zip

rm -rf /var/lib/ghost/content/images/
rm -rf var/lib/ghost/content/media/

unzip /var/lib/ghost/content/images.zip
unzip /var/lib/ghost/content/media.zip
```

this may break the permissions of the content folder, so run

```shell
ls -l /var/lib/ghost/content/
```

to check the user and permissions of the images and media folders, if their permissions belong to root, then you can't upload images and videos anymore, then run

```shell
chown -R node:node /var/lib/ghost/content/
chown -R node:node /var/lib/ghost/content/images/
chown -R node:node /var/lib/ghost/content/media/
```

to fix it, note that `node` is the ghost user in the fly.io case, depending on the result of the `ls -l /var/lib/ghost/content/` command,, in any case make sure that the user of the images and media folders is the same as the user of the other files under `/content/`.

### 6.2 Method 2: Use Github to backup Ghost

The advantage is that it is fast to replicate data, but the disadvantage is that the installation and configuration is relatively complicated.

#### 6.2.1 Back up

1. Login and enter ssh

```shell
cd blog
flyctl auth login
flyctl ssh console
```

2. Install git

```shell
apt-get update && apt-get upgrade && apt-get install git
```

3. Create a private (recommended) repository on the github web side , assuming it is called `<YourRepository>`.

4. Generate the key

```shell
ssh-keygen -t rsa -C "<GithubEmail>" # Press the Enter key continuously
```

5. Terminal new tab, run

```shell
flyctl ssh sftp shell -r -a <AppName>
get /root/.ssh/id_rsa.pub
```

Go back to the blog folder and find the `id_rsa.pub` file, open it with a text editor, and copy the key from it. Add it to `setting→SSH and GPG keys→SSH keys` in github and save it.

Test the connection with github

```shell
ssh git@github.com
```

Pay attention to the word `successful`.

6. Initialize the content git

```shell
cd /var/lib/ghost/content/
git init
git config --global user.name "<GithubUsername>"
git config --global user.email <GithubEmail>
git config --global --add safe.directory /var/lib/ghost/content
git remote add origin git@github.com:<GithubUsername>/<YourRepository>.git
git add .
git commit -m "auto backup"
git push -u origin master --force
```

Make sure you successfully push to github.

7. Create a new script

```shell
apt-get update && apt-get upgrade && apt-get install nano
cd /var/lib/ghost/content/
nano auto_run.sh
```

Copy the following code into `auto_run.sh`

```shell
#! /bin/sh

cd /var/lib/ghost/content # Switch to the directory
git config --global init.defaultBranch master
git config --global --add safe.directory /var/lib/ghost/content
git pull # Pull the repository
git add . # Add a staging
git commit -m "auto backup" # Commit
git push --force
```

Press `ctrl`+`O` followed by `enter` to write; press `ctrl`+`x` to exit nano.

Give the file permission to run

```shell
chmod a+x auto_run.sh
```

Later, after logging into ssh, you can directly run

```shell
sh /var/lib/ghost/content/auto_run.sh
```

to execute a new push.

#### 6.2.2 Restore

1. Log in to shh, reinstall git and add the key without further ado.

2. Empty the content folder

```shell
cd /var/lib/ghost/
rm -rf content
```

It will return that the folder can't be deleted because its `busy`, it doesn't matter, it has been emptied, but not deleted.

3. Initialize the git in the content file and force a pull

```shell
cd /var/lib/ghost/content/
git init
git config --global user.name "<GithubUsername>"
git config --global user.email <GithubEmail>
git pull --force git@github.com:<GithubUsername>/<YourRepository>.git
```

4. Verify that the pull was successful

```shell
ls
```

5. Make sure the data is successfully pulled, then restart the app

```shell
fly apps restart <AppName>
```

As of now, restarting or redeploying will **clear** the installed environment and software, but will **not** delete the ghost data.

6. It is really difficult to run **cron** in docker, so don't try it. In a normal virtual machine, you can set up cron to run at regular intervals

```shell
sh /var/lib/ghost/content/auto_run.sh
```


This article introduce how to run a free ghost blog on fly.io to backup and restore data. Backing up and restoring data is informative for use cases on other servers.

Ghost on Fly.io for Free: Install, Backup and Restore


最近把论文交了后，手又痒痒，折腾了下 ghost。[fly.io](https://fly.io/)是一个 PaaS，现在可以在上面安装若干个 Ghost 博客，而且完全免费。

这篇文章介绍了在 fly.io 上免费安装、备份和还原 Ghost 的方法。备份和恢复数据对其他服务器上的用例具有参考意义。配合使用 cron，定时将全站数据备份到 Github，可以说，真的可以安心用 Ghost，舍弃静态博客了。

## 1.前置条件

1. 注册 fly.io 账号，安装 flyctl 命令行，需要一张支持外币的信用卡。（**必要**）
2. 熟悉基本的 git 命令。（非必要）
3. 了解 fly.io 的[定价](https://fly.io/docs/about/pricing/)。（非必要）
4. 了解 Mailgun。（非必要）

安装命令行

```shell
curl -L https://fly.io/install.sh | sh
```

对于 Windows，运行

```shell
iwr https://fly.io/install.ps1 -useb | iex
```

## 2.安装 Ghost

下面的命令在 Linux 和 Mac 上通用。

打开终端，执行：

```shell
mkdir blog #创建一个目录
cd blog #进入这个目录
flyctl auth login #登录，之后浏览器会弹出登录会话
flyctl launch --image=ghost:5 -r hkg --name=<AppName> --no-deploy
```

对最后一条命令的解释：

- `--image=ghost:5`，表示 5.x 大版本会自动在每一次部署时更新，若打算选中一个具体的版本，比如 5.36.0，则把 5 换成它。[官方镜像在这里](https://hub.docker.com/_/ghost)。

- `- r hkg`表示选择服务器的节点为香港（离我们最近的节点）。 [区域代码在这里](https://fly.io/docs/reference/regions/#fly-io-regions)。

- `--name=<AppName> `表示创建的 app 名字，将`<AppName> `替换成你自己的，并且注意，将来生成的默认网址是`<AppName>.fly.dev`,所以请想一个独一无二的名称。

- `--no-deploy`表示暂时不部署。

这会在 blog 目录里生成一个 fly.toml 文件，使用文本编辑器打开它，使用如下代码覆盖。

```toml

app = "<AppName>"
kill_signal = "SIGINT"
kill_timeout = 5
processes = []

[build]
  image = "ghost:5"

[env]
  url = "https://<AppName>.fly.dev"
  database__client = "sqlite3"
  database__connection__filename = "content/data/ghost.db"
  database__debug = "false"
  database__useNullAsDefault = "true"
  mail__from = "noreply@example.com"
  mail__options__auth__pass = "<YourMailgunPassword>"
  mail__options__auth__user = "postmaster@example.com"
  mail__options__host = "smtp.mailgun.org"
  mail__options__port = "465"
  mail__transport = "SMTP"

[experimental]
  auto_rollback = true

[mounts]
  destination = "/var/lib/ghost/content"
  source = "data"

[[services]]
  http_checks = []
  internal_port = 2368
  processes = ["app"]
  protocol = "tcp"
  script_checks = []
  [services.concurrency]
    hard_limit = 25
    soft_limit = 20
    type = "connections"

  [[services.ports]]
    force_https = true
    handlers = ["http"]
    port = 80

  [[services.ports]]
    handlers = ["tls", "http"]
    port = 443

    [services.ports.http_options.response.headers]
      Referrer-Policy = "strict-origin"
      Strict-Transport-Security = "max-age=63072000; includeSubDomains; preload"
      X-Content-Type-Options = "nosniff"
      X-Frame-Options = "SAMEORIGIN"
      x-xss-protection = "1; mode=block"
      Permissions-Policy = "camera=(), microphone=(), geolocation=(), browsing-topics=()"

  [[services.tcp_checks]]
    grace_period = "1s"
    interval = "15s"
    restart_limit = 0
    timeout = "2s"
```

请将`<AppName>`替换成你自己的，并且，如果不用[Mailgun](https://ghost.org/docs/faq/mailgun-newsletters/)，请删除`[env]`中`mail__`开头的所有代码。

其中`[services.ports.http_options.response.headers]`这一部分是可选的，用于设定 http header。可以逐项搜索`Strict-Transport-Security`，比如，确定你是否要确定将这项加入。部署完毕之后，http header 检测地址在[这里](https://securityheaders.com/)。

检查完毕后，保存并关闭 fly.toml 文件。然后回到终端，继续执行：

```shell
  flyctl volumes create data  -r hkg --no-encryption --size 1 #创建一个大小为1Gb的卷，区域为hkg，不加密（有助于提高性能）。免费额度共3GB。
  flyctl deploy #部署
```

等待片刻，部署成功！会显示`successful`.

## 3. 初始化 Ghost

访问

```shell
https://<AppName>.fly.dev/ghost/
```

以初始化 ghost。在这个之后，你就可以自由使用 ghost 来发布内容了。绑定域名、备份和恢复数据是可选的操作。

## 4. 绑定域名

运行：

```shell
  flyctl ips list
```

以查看你的 app 的 IP 地址。然后在你的 DNS 服务器上为 ipv4 创建 A 记录，为 ipv6 创建 AAAA 记录，指向你的域名`example.com`（必须）。创建 CNAME，`<AppName>.fly.dev`，指向你的`www.example.com` （非必须）。也就是

| 类型  | 记录 | 值                  |
| ----- | ---- | ------------------- |
| A     | @    | ipv4 address        |
| AAAA  | @    | ipv6 address        |
| CNAME | www  | `<AppName>.fly.dev` |

**注意**：在绑定域名**之前**，一定要确保正确创建 DNS 记录。

然后运行：

```shell
flyctl certs create example.com
flyctl certs create www.example.com
```

等待片刻，运行

```shell
flyctl certs check example.com
flyctl certs check www.example.com
```

以检查证书颁布的情况，一般只要 DNS**提前**配置正确，大约需要一两分钟。运行

```shell
flyctl ips list
```

以查看证书颁发情况。

**注意**：不要反复安装证书，因为有限额，[每 7 天只能颁布 5 张证书](https://community.fly.io/t/awaiting-certification-11-hours/7635/8?u=pathsis)。建议在调试完 app 后，再绑定。

## 5.重新部署

注意到 fly.toml 的

```toml
[env]
  url = "https://<AppName>.fly.dev"
```

是 fly.io 分配的地址，如果你点击 ghost 网站的主页标题，就会转向这个地址，所以，当你绑定了自己的域名，将其换成

```toml
[env]
  url = "https://example.com"
```

保存并关闭，然后运行`flyctl deploy`。

## 6. 备份和恢复

以后每一次需要进入你本地的配置目录，才能正确使用 flyctl。

### 6.1 方法 1：使用 SFTP 备份 Ghost

优点是无需复杂配置，但复制速度极慢。

#### 6.1.1 备份

首先登录（假设你以后需要备份）；

```shell
cd blog
flyctl auth login
```

然后运行

```shell
flyctl ssh sftp shell -r -a <AppName>
```

成功后，会显示`>>`（我这里是红色的），然后输入

```shell
get /var/lib/ghost/content/
```

这将备份全站数据，包括主题、图片、视频、文章等等。速度很慢，请耐心等待。

也可以只备份图片和视频，运行

```shell
get /var/lib/ghost/content/images/
get /var/lib/ghost/content/media/
```

这在 blog 目录里将生成一个 content.zip，或，images.zip 和 media.zip。将它们备份到其他地方，或命名为 content-YYYY-MM-DD.zip。

#### 6.1.2 恢复

现在假设你重新安装了一个新的 ghost，假设还是在 fly.io，那么安装目录仍然保持为`/var/lib/ghost/content/`，假设你今后在别的地方，比如 AWS 上安装 ghost，确保创建的目录为这个而不是一般教程所说的`/var/www/ghost/content/`，否则恢复数据会遇到麻烦。

仍然运行

```shell
cd blog
flyctl auth login
flyctl ssh sftp shell -r -a <AppName>
```

然后运行

```shell
put content.zip /var/lib/ghost/content.zip
```

成功后，在终端新一个标签页，然后运行

```shell
flyctl ssh console
```

进入 ssh 后，运行

```shell
apt-get update && apt-get upgrade && apt-get install unzip
```

以安装`unzip`。然后运行

```shell
cd /var/lib/ghost/
unzip content.zip
```

会直接覆盖原先的 content 文件夹。

为验证是否成功解压，运行

```shell
cd /var/lib/ghost/content/images/
ls #列出当前文件夹下的所有的文件
```

查看是否有新的数据。

为修复权限，运行

```shell
chown -R node:node /var/lib/ghost/content/
```

**注意**：可能的情况，无法正确覆盖 content 文件夹，那么请尝试只备份 `/var/lib/ghost/content/images/`和 `/var/lib/ghost/content/media/`。此时运行的是

```shell
put images.zip /var/lib/ghost/content/images.zip
put media.zip /var/lib/ghost/content/media.zip

rm -rf /var/lib/ghost/content/images/
rm -rf var/lib/ghost/content/media/

unzip /var/lib/ghost/content/images.zip
unzip /var/lib/ghost/content/media.zip

```

可能会破坏 content 文件夹的权限，运行

```shell
ls -l /var/lib/ghost/content/
```

以查看 images 和 media 文件夹的用户和权限，若其权限为 root，则不能上传图片和视频了，则运行

```shell
chown -R node:node /var/lib/ghost/content/
chown -R node:node /var/lib/ghost/content/images/
chown -R node:node /var/lib/ghost/content/media/
```

以修复，注意，其中的`node`是在 fly.io 案例中的 ghost 用户，具体情况视`ls -l /var/lib/ghost/content/`命令的结果为准，总之确保 images 和 media 文件夹的用户和 content 下的其他文件的用户一样。

### 6.2 方法 2：使用 Github 备份 Ghost

优点是复制速度快，但缺点是安装配置相对复杂。

#### 6.2.1 备份

1.登录并进入 ssh

```shell
cd blog
flyctl auth login
flyctl ssh console
```

2.安装 git

```shell
apt-get update && apt-get upgrade && apt-get install git
```

3.在 github 网页端先创建一个私密仓库（推荐），假设名为`<YourRepository>`。

4.生成密钥

```shell
ssh-keygen -t rsa -C "<GithubEmail>"  #连续按回车键
```

5.终端新建标签，运行

```shell
flyctl ssh sftp shell -r -a <AppName>
get /root/.ssh/id_rsa.pub
```

回到 blog 文件夹里找到 id_rsa.pub 文件，用文本编辑器打开，并复制其中的密钥。将其添加到 github 的`setting→SSH and GPG keys→SSH keys`中，保存。

测试与 github 的通信

```shell
ssh -T git@github.com
```

留意有没有 successful 的字眼。

```shell
ssh -T git@github.com
Hi Pathsis! You've successfully authenticated, but GitHub does not provide shell access.
```

6.初始化 content 的 git

```shell
cd /var/lib/ghost/content/
git init
git config --global user.name "<GithubUsername>"
git config --global user.email <GithubEmail>
git remote add origin git@github.
com:<GithubUsername>/<YourRepository>.git
git config --global --add safe.directory /var/lib/ghost/content
git add .
git commit -m "auto backup"
git push -u origin master --force
```

确保成功 push 到 github。

7.新建一个脚本

```shell
apt-get update && apt-get upgrade && apt-get install nano
cd /var/lib/ghost/content/
nano auto_run.sh
```

复制以下代码到其中

```shell
#!/bin/sh

cd /var/lib/ghost/content # 切换到目录
git config --global init.defaultBranch master
git config --global --add safe.directory /var/lib/ghost/content
git pull # 拉取仓库
git add . # 添加暂存
git commit -m "auto backup" # 提交
git push --force
```

按`ctrl`+`O`之后再回车，以写入；按`ctrl`+`x`，以退出 nano。

赋予该文件运行权限

```shell
chmod a+x auto_run.sh
```

以后，登录 ssh 后，可以直接运行

```shell
sh /var/lib/ghost/content/auto_run.sh
```

以执行新的 push。

#### 6.2.2 恢复

1.登录 shh，重新安装 git，添加密钥，不再赘述。

2.清空 content 文件夹

```shell
cd /var/lib/ghost/
rm -rf content
```

会返回说,该文件夹无法删除，因为其`busy`，没关系，它已经被清空，但没有被删除。

3.初始化 content 文件中的 git，并强制 pull

```shell
cd /var/lib/ghost/content/
git init
git config --global user.name "<GithubUsername>"
git config --global user.email <GithubEmail>
git pull --force git@github.com:<GithubUsername>/<YourRepository>.git
```

4.验证是否成功拉取

```shell
ls
```

5.确保成功拉取数据后，重启 app

```shell
fly apps restart <AppName>
```

目前来看，重启或重新部署，会清除安装的环境和软件，但不会删除 ghost 的数据。

6.在 docker 中运行 cron 实在困难，不用尝试了。在普通虚拟机中，可以设置 cron，以定时运行

```shell
sh /var/lib/ghost/content/auto_run.sh
```


这篇文章介绍了在 fly.io 上免费运行 Ghost 博客，备份和还原数据的方法。备份和恢复数据对其他服务器上的用例具有参考意义。

在 fly.io 免费运行 Ghost 博客：安装、备份和恢复


![Ghost](https://res-4.cloudinary.com/mkyos/image/upload/q_auto/v1/blog-images/website-on-ghost.png)

要问我为什么？ghost 比 wordpress 好吗？不是。ghost 现在对于普通用户来说一点也不友好，它没有搜索功能，不提供评论系统，Newsletter(时事通讯)功能也刚刚脱离实验室阶段。现在，一个运行 ghost 的**博客网站**(注意，不是“**在线出版网站**”)就像一个孤岛。将 wordpress 迁移到 ghost，我感觉我要与老朋友们失去联系，再也不能与他们轻松互动。

事实上，ghost 已经朝着相当不同于 wordpress 的方向发展。根据创立者 2018 年的[一篇文章](https://ghost.org/blog/5/)，它越来越朝着专业化和商业化——ghost 自身的专业化、目标用户的商业化——的方向进展。

在 ghost 的最初阶段，创立者曾对此有过犹豫，他试图把 ghost 这个去中心化、开源的在线出版程序打造得与中心化、闭源的 Medium 一样易用，比如，用户可以通过简单的几个步骤就将 algolia 添加到 ghost 上，享受后者强大的搜索服务。但是，他放弃了，因为他觉得，即使 ghost 为用户提供十分简单的框架，普通用户还是不懂得如何从 algolia 那里获得 API Key，这些操作依然足以吓退他们。所以，他干脆转向“专业”用户。似乎，在他看来，所谓“专业用户”，是至少能够承受 ghost 那烦琐的调试和安装压力的人，且没有“下限”。ghost 越来越不是我们期待中的博客系统。此外，它的运营机构现在很挣钱，月营收已经达到了 8 万多美元，创立 5 年，累计营收 300 万美元，而且，从一开始就盈利！

我在[ghost 的 Producthunt 主页](https://www.producthunt.com/posts/ghost-4-0?bc=1)上看到创立者 O'Nolan 自己的长篇评论，于是不由得也回复了一大段给他，翻译为中文，部分如下：

> 亲爱的 O'Nolan 先生，感谢你的伟大产品！当你打算在 producthunt 的产品页面上发表如此长的评论时，你应该感到你是多么需要评论系统。也许你甚至没有感觉到，因为 producthunt 自然地为你提供了它。然而，ghost 用户就没有这么幸运了。你会发现，大多数运行 ghost 的网站都没有评论系统，除了一些运营者觉得自己不需要评论系统之外，一个重要的原因是，众所周知，任何一个不起眼的博客系统，都会努力提供评论系统，而 ghost 却没有。除了评论系统之外，搜索功能也是如此。如果我听到 ghost 并想在 producthunt 了解下它，但在 producthunt 却找不到任何搜索框，这将是多么令人沮丧，甚至愤怒的事情。我也曾为 ghost 感到沮丧，甚至恼怒。最近，我在官方博客上读了你的文章，我越来越理解你了。你谈到了 ghost 在开发去中心化的开源软件时面临的困难选择，你明确提到你曾想让普通用户通过简单的设置就能获得像 algolia 这样的伟大服务。然而，你放弃了，认为即使这样，普通用户也不会成功，所以你转向了 “专业”用户。我们知道，在 Wordpress 上，只需一个插件和一些复制和粘贴操作，用户就可以享受到 algolia 的伟大服务，而 Wordpress 也是去中心化的开源软件。在所谓的普通用户和 “专业”用户之间也是有许多中间阶段的。我看到，许多人绞尽脑汁想在他们的 ghost 网站上添加一个搜索按钮，但无济于事。官方文件是如此的粗糙，以至于毫无用处！ 事实上，“专业用户”很难被定义，我见过许多人，他们足够专业，试图在他们的博客上添加一个可用的搜索框，但几乎无一例外地失败。

除了上面宏观的产品战略外，一个相对微观的技术策略是，**ghost 希望保持足够的灵活和开放，它希望所有的这些基础功能，都能由相应的细分领域的产品提供**。搜索、评论、Newsletter、统计分析，等等等等。只是，它为自己没有提供搜索、评论等基础功能所提供的理由实在勉强。事实上，wordpress.com 的官方插件 Jetpack 提供开箱即用的 Newsletter 功能。ghost 不会说 wordpress 比自己还灵活。

Newsletter 是最为吸引我的。这几年，电子邮件作为古老的通讯手段，受到人们的重视。通过 Newsletter，**作家**可以独立自由地维护读者关系，而**读者**则可以主动的筛选信息来源，而不是接受铺天盖地的“算法推送”。但是，大部分国人对此还没有什么概念。他们沉浸在抖音、头条、知乎和 B 站等中心化的网站中。邮件订阅给国人的普遍印象，还是商业营销手段，而不是出版工具。在可预见的时期内，Newsletter 出版不会在中国壮大，原因是众所周知的。

尽管如此，我仍觉得我需要它，或者，我想尝试它，把玩下它。ghost 的邮件简洁漂亮，与之相比，Jetpack 略显土气。我知道我可能没有什么订阅者。我的老朋友们，可以轻松地用 inoreader 等程序来管理 RSS 订阅。我只是有一点点幻想，经过好多年，由于我持续制造了对于我的领域内的人还算有用的东西，会收获那么十几个或几十个订阅。

设置 ghost 的 Newsletter 对我的挑战是巨大的。我在 ghost 和 Mailgun 上分别执行了一切操作，但就是无法成功发送邮件。我在互联网上看到大量的询问和抱怨，他们不知道问题出在了哪里。最后我发现，原来我的 Mailgun 账户尚未成功激活！我没有激活，却在控制面板上看不到任何提示，即使执行了那么多操作！没有激活，是因为，最初我申请 Mailgun 时，没有通过短信验证那一关。过了一段时间，我发现能够成功登录，并且能够“正常”使用，竟然忘了这一点。认识到这个问题后，我给 Mailgun 的客服发了一封邮件，很快就收到回复，他(她)为我激活了账户。于是，我的 ghost 的 newsleter 活了！

ghost 的定位为**在线出版程序**，或许可以说，它是 CMS 的一个细分领域。ghost 以 Newsletter 为媒介，为独立作家提供在线发布、读者维护和营收管理的框架，为未来的出版潮流推波助澜。如果你也需要这么一个东西，那么你可以尝试它。邮箱设置的困难已被克服，与 algolia 的整合，未来应该会有很大的进展，评论系统也是这样。如果考虑了以上问题后，你仍觉得你需要 ghost，那么可以尝试它，如果遇到什么困难，请不要犹豫联系我。

最后，如果你只是想尝试 Newsletter，你完全可以在 wordpress 上借助 Jetpack 轻松实现，开箱即用！按照一个博客程序的标准来评价的话，ghost 现在还像一个不能看时间的 Apple Watch。再给它一点时间；或许需要更多时间。

2021.10.12


ghost的定位是在线出版程序，而不是通用CMS。它希望保持足够的灵活，所有的基础功能由更细分领域的其他产品提供。就一个博客程序而言，由于没有提供搜索和评论等基础功能，ghost目前就像一个不能看时间的Apple Watch 。

标签 ghost