5 Steps to Deploy Hotfixes with Capgo

使用Capgo __CAPGO_KEEP_0__使部署热修复变得快速简单，跳过应用商店延迟，同时保持更新安全和符合Apple和Google的指南。以下是快速概述的过程：

1. 创建和测试修复补丁: 精确记录 code 的修改，严格测试设备，并确保兼容性。
2. 设置 Capgo: 安装 Capgo CLI ，配置加密， npx @capgo/cli init并与 CI/CD 工具集成。
3. 上传修复补丁: Use the CLI to securely upload your update, label it clearly, and prepare for deployment.
4. __CAPGO_KEEP_0__安全地上传您的更新，清晰地标记并准备部署。
5. 选择更新设置：: 监控送达率、更新速度和用户覆盖。如有需要，可立即回滚。

Capgo 已在全球范围内成功送达超过 9.476 亿次更新，并为用户提高了 81% 的发布效率。它是敏捷团队快速、安全部署热修复的首选工具。

步骤 1：创建和测试热修复

编写热修复 Code

专注于制作精确的更改，以解决 bug 而不损害应用程序的稳定性。

以下是快速指南以结构您的热修复：

通过 Capgo 的即时更新功能，您可以专注于修复错误，而不必担心打包不相关的更改。这一方法已经证明有效，如 Colenso 所示：

“We rolled out Capgo OTA 更新 in production for our user base of +5000. We’re seeing very smooth operation almost all our users are up to date within minutes of the OTA being deployed to @Capgo” [1].

我们的用户基数超过 5000。我们看到 OTA 部署后，几乎所有用户都在几分钟内更新到最新版本。@__CAPGO_KEEP_0__”

在您的设备上进行测试

• 彻底的测试至关重要，以确保热修复工作顺畅。使用以下步骤： 开发测试：
• 设备测试： 在各种设备和操作系统版本上检查修复。
• 集成测试： 确认修复不会干扰其他功能。

使用CI/CD工具尽可能地自动化测试过程。

“We practice agile development and @Capgo is mission-critical in delivering continuously to our users!” - Rodrigo Mantica [1]

我们实践敏捷开发，@Capgo 在持续为用户交付方面是 mission-critical！

一旦您的热修复通过了所有测试，您就准备好为部署设置__CAPGO_KEEP_0__。 Capgo

__CAPGO_KEEP_0__ 实时更新控制台界面

To get started with Capgo in your Capacitor project, use its CLI tool. Simply run the following command:

npx @capgo/cli init

这条命令为您做了繁重的工作：

• 安装 Capgo
• 自动配置您的项目
• 为您的项目准备Capgo服务

安装完成后，您可以继续配置您的项目，使用Capgo的加密和合规功能

设置您的项目

Capgo确保您的项目符合苹果和谷歌的加密和合规标准。它与CI/CD工具无缝集成，提供安全的更新加密，并符合应用商店的指南

这个设置已经被开发者验证过了。就像 Bessie Cooper 解释的那样：

“@Capgo 是开发者必备工具，希望提高生产力。避免 bugfix 的审查是黄金的。” [1]

对于更大的团队，Capgo 提供了多个组织设置和详细的权限管理等功能。它与平台如 GitHub, GitLab, Azure DevOps，和 Jenkins，使自动化部署流程变得简单。罗德里戈·曼蒂卡强调了其重要性：

“我们实行敏捷开发，@Capgo 在持续交付给用户方面是 mission-critical 的！” [1]

在项目设置完成后，您就可以上传修复程序并立即部署了。

步骤 3：上传修复程序

将文件发送到 @Capgo

在设置项目后，使用 @Capgo @CLI 工具上传修复程序。这样可以确保安全高效地传输更新。首先，按照开发过程中正常的方式构建您的应用程序。

这里是如何工作的：

• 使用标准流程构建您的应用。
• 确保所有文件都可以编译通过。
• 使用 Capgo CLI 工具上传您的更新。

标记更新

清晰的标签对于管理和跟踪热修复至关重要。当上传您的更新到 Capgo 时，请包括具体的版本细节和描述性标签。这有助于组织您的更新并让所有人保持一致。

马丁·多纳迪厄（Martin Donadieu），Capgo的创始人，设计了一种版本控制系统，它与CI/CD工作流程集成得非常顺畅。这一系统使得跟踪更新和回滚变得非常容易。

Capgo的 更新管理 还包括了功能如端到端加密和即时部署等，确保您的热修复是安全的，同时也能快速到达用户。

一旦您的热修复已上传并标记好，请转到步骤4来配置您的更新设置。

sbb-itb-f9944d2

Capgo Live Update System for Capacitor 应用

步骤 4：选择更新设置

上传热修复后，需要配置针对用户和定义滚动策略的设置。这确保了控制和有效的部署。

选择用户和设备

Capgo 的用户分配工具让您可以精确地确定谁应该接收热修复。有两种主要策略可供选择：

{"targetLanguage":"Simplified Chinese","protectedTokens":["Cloudflare","Capacitor","GitHub","Capgo","code","API","SDK","CLI","npm","bun"],"texts":["Private Testing","Beta testers, QA teams","Enables controlled testing with early feedback","Public Release","All users, staged rollouts","Allows broad distribution with gradual deployment","For example, if a bug affects users in a specific region, you can prioritize that group for quicker validation. After selecting your target audience, you can proceed to set detailed release rules.","Set Release Rules","Through __CAPGO_KEEP_0__’s web interface, you can fine-tune the release process by setting parameters like schedule, app version compatibility, and how gradually the update is rolled out.","Here are the key settings to configure:","Deployment Schedule","：选择更新发布的具体时间点。"]}

