<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Hosted-Runner on PlumePHP</title><link>https://plumephp.com/tags/self-hosted-runner/</link><description>Recent content in Self-Hosted-Runner on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Tue, 22 Sep 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/self-hosted-runner/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Actions 自托管 Runner：架构设计、安全隔离与大规模部署</title><link>https://plumephp.com/github-actions-self-hosted-runners/</link><pubDate>Tue, 22 Sep 2026 10:00:00 +0800</pubDate><guid>https://plumephp.com/github-actions-self-hosted-runners/</guid><description>&lt;blockquote&gt;
&lt;p&gt;GitHub Actions 的免费托管 Runner（&lt;code&gt;ubuntu-latest&lt;/code&gt;、&lt;code&gt;windows-latest&lt;/code&gt;、&lt;code&gt;macos-latest&lt;/code&gt;）足以覆盖大多数开源项目的持续集成需求。但当你的团队遇到以下任何一种情况时，自托管 Runner（Self-hosted Runner）就成为必选项：需要访问私有网络资源、需要特定硬件（GPU/ARM/大内存）、构建时间要求缩短 80% 以上、或者代码合规政策禁止代码离开内网。本文将从架构选型到生产部署，系统梳理自托管 Runner 的全链路实践。&lt;/p&gt;</description></item></channel></rss>