fc-python-website

Files (2)

• .bundled-hash
• SKILL.md

SKILL.md (first lines)

# Deploy a Python App on Function-Compute / 在函数计算上部署 Python 应用

## AutoClaw managed-delivery boundary (highest priority) / 受控交付边界（最高优先级）

When `website_delivery_start` or `AUTOCLAW_FUNCTION_COMPUTE_WEBSITE_PROTOCOL`
is active, **do not call `/functionCompute`, read/request/store/output a JWT, or
execute this Skill's curl commands.** API sections are reference-only. Build,
package, and verify the artifact locally; AutoClaw Main owns create/upload, and
the human owns publication. The current managed automatic-preview path supports
nginx only, so do not add an nginx `autoPreview` marker for a Python package.

当 `website_delivery_start` 或 `AUTOCLAW_FUNCTION_COMPUTE_WEBSITE_PROTOCOL`
生效时，**禁止调用 `/functionCompute`、读取/索取/保存/输出 JWT，禁止执行本 Skill 的 curl。**
API 章节仅作参考；Agent 只负责本地构建、打包与验证，创建和上传由 AutoClaw Main 负责，
正式发布由用户负责。当前自动预览仅支持 nginx，Python 产物不得写 nginx `autoPreview` 标记。

## Standalone API reference (not managed delivery) / 独立 API 参考（不适用于受控交付）

1. Write `index.py` exporting `def handler(event, context)` that returns
   `{"statusCode", "headers", "body"}`.
2. Zip it with `index.py` **at the root** of the archive.
3. `POST /functionCompute/functions` with `{"environment":"python","name":"..."}` → get `id`.
4. `POST /functionCompute/functions/{id}/code` with `{"zip_base64":"<base64>"}` → your code is now live at **`preview_url`**.
5. Verify on `preview_url`. **You (the Agent) stop here.** The human clicks **Publish** in the UI to promote it to `stable_url`.

中文速览：

1. 编写 `index.py`，导出 `def handler(event, context)`，返回 `{"statusCode","headers","body"}`。
2. 打成 zip，`index.py` 必须在压缩包**根目录**。
3. `POST /functionCompute/functions`，body 为 `{"environment":"python","name":"..."}`，拿到 `id`。
4. `POST /functionCompute/functions/{id}/code`，body 为 `{"zip_base64":"<base64>"}`，代码即刻在 **`preview_url`** 可见。
5. 在 `preview_url` 自测。**Agent 到此为止**，由人工在 UI 点击 **Publish**，才会推送到 `stable_url`。

---

## 1. The Python environment / Python 运行环境

**English.** The `python` environment maps to the Aliyun Function Compute 3.0
**built-in runtime `python3.12`**. It uses FC's built-in HTTP handler: FC
receives the HTTP request, invokes your `handler`, and turns the returned dict
into the HTTP response. You do **not** open a socket or bind a port yourself —
that is only for custom runtimes (nginx / next.js). Your uploaded code is
extracted to **`/code`** inside the instance; `/code` is the working directory
and is on the import path.

Fixed resource preset (from the repo, do not assume you can change these):

| Property | Value |
|---|---|
| Runtime | `python3.12` |
| Handler | `index.handler` (file `index.py`, function `handler`) |
| CPU | 0.35 vCPU |
| Memory | 512 MB |
| Disk | 512 MB |
| Timeout | 60 s per request |
| Instance concurrency | 1 |
| Code location | extracted to `/code` |
| Max upload zip | 50 MB (base64 body) |

**中文。** `python` 环境对应阿里云函数计算 3.0 的**内置运行时 `python3.12`**，
使用 FC 内置 HTTP 处理器：FC 接收 HTTP 请求，调用你的 `handler`，并把返回的
字典转换成 HTTP 响应。你**不需要**自己监听端口或开 socket（那是 nginx /
next.js 等自定义运行时才做的）。上传的代码会解压到实例内的 **`/code`**，
`/code` 即工作目录，也在模块导入路径上。

资源规格是固定的（来自仓库预设，不要假设可以修改）：运行时 `python3.12`、
处理器 `index.handler`、CPU 0.35 核、内存 512 MB、磁盘 512 MB、单次请求
超时 60 秒、单实例并发 1、代码解压到 `/code`、上传 zip 上限 50 MB。

### Constraints to respect / 需要遵守的约束

- **Handler name is fixed.** It must be `index.handler` → file `index.py`, function `handler`. Do not rename.
- **Return a dict**, not a string. Keys: `statusCode` (int), `headers` (dict), `body` (str). Missing `statusCode` will error.
- **Requests over 60 s are killed.** Keep handlers fast; do not run long background loops.
- **512 MB memory / disk.** Vendor only the wheels you need. Large ML models will not fit.
- **Instance concurrency is 1** — one request per instance at a time; FC scales out with more instances.
- 处理器名称固定为 `index.handler`；必须返回字典（含 `statusCode`）；单次请求超过 60 秒会被终止；内存/磁盘各 512 MB；单实例并发为 1。

---

## 2. File-structure contract / 文件结构约定

The zip you upload must have `index.py` **at the top level** (not inside a
subfolder). Third-party packages must be vendored **beside** `index.py`
(install with `pip install -t .`), because there is no build step on upload.

```
mysite.zip
├── index.py          # REQUIRED, at root, defines handler(event, context)
├── requirements deps # optional: vendored packages next to index.py
│   └── ... (e.g. jinja2/, markupsafe/)
└── static/           # optional: your own assets you read from /code/static
```

上传的 zip 必须把 `index.py` 放在**最顶层**（不能在子目录里）。第三方依赖要
用 `pip install -t .` 装到 `index.py` **同级**目录，因为上传时没有构建步骤。

---

## 3. Minimal working example / 最小可运行示例

This is the exact starter that ships with the environment. Copy it verbatim as
`index.py` and it will serve HTML immediately.

```python
# index.py
def handler(event, context):
    return {
        "statusCode": 200,
        "headers": {"content-type": "text/html"},
        "body": "<html><body><h1>Hello from Function Compute (Python)</h1></body></html>",
    }
```

### Reading the request / 读取请求

For the built-in HTTP handler, `event` arrives as **raw `bytes`** — a
JSON-encoded description of the HTTP request. You **must** `json.loads(event)`
to get a dict; there is no pre-parsed dict handed to you. The parsed object has

From Reyvic925/tradingwebsite, MIT.

More from Reyvic925/tradingwebsite