Edge Computing with Cloudflare Workers & Deno · 课时

Workers 中的环境变量与秘密信息

使用环境变量配置 Cloudflare Worker，并安全管理 API 密钥等秘密信息。

第 4 / 4 课13 个步骤

Workers 中的环境变量与秘密信息 是 CoddyKit 上的免费 Edge Computing with Cloudflare Workers & Deno 课时。这是第 4 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Edge Computing with Cloudflare Workers & Deno 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Edge Computing with Cloudflare Workers & Deno 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Why Configuration Matters

Hardcoding values like API keys into your Worker is insecure and inflexible. Environment variables and secrets keep config out of your code.

Vars vs Secrets

Workers distinguish two kinds:

Vars: plain text config, visible in dashboard
Secrets: encrypted, write-only values like keys and tokens

Defining Vars in wrangler

Plain variables go in your wrangler.toml under a [vars] table.

# wrangler.toml
[vars]
API_BASE = 'https://api.example.com'
ENVIRONMENT = 'production'

Accessing the env Binding

In the modules format, config arrives as the env argument of your fetch handler.

export default {
  async fetch(request, env, ctx) {
    return new Response('Base: ' + env.API_BASE);
  }
};

Adding a Secret

Secrets are never stored in your repo. Add them with the Wrangler CLI, which prompts for the value.

wrangler secret put MY_API_KEY

Using a Secret

Secrets appear on the same env object as vars, so reading them is identical.

const res = await fetch('https://api.example.com/data', {
  headers: { Authorization: 'Bearer ' + env.MY_API_KEY }
});

Listing & Deleting Secrets

Manage secrets entirely from the CLI. You can list names (never values) and delete ones you no longer need.

wrangler secret list
wrangler secret delete MY_API_KEY

Per-Environment Config

Use named environments to give staging and production different values.

# wrangler.toml
[env.staging.vars]
ENVIRONMENT = 'staging'

Local Development Secrets

For local wrangler dev, put secrets in a .dev.vars file and add it to .gitignore so they never reach version control.

# .dev.vars
MY_API_KEY=local-test-key

Security Best Practices

Keep config safe:

Never commit secrets
Rotate keys periodically
Use secrets, not vars, for anything sensitive

Putting It Together

A typical Worker reads a public base URL from vars and an auth token from a secret, then calls an upstream API safely.

export default {
  async fetch(req, env) {
    const r = await fetch(env.API_BASE + '/me', {
      headers: { Authorization: 'Bearer ' + env.MY_API_KEY }
    });
    return new Response(await r.text());
  }
};

Quick Check

Test your config knowledge.

在交互式课程中回答

Recap

You learned the difference between vars and secrets, how to define and access them via the env binding, manage them with Wrangler, and keep sensitive values secure across environments.

免费开始

用 AI 导师学习 Edge Computing with Cloudflare Workers & Deno — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 12
课程: 47

免费开始学习查看完整课程

常见问题解答

「Workers 中的环境变量与秘密信息」课时是免费的吗？

是的 — 「Workers 中的环境变量与秘密信息」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Edge Computing with Cloudflare Workers & Deno 课程的其余内容，请升级到 CoddyKit PRO。 Edge Computing with Cloudflare Workers & Deno 课程共包含 4 节课。

「Workers 中的环境变量与秘密信息」这节课中我会学到什么？

使用环境变量配置 Cloudflare Worker，并安全管理 API 密钥等秘密信息。你通过在浏览器中直接运行的动手代码来练习 Edge Computing with Cloudflare Workers & Deno，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Edge Computing with Cloudflare Workers & Deno 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Edge Computing with Cloudflare Workers & Deno 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 4 节课，共 4 节。

「Workers 中的环境变量与秘密信息」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Edge Computing with Cloudflare Workers & Deno 课中编写并运行代码吗？

能。每节 Edge Computing with Cloudflare Workers & Deno 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

设置 Worker 环境
处理 HTTP 请求
部署您的第一个 Worker
Workers 中的环境变量与秘密信息

← 返回 Edge Computing with Cloudflare Workers & Deno