{"targetLanguage":"Simplified Chinese","protectedTokens":["Cloudflare","Capacitor","GitHub","Capgo","code","API","SDK","CLI","npm","bun"],"texts":["Private Testing","Beta testers, QA teams","Enables controlled testing with early feedback","Public Release","All users, staged rollouts","Allows broad distribution with gradual deployment","For example, if a bug affects users in a specific region, you can prioritize that group for quicker validation. After selecting your target audience, you can proceed to set detailed release rules.","Set Release Rules","Through __CAPGO_KEEP_0__’s web interface, you can fine-tune the release process by setting parameters like schedule, app version compatibility, and how gradually the update is rolled out.","Here are the key settings to configure:","Deployment Schedule","：选择更新发布的具体时间点。"]}

{"targetLanguage":"Simplified Chinese","protectedTokens":["Cloudflare","Capacitor","GitHub","Capgo","code","API","SDK","CLI","npm","bun"],"texts":["Private Testing","Beta testers, QA teams","Enables controlled testing with early feedback","Public Release","All users, staged rollouts","Allows broad distribution with gradual deployment","For example, if a bug affects users in a specific region, you can prioritize that group for quicker validation. After selecting your target audience, you can proceed to set detailed release rules.","Set Release Rules","Through Capgo’s web interface, you can fine-tune the release process by setting parameters like schedule, app version compatibility, and how gradually the update is rolled out.","Here are the key settings to configure:","Deployment Schedule","：选择更新发布的具体时间点。"]}

{"targetLanguage":"Simplified Chinese","protectedTokens":["Cloudflare","Capacitor","GitHub","Capgo","code","API","SDK","CLI","npm","bun"],"texts":["Private Testing","Beta testers, QA teams","Enables controlled testing with early feedback","Public Release","All users, staged rollouts","Allows broad distribution with gradual deployment","For example, if a bug affects users in a specific region, you can prioritize that group for quicker validation. After selecting your target audience, you can proceed to set detailed release rules.","Set Release Rules","Through __CAPGO_KEEP_0__’s web interface, you can fine-tune the release process by setting parameters like schedule, app version compatibility, and how gradually the update is rolled out.","Here are the key settings to configure:","Deployment Schedule","：选择更新发布的具体时间点。"]}

• {"targetLanguage":"Simplified Chinese","protectedTokens":["Cloudflare","Capacitor","GitHub","Capgo","code","API","SDK","CLI","npm","bun"],"texts":["Private Testing","Beta testers, QA teams","Enables controlled testing with early feedback","Public Release","All users, staged rollouts","Allows broad distribution with gradual deployment","For example, if a bug affects users in a specific region, you can prioritize that group for quicker validation. After selecting your target audience, you can proceed to set detailed release rules.","Set Release Rules","Through __CAPGO_KEEP_0__’s web interface, you can fine-tune the release process by setting parameters like schedule, app version compatibility, and how gradually the update is rolled out.","Here are the key settings to configure:","Deployment Schedule","：选择更新发布的具体时间点。"]}translations
• 版本要求: 定义哪些应用版本应该接收更新。
• 发布比例: 控制发布的速度，先从小规模开始逐渐扩大。

对于紧急修复，您可以立即部署以立即解决问题。对于较不重要的更新，分阶段发布允许您监控性能并在问题出现时解决潜在问题。另外，Capgo 提供了创建专门的测试组的选项，使协调更加顺畅和高效。

步骤 5：跟踪您的更新

密切关注您的热修复进度，并尽快解决任何问题。

检查更新状态

Capgo 的分析提供了关键更新指标的见解：

__CAPGO_KEEP_9__

__CAPGO_KEEP_10__

• __CAPGO_KEEP_11__
  If something goes wrong, Capgo’s rollback feature lets you instantly revert to the previous version.

• 分析用户分配
  查看更新如何分发以确定是否特定组或设备正在遇到问题。

• 监控性能
  使用实时指标来找出和解决问题。Capgo的工具可以帮助确定问题是否出在传输、安装或兼容性上。

罗德里戈·曼蒂卡（Rodrigo Mantica）是一位业务开发人员，他强调了Capgo的重要性：

“我们实行敏捷开发，并且@Capgo在持续交付给我们的用户方面是 mission-critical！” [1]

Capgo的Web界面使得监控更新进度变得容易，包括详细的日志和性能指标。其跟踪功能已经帮助组织提高发布效率达到了81% [1],确保应用程序性能稳定，同时快速解决任何问题。

概要

主要点

Capgo简化了快速有效地部署热修复的过程，具有可靠的交付记录。 947.6百万次更新 在 1,400个生产应用中 [1].

按照以下步骤将Capgo集成到您的工作流程中并优化您的更新过程

入门

在开始之前，请花点时间浏览上面的步骤。这些步骤将部署过程分解为可管理的动作，使其更容易实施。

启动您的Capgo集成，通过将CapgoCLI添加到您的项目中。使用 端到端加密，该平台每次都确保安全可靠的更新。

“Capgo是热code推送的聪明方式。”

为了更高效的效率，集成Capgo与您的CI/CD工具，如Azure DevOps、GitLab或GitHub。此设置使自动部署成为可能，同时您可以控制更新分发通过用户分配功能。

继续从5步部署热修复程序的Capgo

如果您正在使用 5步部署热修复程序的Capgo 来规划安全性和合规性，连接它与 加密 以获取加密的实施细节在加密中 合规性 关于 Compliance 的实现细节 Capgo 安全扫描器 关于 Capgo 安全扫描器 的产品工作流程 Capgo 安全 关于 Capgo 安全 的产品工作流程 Capgo 信任中心 关于 Capgo 信任中心 的产品工作流程