-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy paths.yaml
More file actions
46 lines (45 loc) · 1.92 KB
/
Copy paths.yaml
File metadata and controls
46 lines (45 loc) · 1.92 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
# Serverless Devs manifest, Alibaba Cloud Function Compute 3.0 (fc3 component).
# Deploys the Continuum backend as a custom-container web function.
# Schema verified against docs.serverless-devs.com/user-guide/aliyun/fc3/spec (2026).
#
# Before deploy:
# 1. s config add # store your AccessKey (your step; see docs/deploy.md)
# 2. export DASHSCOPE_API_KEY=sk-... (or put it in a .env file next to this)
# 3. set `image` below to your ACR repository address
# 4. s deploy # builds + pushes the image, then creates the function
edition: 3.0.0
name: continuum
access: default
resources:
continuum:
component: fc3
props:
# Singapore region matches the international DashScope endpoints the app calls.
region: ap-southeast-1
functionName: continuum
runtime: custom-container
customContainerConfig:
# e.g. registry.ap-southeast-1.aliyuncs.com/<namespace>/continuum:latest
image: <your-acr-namespace>/continuum:latest
port: 9000
cpu: 1
diskSize: 10240 # 10 GB scratch for clips downloaded from Wan before the cut
memorySize: 2048
timeout: 600
internetAccess: true # needed to reach DashScope / Wan
instanceConcurrency: 5
environmentVariables:
# Never hardcode the key here; it is read from the environment / .env at deploy.
DASHSCOPE_API_KEY: ${env('DASHSCOPE_API_KEY')}
DASHSCOPE_BASE_URL_OPENAI: https://dashscope-intl.aliyuncs.com/compatible-mode/v1
DASHSCOPE_HTTP_BASE: https://dashscope-intl.aliyuncs.com/api/v1
CONTINUUM_DATA_DIR: /tmp/continuum # writable scratch in the container
triggers:
- triggerName: httpTrigger
triggerType: http
triggerConfig:
authType: anonymous # public demo URL; tighten to `function` for private
disableURLInternet: false
methods:
- GET
- POST