---
title: "All posts - Owen"
url: "https://www.owenyoung.com/archive?layout=list&page=55"
markdown_url: "https://www.owenyoung.com/archive.md?layout=list&page=55"
site: "Owen"
language: "zh-Hans"
page: 55
total_pages: 55
llms: "https://www.owenyoung.com/llms.txt"
skill: "https://www.owenyoung.com/skill.md"
mcp: "https://www.owenyoung.com/api/mcp"
public_mcp: "https://www.owenyoung.com/api/public/mcp"
public_api: "https://www.owenyoung.com/api/public/threads"
---

# All posts - Owen

*For AI assistants — Site overview: [llms.txt](https://www.owenyoung.com/llms.txt) · Author/agent guide: [skill.md](https://www.owenyoung.com/skill.md) · Public read-only MCP: https://www.owenyoung.com/api/public/mcp*

---

## 重新开始投资

说起来我投资的时间还蛮久的，从大学的时候就开了股票账户，一直到现在有 8 年以上的投资经验了，但其实还是像一个菜鸟一样，没赚过什么钱，当然，万幸的是至少没亏钱。

今天有一笔股市打新的意外收入，填平了一直萦绕在我心里的 3 年前的一笔股票巨额亏损，这让我终于没了心魔，这才敢在 Google Sheet 里创建了一个表格，总结了下近几年的投资收益和各个账户的资金状态（还有一个原因是，我一直想总结下自己在各个银行开立的账户，万一我发生什么意外，让亲友能知道我的账户情况）

<!--more-->

总的来说，总盈利 60000 元左右，其中基金 25000，数字货币 25000，股票 10000.

总结完毕后，觉得神清气爽，在表格里记录自己的各项账户余额真是一个很有必要的做法，想想以前的自己，唉，竟然一直都马马虎虎的在脑子中记个大概的数，我觉得这可能也是遗传了家人的性格，父母从来不把自己的钱做一个清晰的规划，所以这么多年来他们的钱老是攒不起来，我要找个时间给他们做一次整理。

我决定把 2021-02-04，作为我投资生涯的一个新的开始，以今天为初始资金的计算点，开启今后的投资，每半年更新下 Google Sheet，看看收益如何。

我在表格里记录了以下字段：

- 平台
- 金额
- 状态
- 到期时间
- 预估到期收益
- 方式
- 年化收益率 %
- 派息时间
- 登录入口
- 存入时间
- 平台账号
- 产品名称
- 登录方式
- 登录账号
- 分行
- 唯一标识
- 银行卡号

希望以后能分享一些投资心得吧（前提是赚钱了的话，亏钱的话都不敢看账户的

_2021-02-04 · note_ — [HTML](https://www.owenyoung.com/blog/start-investing-again) · [Markdown](https://www.owenyoung.com/blog/start-investing-again.md)

---

## 如何培养长期的英文阅读兴趣？

在我自己博客里的[/about](https://blog.owenyoung.com/about/)页里对自己的第一个介绍就是:**A failure of English learning**, 一个学了 10 年英语的菜鸟，我自己认为根本原因是我的意志力，物理原因主要是对英文的练习不够，所以我现在的主要思路还是要提高英语的练习量，重点是坚持。

<!--more-->

第一次看到[湾区日报](https://wanqu.co/)的时候觉得，哇又能看自己感兴趣的，又能看原文学英语，多好！但是最后还是没能坚持看下去，为啥呢？可能还是因为这事太正能量了，潜意识可能告诉我，这是工作不是兴趣！不然为啥刷推刷的那么频繁呢？

所以，为了让自己像刷推一样刷感兴趣的英文讯息，我仿照湾区日报的模式，做了几个导读网站 - [Buzzing](https://www.buzzing.cc/)，其中我每天必刷的有[Reddit 热门](https://reddit.buzzing.cc/), [国外股市热门](https://stocks.buzzing.cc/), [Hacker News 热门](https://hn.buzzing.cc/), [Product Hunt 热门](https://ph.buzzing.cc/)， [Reddit 热门提问](https://ask.buzzing.cc/)

导读内容的翻译是自动进行的，用的是[deepl](https://www.deepl.com/en/translator)的服务，据说是翻译中文最好的翻译引擎，我试了谷歌翻译，腾讯翻译和 deepl，确实 deepl 翻译的更准确一点。

目前推进的很好，每天都会上去看更新，而且是带着强烈兴趣的去看更新，有了中文导读之后，可以更快的找到自己想看的内容，然后进去之后看原文会更有动力。

如果你也有类似问题，可以尝试刷下[Buzzing](https://www.buzzing.cc/)，或者你有一些感兴趣的主题，也可以 DM 或者邮件联系我，可以新增一些主题～

_2021-02-03 · note_ — [HTML](https://www.owenyoung.com/blog/how-do-i-cultivate-long-term-interest-in-english-reading) · [Markdown](https://www.owenyoung.com/blog/how-do-i-cultivate-long-term-interest-in-english-reading.md)

---

## 使用Actionsflow在Github上免费部署Rsshub

[Rsshub](https://github.com/DIYgod/RSSHub)是一个很棒的工具，把很多知名或不知名的网页数据通通统一为[RSS 格式](https://en.wikipedia.org/wiki/RSS)，堪称中文互联网的 W3C. 但是官方推荐的部署方式是[Docker 部署](https://docs.rsshub.app/install/#docker-compose-bu-shu)，对于大多数轻量使用的用户来说有点重，所以这里介绍一种免费，轻量，按需使用的部署方式，利用[Actionsflow](https://github.com/actionsflow/actionsflow)部署在 GitHub 的 [Actions](https://docs.github.com/en/actions) 上。

[Actionsflow](https://github.com/actionsflow/actionsflow)是一个基于 Github Actions 上的 IFTTT/Zapier 的开源替代，使用 [Github Actions 的配置格式](https://actionsflow.github.io/docs/workflow/)来配置你需要的工作流, 更多关于 Actionsflow 的使用可以看我的[另一篇文章介绍](https://blog.owenyoung.com/zh/posts/actionsflow/),或者[官方文档](https://actionsflow.github.io/docs/)

<!--more-->

比如我自己在用的一个工作流就是监控豆瓣车组的一些我需要的关键词，如果有提到关键词的帖子，那么发送一个 telegram 消息给我，配置如下：

```yaml
on:
  rsshub:
    path:
      - path: /douban/group/669481
        query:
          filter_case_sensitive: false
          filter_title: 罐头|狗粮|爱肯拿|渴望|姐妹们快|牛奶|牛肉|羊肉|来伊份岩烧|来伊份面包|烤箱|生鲜|螺蛳粉|米诺|果酸|杏仁酸|鸡蛋|大米|薅|cr海盐|洗头膏|崔娅蓬松|洗鼻|橙
          filterout_title: 求|转|求购|交流|已购|专楼|蒙牛|伊利|讨论|华为|停车|代拍|完|分装|意向|拼单|删|一元
jobs:
  ifttt:
    name: Make a Request to telegram
    runs-on: ubuntu-latest
    steps:
      - name: Send a telegram message
        uses: appleboy/telegram-action@v0.1.0
        with:
          to: ${{ secrets.TELEGRAM_TO }}
          token: ${{ secrets.TELEGRAM_TOKEN }}
          message: |
            <b>${{ on.rsshub.outputs.title}}</b>
            <a href="${{on.rsshub.outputs.link}}">${{on.rsshub.outputs.description}}</a>
          format: html
          disable_web_page_preview: true
```

> 配置来自[这里](https://github.com/theowenyoung/actionsflow-workflow/blob/main/workflows/rsshub.yml)

接下来介绍下如何部署：）

> 因为 rsshub 这个 trigger 没有内置在 Actionsflow 里，所以按照官方的教程初始化之后，需要主动安装下[@actionsflow/trigger-rsshub](https://github.com/theowenyoung/actionsflow-trigger-rsshub)这个 trigger

1. 使用这个[链接](https://github.com/actionsflow/actionsflow-workflow-default/generate)用 Actionsflow 的默认模板创建一个新的 GitHub 项目，一个典型的 Actionsflow 项目长这样：
   ```bash
   ├── .github
   │   └── workflows
   │       └── actionsflow.yml
   ├── .gitignore
   ├── README.md
   └── workflows
   │   └── rss.yml
   │   └── webhook.yml
   └── package.json
   ```
2. clone 你刚创建的项目到本地
   ```bash
   git clone git@github.com:<your-github-username>/<repo-name>
   ```
3. 在本地编辑 `.github/workflows/actionsflow.yml` 文件，取消`schedule`的注释
4. 安装[@actionsflow/trigger-rsshub](https://github.com/theowenyoung/actionsflow-trigger-rsshub)
   ```bash
   npm i @actionsflow/trigger-rsshub
   ```
5. 在`workflows/`文件夹创建你自己的 workflow 文件
   > workflow 的写法和 rsshub trigger 的用法清参考官方文档[Actionsflow Workflow Syntax](https://actionsflow.github.io/docs/workflow/), [Actionsflow rsshub trigger](https://github.com/theowenyoung/actionsflow-trigger-rsshub)
   > 可以参考[这里](https://actionsflow.github.io/docs/actions/)列出的 常用 Github Action，以及这个[Actionsflow 的 Awesome 项目](https://github.com/actionsflow/awesome-actionsflow)

   示例(`/workflow/rsshub.yml`)：
   ```yaml
   on:
     rsshub:
       path: /smzdm/keyword/女装
   jobs:
     print:
       name: Print
       runs-on: ubuntu-latest
       steps:
         - name: Print Outputs
           env:
             title: ${{on.rsshub.outputs.title}}
             description: ${{on.rsshub.outputs.description}}
             link: ${{on.rsshub.outputs.link}}
           run: |
             echo title: $title
             echo description: $description
             echo link: $link
   ```
6. 保存并提交你的文件到 Github

> 如果你想本地测试的话，需要先安装[Docker](https://docs.docker.com/get-docker/), 并运行 `npm run start`

_2021-02-03 · note_ — [HTML](https://www.owenyoung.com/blog/deploy-rsshub-with-actionsflow) · [Markdown](https://www.owenyoung.com/blog/deploy-rsshub-with-actionsflow.md)

---

## Actionsflow介绍 - 可以一键部署在Github上的IFTTT/Zapier的开源替代

我还记得当年第一次使用[IFTTT](https://ifttt.com)的时候的那种兴奋，天呐，这才是互联网！从那时起，就一直使用 IFTTT 到今天，真的很棒的一个产品！直到 IFTTT 最近宣布要收费，我就在想有没有合适的开源方案可以替代，因为托管方案肯定没戏了，连 10 年都免费的 IFTTT 都开始收费了，其他的只会更贵，结果发现主流的开源替代方案，比如 huginn, n8n, node-red 好像又有点重，不够轻量，而且扩展起来也不容易。

<!--more-->

刚好在那时看到[Github 的 Actions](https://docs.github.com/en/actions)支持[Schedule](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#schedule)事件，而 Github 的 Actions 又是对开源项目免费使用，所以就萌生了利用 Github Actions 的定时运行来检测更新，并执行指定动作。所以一个新的轮子[Actionsflow](https://github.com/actionsflow/actionsflow) 来了！

## 开始

1. 使用这个[链接](https://github.com/actionsflow/actionsflow-workflow-default/generate)用 Actionsflow 的默认模板创建一个新的 GitHub 项目，一个典型的 Actionsflow 项目长这样：
   ```bash
   ├── .github
   │   └── workflows
   │       └── actionsflow.yml
   ├── .gitignore
   ├── README.md
   └── workflows
   │   └── rss.yml
   │   └── webhook.yml
   └── package.json
   ```
2. 取消 `.github/workflows/actionsflow.yml` 文件里`schedule`的注释
3. 在`workflows/`文件夹创建你自己的 workflow 文件
4. 保存并提交你的文件到 Github

## 配置

我对 Actionsflow 的设计原则是规则尽可能简单，并且可扩展，workflow 的配置规则直接采用 Github Actions 的[配置格式](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions)，如果你之前有用过 Github Actions 的话，应该立刻就能懂 Actionsflow 的全部配置规则：

```yaml
on:
  rss:
    url: https://hnrss.org/newest?points=300
    config:
    	limit: 10
jobs:
  request:
    name: Make a HTTP Request
    runs-on: ubuntu-latest
    steps:
      - name: Make a HTTP Request
        uses: actionsflow/axios@v1
        with:
          url: https://hookb.in/VGPzxoWbdjtE22bwznzE
          method: POST
          body: |
            {
              "link":"${{ on.rss.outputs.link }}",
              "title": "${{ on.rss.outputs.title }}",
              "content":"<<<${{ on.rss.outputs.contentSnippet }}>>>"
            }
```

和原生的 Github Actions 的配置相比，Actionsflow 只是扩展了`on`的事件，在 Actionsflow 里，我把它叫做`trigger`， [RSS trigger](https://actionsflow.github.io/docs/triggers/rss/)经常被用来做示例使用，你可以点击\[这里\]([Actionsflow Triggers | Actionsflow Documentation](https://actionsflow.github.io/docs/triggers/))查看目前 Actionsflow 支持的所有 trigger. Trigger 里有个特殊的参数是`config`,这个 config 是通用参数，也就是所有的 trigger 都支持 config 参数，config 实现了很多通用的功能的，比如设置过滤条件，设置过滤条数，格式化输出结果，设置触发时间等等，点击\[这里\]([Workflow Syntax for Actionsflow | Actionsflow Documentation](https://actionsflow.github.io/docs/workflow/#ontriggerconfig)可以查看所有支持的配置。

其他的就和 Github Actions 的配置一样了，你可以在 jobs 里配置任何复杂的任务，或者简单的发个请求，你可以用 `${{ on.rss.outputs.<key> }}`来使用 trigger 的结果，每个 trigger 的结果的 key 需要去看对应 trigger 的文档。

我在[这里](https://actionsflow.github.io/docs/actions/)列出了你可能会用到的 Github Action，同时新建了一个[Awesome 项目](https://github.com/actionsflow/awesome-actionsflow)列出一些常用的 Actionsflow 工作流。

## Webhook

Actionsflow 不仅支持定时抓取类的任务，同时还支持 Webhook 类的任务，这样第三方服务如果有任何更新就可以主动通知 Actionsflow 了。这里 Webhook 机制是利用 Github 可以接收外界的 [`repository_dispatch`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#repository_dispatch) 事件来触发 Action 运行来实现的，具体使用可以见[这里](https://actionsflow.github.io/docs/triggers/webhook/)

## 本地运行

大多数情况下，使用 Github Actions 运行 Actionsflow 是更方便，也是推荐的使用方式，但是可能出于某种原因你需要在本地或者你自己的 VPS 上部署 Actionsflow. 要在本地运行 Actionsflow，必须先安装[Docker](https://www.docker.com/)

然后只需要运行:

```bash
docker run -it -v /var/run/docker.sock:/var/run/docker.sock -v ${PWD}:/data -p 3000:3000 actionsflow/actionsflow
```

手动运行方式见[这里](https://actionsflow.github.io/docs/self-hosted/#manual)

_2021-02-02 · note_ — [HTML](https://www.owenyoung.com/blog/actionsflow) · [Markdown](https://www.owenyoung.com/blog/actionsflow.md)

---

## A new Gatsby theme [Timeline] - Show your all posts, tweets, instagram posts into one

Don't you think there are too many different personal profile for us? Like twitter, instagram, facebook, blog, etc, So do I, I suppose there is an elegant site to show all my creative work, that's the new gatsby theme [Timeline](https://github.com/theowenyoung/gatsby-theme-timeline), a [Gatsby](https://www.gatsbyjs.com/) theme, you can use it to show your all posts, tweets, instagram posts etc into one blog. In my opinion, this is a real personal home.

Checkout my blog: [https://blog.owenyoung.com/](https://blog.owenyoung.com/)

[Source Repo](https://github.com/theowenyoung/gatsby-theme-timeline)

[Live Demo](https://gatsby-theme-timeline.owenyoung.com/)

<!--more-->

![Screen](https://media.jant.me/media/sit_01kmyfab3cfztrzn5qs9b80083/files/med_01kwtj8m0hfeza93aj1kfad6jb.png)

Here are the features for now:

- Support markdown, tweet, instagram posts, youtube videos, hacker news, reddit post
- Support i18n by [gatsby-theme-i18n](https://www.gatsbyjs.com/plugins/gatsby-theme-i18n/), you can choose your own [i18n library](https://github.com/gatsbyjs/themes/tree/master/packages)
- Support comments platform [disqus](https://disqus.com/) or [utterances](https://utteranc.es/)
- Support Tags
- Pagination, even tag pages support pagination
- SEO Optimization

Just start a new blog for yourself:

```bash
gatsby new my-themed-blog https://github.com/theowenyoung/gatsby-starter-timeline
```

> For more about installation please see [here](https://github.com/theowenyoung/gatsby-theme-timeline/tree/main/packages/gatsby-theme-timeline#installation)

## Note

In the starter demo, I use two gatsby plugins [gatsby-source-twitter](https://github.com/G100g/gatsby-source-twitter) and [gatsby-source-instagram](https://github.com/theowenyoung/gatsby-source-instagram) as the blog's sources. But in [my blog](https://blog.owenyoung.com), I use [Actionsflow](https://github.com/actionsflow/actionsflow) to get my tweets, instagram data, sync the JSON file to [my content source repository](https://github.com/theowenyoung/story) ((Why Actionsflow? For more stably, and I can store all my creative work into one)), and [site repository](https://github.com/theowenyoung/theowenyoung.github.io) use plugin [gatsby-source-git](https://github.com/theowenyoung/gatsby-source-git) to sync those data, and my markdown posts, for more tech stack, you can see [How I Built my Blog?](https://blog.owenyoung.com/en/posts/how-i-built-my-blog/)

> Disclaimer: I made the [Actionsflow](https://github.com/actionsflow/actionsflow) :)

_2021-01-29 · note_ — [HTML](https://www.owenyoung.com/blog/gatsby-timeline-theme/index-en) · [Markdown](https://www.owenyoung.com/blog/gatsby-timeline-theme/index-en.md)

---

## Open BBR for Debian

Enable TCP BBR on Debian.

<!--more-->

## Steps

1. Open the following configuration file to enable TCP BBR.

```bash
vi /etc/sysctl.conf
```

2. At the end of the config file, add the following lines.

```bash
net.core.default_qdisc=fq
net.ipv4.tcp_congestion_control=bbr
```

3. reload

```bash
sysctl -p
```

Now, Verify if BBR is enabled in your system,

```bash
sysctl net.ipv4.tcp_congestion_control
```

Output:

```bash
root@vps:~# sysctl net.ipv4.tcp_congestion_control
net.ipv4.tcp_congestion_control = bbr
```

_2021-01-26 · note_ — [HTML](https://www.owenyoung.com/blog/open-bbr-for-debian-en) · [Markdown](https://www.owenyoung.com/blog/open-bbr-for-debian-en.md)

---

## Anki背单词必备的3个插件

用了那么多背单词软件，发现还是[Anki](https://ankiweb.net/)好用，我觉得其中最好用是 Anki 提供的强大的 Tag 功能，你可以给每个单词打上一个 Tag ，这样方便你日后归类来复习这些单词，比如你可以有一个「hard」的 Tag。

<!--more-->

Tag 是 Anki 官方提供的功能，你可以直接在 Anki 上管理 tag，但是默认的 tag 管理比较不够便捷，所以如果配合以下插件，就能更方便的添加，查看 Tag。

这里纪录下我的 Anki 配置，希望你也能用得着。最终效果如下：

![](https://media.jant.me/media/sit_01kmyfab3cfztrzn5qs9b80083/files/med_01kwtj95k6feza93dgr0py0prw.png)

## 预先准备

- [下载 Anki 桌面版](https://apps.ankiweb.net/)
- \[下载一个词库\]\[[https://ankiweb.net/shared/decks/\]](https://ankiweb.net/shared/decks/]) - 可选，我初学的时候用的是这个排名第一的[4000 Essential English Words 英英](https://ankiweb.net/shared/info/1104981491)

## 必备插件

下载插件是在「Tools-&gt;Add-ons-&gt;Get Add-ons」,输入插件的 Code，插件的 Code 在插件主页上找到，\[点击这里\]([https://ankiweb.net/shared/addons/](https://ankiweb.net/shared/addons/) 2.1)可以浏览所有的插件。

> Note: 每次安装完插件后，重启才能生效。

### 1. [Quick tagging](https://ankiweb.net/shared/info/304770511)

Code: `304770511`

这个插件用来在 review 时，用快捷键快速添加 tag，默认是「q」键，你可以配置自己常用的 tag，比如「h」键添加一个「hard」标签。

以下是我的配置(其实就只是加了一个 hard 快捷键)：

```json
{
  "add tag shortcut": "q",
  "edit tag shortcut": "w",
  "quick tags": {
    "Ctrl+Shift+B": {
      "action": "bury note",
      "tags": "burynote"
    },
    "Shift+B": {
      "action": "bury card",
      "tags": "burycard"
    },
    "Shift+S": {
      "action": "suspend card",
      "tags": "suspend"
    },
    "h": {
      "action": "again card",
      "tags": "hard"
    }
  }
}
```

### 2. [Clickable Tags](https://ankiweb.net/shared/info/380714095)

Code: `380714095`

接下来就是这个 Clickable Tags 插件了，上一个插件解决了添加 Tag 的问题，这个插件解决显示 Tag 的问题，用了这个插件后你可以把这个单词所属的 Tag 都显示在 Review 页面，并且可以随时点击进去查看同个 Tag 的所有单词。效果如下：

![](https://media.jant.me/media/sit_01kmyfab3cfztrzn5qs9b80083/files/med_01kwtj980nfeza93e2mjsj7ztm.png)

安装完成后，你需要在你的单词模板里插入一个占位符来作为显示 Tag 的地方，步骤如下：

![](https://media.jant.me/media/sit_01kmyfab3cfztrzn5qs9b80083/files/med_01kwtj9a9nfeza93eqrd34xf00.png)

点击「Cards」，选择「Back Template」，在合适的地方插入 `{{clickable:Tags}}`

![](https://media.jant.me/media/sit_01kmyfab3cfztrzn5qs9b80083/files/med_01kwtj9cwkfeza93f0hckm4112.png)

保存并重启 Anki，你就会在卡片背面看到单词的 Tags（如果有 Tag 的话）

### 3. [Tag Entry Enhancements v2](https://ankiweb.net/shared/info/536796161)

Code: `536796161`

这个插件提供标签输入增强的，提供了以下功能：

- 添加 Return / Enter 作为热键以应用第一个建议的标签
- 将 Ctrl + Tab 作为热键添加以在建议列表中移动
- 输入字段时禁用初始建议框弹出窗口
- 允许使用 ↑/↓ 调用标签建议框

安装后重启即可使用

## 总结

总之，我使用 Anki 的重度功能就是这个 Tag，背到某个单词的时候，可以看到你标记的同类单词，这样更不容易忘记。

_2020-11-10 · note_ — [HTML](https://www.owenyoung.com/blog/anki-get-started) · [Markdown](https://www.owenyoung.com/blog/anki-get-started.md)

---

## Contact

- 我为这个博客建立的 Telegram 讨论群组：[https://t.me/+m124rcTl9FE3M2Vh](https://t.me/+m124rcTl9FE3M2Vh)
- 我的电子邮件：`owen#owenyoung.com` (把`#`换成`@`)
- [iMessage](sms:theowenyoung@gmail.com)
- 推特 [@OwenYoungZh](https://twitter.com/OwenYoungZh)
  - Twitter English [@TheOwenYoung](https://twitter.com/TheOwenYoung)
- Telegram 频道: [https://t.me/owenyoungzh](https://t.me/owenyoungzh)
- Telegram 私人账户: [https://t.me/itsowenyoung](https://t.me/itsowenyoung)
- 微信朋友圈（请大胆通过邮件或者 [Telegram](https://t.me/itsowenyoung) 联系我索要微信号，或者告诉我你的微信号，希望能同时附上你的公开主页如博客，小红书，即刻，推特等等（还没有？可以去[Pika](https://pika.page/) 或者 [Jant](https://jant.me) 新建一个！)
- Github [@theowenyoung](https://github.com/theowenyoung)
- 或者直接通过下面这个[表单](https://letterbird.co/owen)联系我，我会收到一封邮件：

```jant-html
<script data-letterbirduser="owen" src="https://letterbird.co/embed/v1.js"></script>
```

_2020-04-19 · note_ — [HTML](https://www.owenyoung.com/contact) · [Markdown](https://www.owenyoung.com/contact.md)

---

## Sonarr Setup

Before setup sonarr, you should setup [qBittorrent setup for Debian](/blog/qbittorrent-setup-for-debian.en)

<!--more-->

## Install

See [here](https://sonarr.tv/#downloads-v3-linux)

Once installed, visit [http://ip:8989](http://ip:8989)

## Restart

```bash
sudo systemctl restart sonarr
```

## Setup

See also [Sonarr Quick Start Guide | WikiArr](https://wiki.servarr.com/sonarr/quick-start-guide)

1. Click on `Settings => Media Management` on the left menu.

   Check `Rename Episodes`
2. Check left top `Show Advanced`

   `Importing` -&gt; `Import Extra Files` `.srt,.ass,.sub`
3. Add `/data/TV` to `Root Folders`
4. Indexers, Add `eztv`, `RARBG` as Indexers, see jackett home page.

### Add qBittorrent Client:

`Setting` -&gt; `Download Clients`  -&gt; `qBittorrent`

## Resource

- [高阶教程-追剧全流程自动化](https://sleele.com/2020/03/16/高阶教程-追剧全流程自动化/)

_2020-03-26 · note_ — [HTML](https://www.owenyoung.com/blog/sonarr-setup-en) · [Markdown](https://www.owenyoung.com/blog/sonarr-setup-en.md)

---

## Radarr Setup

[repo](https://github.com/Radarr/Radarr)

<!--more-->

## Install

See also [here](https://wiki.servarr.com/radarr/installation#linux)

[Latest Release](https://github.com/Radarr/Radarr/releases)

### Systemd

```bash
cat << EOF | sudo tee /etc/systemd/system/radarr.service > /dev/null
[Unit]
Description=Radarr Daemon
After=syslog.target network.target
[Service]
User=green
Group=admin
Type=simple

ExecStart=/home/green/radarr/Radarr -nobrowser -data=/home/green/.config/radarr/
TimeoutStopSec=20
KillMode=process
Restart=always
[Install]
WantedBy=multi-user.target
EOF
```

_2020-03-26 · note_ — [HTML](https://www.owenyoung.com/blog/radarr-setup-en) · [Markdown](https://www.owenyoung.com/blog/radarr-setup-en.md)

---

## Peertube Setup with Caddy Server

Peertube is an activityPub-federated video streaming platform using P2P directly in your web browser.

<!--more-->

Also see [here](https://github.com/Chocobozzz/PeerTube/blob/develop/support/doc/production.md)

## Pre Requirement

1. [Debian Server Setup](/blog/debian-server-setup.en)
2. [Caddy2 Setup for Debian](/blog/caddy2-setup-for-debian.en)
3. [Nodejs Setup for Debian](/blog/nodejs-setup-for-debian.en)
4. Install yarn, and be sure to have [a recent version](https://github.com/yarnpkg/yarn/releases/latest): [https://yarnpkg.com/en/docs/install#linux-tab](https://yarnpkg.com/en/docs/install#linux-tab)

```bash
sudo npm i -g yarn
```

4. Install Python:

On Ubuntu &lt;= bionic (18.04 LTS) or Debian &lt;= Buster:

```
sudo apt update
sudo apt install python-dev
python --version # Should be >= 2.x or >= 3.x
```

On Ubuntu &gt;= focal (20.04 LTS) or Debian &gt;= Bullseye:

```
sudo apt update
sudo apt install python3-dev python-is-python3 # python-is-python2 should also work
python --version # Should be >= 2.x or >= 3.x
```

## Install

1. Install common dependencies:

```
sudo apt update
sudo apt install certbot nginx ffmpeg postgresql postgresql-contrib openssl g++ make redis-server git cron wget
ffmpeg -version # Should be >= 4.1
g++ -v # Should be >= 5.x
```

Now that dependencies are installed, before running PeerTube you should start PostgreSQL and Redis:

```
sudo systemctl start redis postgresql
```

### PeerTube user

Create a `peertube` user with `/var/www/peertube` home:

```
$ sudo useradd -m -d /var/www/peertube -s /bin/bash -p peertube peertube
```

Set its password:

```
$ sudo passwd peertube
```

### Database

Create the production database and a peertube user inside PostgreSQL:

```
$ cd /var/www/peertube
$ sudo -u postgres createuser -P peertube
```

For password you can use `peertube` from the default config yaml.

Here you should enter a password for PostgreSQL `peertube` user, that should be copied in `production.yaml` file. Don't just hit enter else it will be empty.

```
$ sudo -u postgres createdb -O peertube -E UTF8 -T template0 peertube_prod
```

Then enable extensions PeerTube needs:

```
$ sudo -u postgres psql -c "CREATE EXTENSION pg_trgm;" peertube_prod
$ sudo -u postgres psql -c "CREATE EXTENSION unaccent;" peertube_prod
```

### Prepare PeerTube directory

Fetch the latest tagged version of Peertube

```
$ VERSION=$(curl -s https://api.github.com/repos/chocobozzz/peertube/releases/latest | grep tag_name | cut -d '"' -f 4) && echo "Latest Peertube version is $VERSION"
```

Open the peertube directory, create a few required directories

```
$ cd /var/www/peertube
$ sudo -u peertube mkdir config storage versions
$ sudo -u peertube chmod 750 config/
```

Download the latest version of the Peertube client, unzip it and remove the zip

```
$ cd /var/www/peertube/versions
$ sudo -u peertube wget -q "https://github.com/Chocobozzz/PeerTube/releases/download/${VERSION}/peertube-${VERSION}.zip"
$ sudo -u peertube unzip -q peertube-${VERSION}.zip && sudo -u peertube rm peertube-${VERSION}.zip
```

Install Peertube:

```
cd /var/www/peertube
sudo -u peertube ln -s versions/peertube-${VERSION} ./peertube-latest
cd ./peertube-latest
sudo -H -u peertube yarn install --production --pure-lockfile
```

### PeerTube configuration

Copy the default configuration file that contains the default configuration provided by PeerTube. You **must not** update this file.

```
$ cd /var/www/peertube
$ sudo -u peertube cp peertube-latest/config/default.yaml config/default.yaml
```

Now copy the production example configuration:

```
$ cd /var/www/peertube
$ sudo -u peertube cp peertube-latest/config/production.yaml.example config/production.yaml
```

Then edit the `config/production.yaml` file according to your webserver and database configuration (`webserver`, `database`, `redis`, `smtp` and `admin.email` sections in particular). Keys defined in `config/production.yaml` will override keys defined in `config/default.yaml`.

**PeerTube does not support webserver host change**. Even though [PeerTube CLI can help you to switch hostname](https://docs.joinpeertube.org/maintain-tools?id=update-hostjs) there's no official support for that since it is a risky operation that might result in unforeseen errors.

### Webserver

We only provide official configuration files for Nginx.

Copy the nginx configuration template:

```
$ sudo /etc/nginx/sites-available/peertube
```

with the following config:

```conf
# Minimum Nginx version required:  1.13.0 (released Apr 25, 2017)
# Please check your Nginx installation features the following modules via 'nginx -V':
# STANDARD HTTP MODULES: Core, Proxy, Rewrite, Access, Gzip, Headers, HTTP/2, Log, Real IP, SSL, Thread Pool, Upstream, AIO Multithreading.
# THIRD PARTY MODULES:   None.

upstream backend {
  server 127.0.0.1:9000;
}

server {
  listen 8880;
  listen [::]:8880;
  access_log /var/log/nginx/peertube.access.log; # reduce I/0 with buffer=10m flush=5m
  error_log  /var/log/nginx/peertube.error.log;

  ##
  # Certificates
  # you need a certificate to run in production. see https://letsencrypt.org/
  ##

  location @api {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host  $host;
    proxy_set_header X-Real-IP       $remote_addr;

    client_max_body_size  100k; # default is 1M

    proxy_connect_timeout 10m;
    proxy_send_timeout    10m;
    proxy_read_timeout    10m;
    send_timeout          10m;

    proxy_pass http://backend;
  }

  location / {
    try_files /dev/null @api;
  }

  location = /api/v1/videos/upload-resumable {
    client_max_body_size    0;
    proxy_request_buffering off;

    try_files /dev/null @api;
  }

  location = /api/v1/videos/upload {
    limit_except POST HEAD { deny all; }

    # This is the maximum upload size, which roughly matches the maximum size of a video file.
    # Note that temporary space is needed equal to the total size of all concurrent uploads.
    # This data gets stored in /var/lib/nginx by default, so you may want to put this directory
    # on a dedicated filesystem.
    client_max_body_size                      12G; # default is 1M
    add_header            X-File-Maximum-Size 8G always; # inform backend of the set value in bytes before mime-encoding (x * 1.4 >= client_max_body_size)

    try_files /dev/null @api;
  }

  location ~ ^/api/v1/(videos|video-playlists|video-channels|users/me) {
    client_max_body_size                      6M; # default is 1M
    add_header            X-File-Maximum-Size 4M always; # inform backend of the set value in bytes before mime-encoding (x * 1.4 >= client_max_body_size)

    try_files /dev/null @api;
  }

  ##
  # Websocket
  ##

  location @api_websocket {
    proxy_http_version 1.1;
    proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header   Host            $host;
    proxy_set_header   X-Real-IP       $remote_addr;
    proxy_set_header   Upgrade         $http_upgrade;
    proxy_set_header   Connection      "upgrade";

    proxy_pass http://backend;
  }

  location /socket.io {
    try_files /dev/null @api_websocket;
  }

  location /tracker/socket {
    # Peers send a message to the tracker every 15 minutes
    # Don't close the websocket before then
    proxy_read_timeout 15m; # default is 60s

    try_files /dev/null @api_websocket;
  }

  ##
  # Performance optimizations
  # For extra performance please refer to https://github.com/denji/nginx-tuning
  ##

  root /var/www/peertube/storage;

  # Enable compression for JS/CSS/HTML, for improved client load times.
  # It might be nice to compress JSON/XML as returned by the API, but
  # leaving that out to protect against potential BREACH attack.
  gzip              on;
  gzip_vary         on;
  gzip_types        # text/html is always compressed by HttpGzipModule
                    text/css
                    application/javascript
                    font/truetype
                    font/opentype
                    application/vnd.ms-fontobject
                    image/svg+xml;
  gzip_min_length   1000; # default is 20 bytes
  gzip_buffers      16 8k;
  gzip_comp_level   2; # default is 1

  client_body_timeout       30s; # default is 60
  client_header_timeout     10s; # default is 60
  send_timeout              10s; # default is 60
  keepalive_timeout         10s; # default is 75
  resolver_timeout          10s; # default is 30
  reset_timedout_connection on;
  proxy_ignore_client_abort on;

  tcp_nopush                on; # send headers in one piece
  tcp_nodelay               on; # don't buffer data sent, good for small data bursts in real time

  # If you have a small /var/lib partition, it could be interesting to store temp nginx uploads in a different place
  # See https://nginx.org/en/docs/http/ngx_http_core_module.html#client_body_temp_path
  #client_body_temp_path /var/www/peertube/storage/nginx/;

  # Bypass PeerTube for performance reasons. Optional.
  # Should be consistent with client-overrides assets list in /server/controllers/client.ts
  location ~ ^/client/(assets/images/(icons/icon-36x36\.png|icons/icon-48x48\.png|icons/icon-72x72\.png|icons/icon-96x96\.png|icons/icon-144x144\.png|icons/icon-192x192\.png|icons/icon-512x512\.png|logo\.svg|favicon\.png))$ {
    add_header Cache-Control "public, max-age=31536000, immutable"; # Cache 1 year

    root /var/www/peertube;

    try_files /storage/client-overrides/$1 /peertube-latest/client/dist/$1 @api;
  }

  # Bypass PeerTube for performance reasons. Optional.
  location ~ ^/client/(.*\.(js|css|png|svg|woff2|otf|ttf|woff|eot))$ {
    add_header Cache-Control "public, max-age=31536000, immutable"; # Cache 1 year

    alias /var/www/peertube/peertube-latest/client/dist/$1;
  }

  # Bypass PeerTube for performance reasons. Optional.
  location ~ ^/static/(thumbnails|avatars)/ {
    if ($request_method = 'OPTIONS') {
      add_header Access-Control-Allow-Origin  '*';
      add_header Access-Control-Allow-Methods 'GET, OPTIONS';
      add_header Access-Control-Allow-Headers 'Range,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
      add_header Access-Control-Max-Age       1728000; # Preflight request can be cached 20 days
      add_header Content-Type                 'text/plain charset=UTF-8';
      add_header Content-Length               0;
      return 204;
    }

    add_header Access-Control-Allow-Origin    '*';
    add_header Access-Control-Allow-Methods   'GET, OPTIONS';
    add_header Access-Control-Allow-Headers   'Range,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
    add_header Cache-Control                  "public, max-age=7200"; # Cache response 2 hours

    rewrite ^/static/(.*)$ /$1 break;

    try_files $uri @api;
  }

  # Bypass PeerTube for performance reasons. Optional.
  location ~ ^/static/(webseed|redundancy|streaming-playlists)/ {
    limit_rate_after            5M;

    # Clients usually have 4 simultaneous webseed connections, so the real limit is 3MB/s per client
    set $peertube_limit_rate    800k;

    # Increase rate limit in HLS mode, because we don't have multiple simultaneous connections
    if ($request_uri ~ -fragmented.mp4$) {
      set $peertube_limit_rate  5M;
    }

    # Use this line with nginx >= 1.17.0
    #limit_rate $peertube_limit_rate;
    # Or this line if your nginx < 1.17.0
    set $limit_rate $peertube_limit_rate;

    if ($request_method = 'OPTIONS') {
      add_header Access-Control-Allow-Origin  '*';
      add_header Access-Control-Allow-Methods 'GET, OPTIONS';
      add_header Access-Control-Allow-Headers 'Range,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
      add_header Access-Control-Max-Age       1728000; # Preflight request can be cached 20 days
      add_header Content-Type                 'text/plain charset=UTF-8';
      add_header Content-Length               0;
      return 204;
    }

    if ($request_method = 'GET') {
      add_header Access-Control-Allow-Origin  '*';
      add_header Access-Control-Allow-Methods 'GET, OPTIONS';
      add_header Access-Control-Allow-Headers 'Range,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';

      # Don't spam access log file with byte range requests
      access_log off;
    }

    # Enabling the sendfile directive eliminates the step of copying the data into the buffer
    # and enables direct copying data from one file descriptor to another.
    sendfile on;
    sendfile_max_chunk 1M; # prevent one fast connection from entirely occupying the worker process. should be > 800k.
    aio threads;

    rewrite ^/static/webseed/(.*)$ /videos/$1 break;
    rewrite ^/static/(.*)$         /$1        break;

    try_files $uri @api;
  }
}
```

Add caddy config:

```conf
example.com {
	reverse_proxy 127.0.0.1:8880
}
```

Then modify the webserver configuration file. Please pay attention to the `alias` keys of the static locations. It should correspond to the paths of your storage directories (set in the configuration file inside the `storage` key).

```
$ sudo vim /etc/nginx/sites-available/peertube
```

Activate the configuration file:

```
$ sudo ln -s /etc/nginx/sites-available/peertube /etc/nginx/sites-enabled/peertube
```

To generate the certificate for your domain as required to make https work you can use [Let's Encrypt](https://letsencrypt.org/):

```
$ sudo systemctl stop nginx
$ sudo certbot certonly --standalone --post-hook "systemctl restart nginx"
$ sudo systemctl reload nginx
```

Now you have the certificates you can reload nginx:

```
$ sudo systemctl reload nginx
```

Certbot should have installed a cron to automatically renew your certificate. Since our nginx template supports webroot renewal, we suggest you to update the renewal config file to use the `webroot` authenticator:

```
$ # Replace authenticator = standalone by authenticator = webroot
$ # Add webroot_path = /var/www/certbot
$ sudo vim /etc/letsencrypt/renewal/your-domain.com.conf
```

### TCP/IP Tuning

**On Linux**

```
$ sudo cp /var/www/peertube/peertube-latest/support/sysctl.d/30-peertube-tcp.conf /etc/sysctl.d/
$ sudo sysctl -p /etc/sysctl.d/30-peertube-tcp.conf
```

Your distro may enable this by default, but at least Debian 9 does not, and the default FIFO scheduler is quite prone to "Buffer Bloat" and extreme latency when dealing with slower client links as we often encounter in a video server.

### systemd

If your OS uses systemd, copy the configuration template:

```
$ sudo cp /var/www/peertube/peertube-latest/support/systemd/peertube.service /etc/systemd/system/
```

Check the service file (PeerTube paths and security directives):

```
$ sudo vim /etc/systemd/system/peertube.service
```

Tell systemd to reload its config:

```
$ sudo systemctl daemon-reload
```

If you want to start PeerTube on boot:

```
$ sudo systemctl enable peertube
```

Run:

```
$ sudo systemctl start peertube
$ sudo journalctl -feu peertube
```

Run:

```
$ sudo service peertube start
```

### Administrator

The administrator password is automatically generated and can be found in the PeerTube logs (path defined in `production.yaml`). You can also set another password with:

```
$ cd /var/www/peertube/peertube-latest && NODE_CONFIG_DIR=/var/www/peertube/config NODE_ENV=production npm run reset-password -- -u root
```

Alternatively you can set the environment variable `PT_INITIAL_ROOT_PASSWORD`, to your own administrator password, although it must be 6 characters or more.

### What now?

Now your instance is up you can:

- Add your instance to the public PeerTube instances index if you want to: [https://instances.joinpeertube.org/](https://instances.joinpeertube.org/)
- Check [available CLI tools](/support/doc/tools.md)

## Upgrade

### PeerTube instance

**Check the changelog (in particular BREAKING CHANGES!):** [https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md](https://github.com/Chocobozzz/PeerTube/blob/develop/CHANGELOG.md)

#### Auto

The password it asks is PeerTube's database user password.

```
$ cd /var/www/peertube/peertube-latest/scripts && sudo -H -u peertube ./upgrade.sh
$ sudo systemctl restart peertube # Or use your OS command to restart PeerTube if you don't use systemd
```

#### Manually

Make a SQL backup

```
$ SQL_BACKUP_PATH="backup/sql-peertube_prod-$(date -Im).bak" && \
    cd /var/www/peertube && sudo -u peertube mkdir -p backup && \
    sudo -u postgres pg_dump -F c peertube_prod | sudo -u peertube tee "$SQL_BACKUP_PATH" >/dev/null
```

Fetch the latest tagged version of Peertube:

```
$ VERSION=$(curl -s https://api.github.com/repos/chocobozzz/peertube/releases/latest | grep tag_name | cut -d '"' -f 4) && echo "Latest Peertube version is $VERSION"
```

Download the new version and unzip it:

```
$ cd /var/www/peertube/versions && \
    sudo -u peertube wget -q "https://github.com/Chocobozzz/PeerTube/releases/download/${VERSION}/peertube-${VERSION}.zip" && \
    sudo -u peertube unzip -o peertube-${VERSION}.zip && \
    sudo -u peertube rm peertube-${VERSION}.zip
```

Install node dependencies:

```
$ cd /var/www/peertube/versions/peertube-${VERSION} && \
    sudo -H -u peertube yarn install --production --pure-lockfile
```

Copy new configuration defaults values and update your configuration file:

```
$ sudo -u peertube cp /var/www/peertube/versions/peertube-${VERSION}/config/default.yaml /var/www/peertube/config/default.yaml
$ diff /var/www/peertube/versions/peertube-${VERSION}/config/production.yaml.example /var/www/peertube/config/production.yaml
```

Change the link to point to the latest version:

```
$ cd /var/www/peertube && \
    sudo unlink ./peertube-latest && \
    sudo -u peertube ln -s versions/peertube-${VERSION} ./peertube-latest
```

### nginx

Check changes in nginx configuration:

```
$ cd /var/www/peertube/versions
$ diff "$(ls --sort=t | head -2 | tail -1)/support/nginx/peertube" "$(ls --sort=t | head -1)/support/nginx/peertube"
```

### systemd

Check changes in systemd configuration:

```
$ cd /var/www/peertube/versions
$ diff "$(ls --sort=t | head -2 | tail -1)/support/systemd/peertube.service" "$(ls --sort=t | head -1)/support/systemd/peertube.service"
```

### Restart PeerTube

If you changed your nginx configuration:

```
$ sudo systemctl reload nginx
```

If you changed your systemd configuration:

```
$ sudo systemctl daemon-reload
```

Restart PeerTube and check the logs:

```
$ sudo systemctl restart peertube && sudo journalctl -fu peertube
```

### Things went wrong?

Change `peertube-latest` destination to the previous version and restore your SQL backup:

```
$ OLD_VERSION="v0.42.42" && SQL_BACKUP_PATH="backup/sql-peertube_prod-2018-01-19T10:18+01:00.bak" && \
    cd /var/www/peertube && sudo -u peertube unlink ./peertube-latest && \
    sudo -u peertube ln -s "versions/peertube-$OLD_VERSION" peertube-latest && \
    sudo -u postgres pg_restore -c -C -d postgres "$SQL_BACKUP_PATH" && \
    sudo systemctl restart peertube
```

_2020-03-26 · note_ — [HTML](https://www.owenyoung.com/blog/peertube-setup-with-caddy-server-en) · [Markdown](https://www.owenyoung.com/blog/peertube-setup-with-caddy-server-en.md)

---

## Nodejs Setup for Debian

## Install

See also [here](https://github.com/nodesource/distributions/blob/master/README.md)

```bash
# Using Debian, as root
curl -fsSL https://deb.nodesource.com/setup_14.x | bash -
apt-get install -y nodejs
```

_2020-03-26 · note_ — [HTML](https://www.owenyoung.com/blog/nodejs-setup-for-debian-en) · [Markdown](https://www.owenyoung.com/blog/nodejs-setup-for-debian-en.md)

---

## Nginx Setup for Debian

Install latest stable nginx for debian

> Also see [here](https://www.nginx.com/resources/wiki/start/topics/tutorials/install/)

<!--more-->

```bash
sudo su
cat <<EOF >> /etc/apt/sources.list.d/nginx.list
deb http://nginx.org/packages/debian/ buster nginx
deb-src http://nginx.org/packages/debian/ buster nginx
EOF
exit
curl -L https://nginx.org/keys/nginx_signing.key | sudo apt-key add -
sudo apt update
sudo apt install nginx
```

## Optional generate nginx conf online

Generate a nginx conf online at [here](https://www.digitalocean.com/community/tools/nginx)

If nginx conf need dhparam.pem, run :`cd /etc/nginx sudo openssl dhparam -dsaparam -out dhparam.pem 4096`

## Optional install acme.sh

```bash
sudo su
wget -O -  https://get.acme.sh | sh -s email=my@example.com
```

```bash
source ~/.bashrc
acme.sh --issue -d example.com --nginx
```

## Optional Install certbot

### Install snap

> [https://snapcraft.io/docs/installing-snapd](https://snapcraft.io/docs/installing-snapd)

```bash
sudo apt -y install snapd
sudo snap install core; sudo snap refresh core

```

> [https://certbot.eff.org/lets-encrypt/debianbuster-nginx](https://certbot.eff.org/lets-encrypt/debianbuster-nginx)

```bash
sudo snap install --classic certbot
sudo snap install certbot-dns-cloudflare
sudo ln -s /snap/bin/certbot /usr/bin/certbot
```

## Generate SSL

```bash
sudo certbot --nginx
```

_2020-03-26 · note_ — [HTML](https://www.owenyoung.com/blog/nginx-setup-for-debian-en) · [Markdown](https://www.owenyoung.com/blog/nginx-setup-for-debian-en.md)

---

## Metube Setup

Metube Setup with docker.

<!--more-->

## List

- [GitHub - alexta69/metube: youtube-dl web UI](https://github.com/alexta69/metube)
- [Metube chrome extension](https://chrome.google.com/webstore/detail/metube-downloader/fbmkmdnlhacefjljljlbhkodfmfkijdh)

## Setup

[Docker Install](https://docs.docker.com/engine/install/)

## Config

```yaml
version: "3"
services:
  metube:
    image: alexta69/

    container_name: metube
    restart: unless-stopped
    ports:
      - "10005:8081"
    volumes:
      - /data/youtube:/downloads
```

_2020-03-26 · note_ — [HTML](https://www.owenyoung.com/blog/metube-setup-en) · [Markdown](https://www.owenyoung.com/blog/metube-setup-en.md)

---

## Install PHP 8.0 On CentOS 7 / RHEL 7

```bash

yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm

yum install -y https://rpms.remirepo.net/enterprise/remi-release-7.rpm
yum install -y --enablerepo=remi-php80 php php-cli
php -v
```

_2020-03-26 · note_ — [HTML](https://www.owenyoung.com/blog/install-php8-on-centos7-en) · [Markdown](https://www.owenyoung.com/blog/install-php8-on-centos7-en.md)
