[PR #31] feat(moemail-auto-deploy): 实现 Moemail 邮箱自动化部署 #77

New issue

Closed

opened 2026-02-26 12:17:55 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:17:55 +03:00

Owner

Original Pull Request: https://github.com/beilunyang/moemail/pull/31

State: closed
Merged: No

提供一个自动化部署Moemail的解决方案
新增工作流可构建发布 Moemail自动化部署执行文件
自动化部署菜单可选择
1.全流程部署
2.创建github app 获取
AUTH_GITHUB_ID
AUTH_GITHUB_SECRET
AUTH_SECRET
3.创建Cloudflare 的D1, KV,以及Page 获取
CLOUDFLARE_ACCOUNT_ID: Cloudflare 账户 ID
DATABASE_NAME: D1 数据库名称
DATABASE_ID: D1 数据库 ID
KV_NAMESPACE_ID: Cloudflare KV namespace ID，用于存储网站配置
CLOUDFLARE_API_TOKEN 仍需手动生成，并在.env文件内填写 CLOUDFLARE_API_TOKEN = xxxxx
4.自动fork 和填入 .env文件内的的变量并运行部署

**Original Pull Request:** https://github.com/beilunyang/moemail/pull/31 **State:** closed **Merged:** No --- - 提供一个自动化部署Moemail的解决方案 - 新增工作流可构建发布 Moemail自动化部署执行文件 - 自动化部署菜单可选择 - 1.全流程部署 - 2.创建github app 获取 - [ ] **AUTH_GITHUB_ID** - [ ] **AUTH_GITHUB_SECRET** - [ ] **AUTH_SECRET** - 3.创建Cloudflare 的D1, KV,以及Page 获取 - [ ] **CLOUDFLARE_ACCOUNT_ID**: Cloudflare 账户 ID - [ ] **DATABASE_NAME**: D1 数据库名称 - [ ] **DATABASE_ID**: D1 数据库 ID - [ ] **KV_NAMESPACE_ID**: Cloudflare KV namespace ID，用于存储网站配置 - **CLOUDFLARE_API_TOKEN** 仍需手动生成，并在.env文件内填写 CLOUDFLARE_API_TOKEN = xxxxx - 4.自动fork 和填入 .env文件内的的变量并运行部署

kerem

2026-02-26 12:17:55 +03:00

closed this issue
added the
pull-request
label

kerem changed title from ~~[PR #31] [CLOSED] feat(moemail-auto-deploy): 实现 Moemail 邮箱自动化部署~~ to [PR #31] feat(moemail-auto-deploy): 实现 Moemail 邮箱自动化部署

2026-02-27 12:33:43 +03:00

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/moemail#77

No description provided.

Rows
Columns