-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdo-app.yaml
More file actions
53 lines (52 loc) · 2.36 KB
/
Copy pathdo-app.yaml
File metadata and controls
53 lines (52 loc) · 2.36 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
47
48
49
50
51
52
53
# DigitalOcean App Platform spec for the Pinner MCP server — CORRECTED to deploy from GHCR.
#
# NOTE: App Platform containers have NO persistent local storage and DO NOT support
# volumes. The original `mount:` block was invalid/unsupported and has been removed.
# For persistence use DO Spaces (object storage) or a DO Managed Database instead.
# Apply with: doctl apps create --spec do-app.yaml (or paste in DO dashboard > Create App > Container image).
name: pinner
services:
- name: pinner
image:
# Valid registry_type values: DOCR | DOCKER_HUB | GHCR (NOT "OTHER").
registry_type: GHCR
# For GHCR, "registry" is the GitHub org/owner of the image, NOT the host "ghcr.io".
registry: lumeweb
# The image repository name under that org (ghcr.io/lumeweb/pinner).
repository: pinner
tag: latest
http_port: 8080
instance_count: 1
instance_size_slug: basic-xxs
health_check:
http_path: /healthz
initial_delay_seconds: 15
period_seconds: 30
timeout_seconds: 5
success_threshold: 1
failure_threshold: 3
envs:
# MCP_AUTH_TOKEN is intentionally NOT declared here. An empty value is
# treated by the runtime as "no secret configured" and leaves the public
# /mcp endpoint unauthenticated; a committed placeholder is worse. App
# Platform cannot render a real secret from a committed spec, so set a
# non-empty value in the DO dashboard (App > Settings > Env Vars) BEFORE
# the first deploy, e.g. $(openssl rand -base64 32) — otherwise the
# endpoint executes catalog tools with no authentication.
- key: MCP_OAUTH
# OAuth stays OFF (0) because the app-spec cannot render a real token.
# The runtime hard-fails with "--oauth requires --auth-token" when an
# empty token is combined with MCP_OAUTH=1, so the deploy would serve
# nothing. After setting a real MCP_AUTH_TOKEN in the DO dashboard,
# flip this to "1" to enable OAuth-aware clients.
value: "0"
type: GENERAL
- key: MCP_CORS
value: "1"
type: GENERAL
- key: PINNER_HOME
value: /data
type: GENERAL
# REMOVED: `mount:` is NOT a valid app-spec key and App Platform does not support
# volumes (ephemeral local filesystem only, capped at 4 GiB). Use Spaces / Managed DB
# for any persistent data.