Skip to content
Back to search

maskin

AI run the shop. Humans set direction, agents execute.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 21 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/sindre-ai/maskin with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/sindre-ai/maskin'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sindre-ai--maskin/badge.svg)](/listings/sindre-ai--maskin)

HTML

<a href="/listings/sindre-ai--maskin"><img src="/api/listings/sindre-ai--maskin/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

πŸš€ Zero-click setup (from Claude Code)

Paste this single prompt into Claude Code (or any MCP-compatible agent) to have it bootstrap the whole thing for you:

Clone https://github.com/sindre-ai/maskin, cd into it, follow the "Onboarding a new user from Claude Code" section of CLAUDE.md, and hand off to the list_marketplace MCP tool.

Claude will clone, `pnpm install`, start the dev stack in the background, wait for the startup banner, wire the MCP server into your Claude Code config using the auto-provisioned API key + workspace, run `/reload-plugins` so the Maskin tools are immediately available in the same session, and then ask you which template to set up (development / growth / custom). From clone to a running pipeline in one message, no session restart.

Manual setup

# Clone and install
git clone https://github.com/sindre-ai/maskin.git && cd maskin
pnpm install

# Start everything (Docker + migrations + backend + frontend)
pnpm dev          # macOS / Linux
pnpm dev:win      # Windows (cmd / PowerShell)

`pnpm dev` boots PostgreSQL + SeaweedFS via Docker, runs migrations, then starts the backend (`http://localhost:3000`) and frontend (`http://localhost:5173`). When the backend prints its startup banner, pick one of the two paths below.

β‘  Get started from the browser

1. Open `http://localhost:5173` and create an account. 2. Create your first workspace from the UI. 3. (Optional) Connect MCP from **Settings β†’ MCP** later if you want agents to drive the workspace.

β‘‘ Get started from Claude Code (no UI)

On a fresh database, `pnpm dev` automatically creates a default actor + workspace and prints a ready-to-run `claude mcp add` command in the startup banner β€” including the API key. Two steps from there:

1. **Connect MCP** β€” copy the `claude mcp add maskin …` line from the dev banner and run it. (Disable this auto-bootstrap with `MASKIN_AUTO_BOOTSTRAP=false` if you want to create credentials yourself.)

2. **Configure the workspace.** In Claude Code, paste one of:

   Configure my Maskin workspace with the "development" template.
   Configure my Maskin workspace with the "growth" template.
   Configure my Maskin workspace with a custom template.

The first two apply pre-built templates (object types, statuses, custom fields, seed objects). The third walks you through a short questionnaire and tailors the workspace to whatever you're working on. Claude will ask a couple of light tailoring questions (workspace name, what you're building, near-term goal) β€” answer any, all, or none. Total time: under 3 minutes.

Rename the default actor and workspace whenever you're ready β€” from the UI (Settings β†’ Profile / Workspace) or via MCP (`update_actor`, `update_workspace`). Run `list_marketplace` again any time on a different workspace by passing `workspace_id`.

> Want demo data instead? Run `pnpm db:seed` for a pre-populated example workspace.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md Β· README Β· 383 lines
  1. # Maskin
  2. [![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
  3. [![CI](https://img.shields.io/github/actions/workflow/status/sindre-ai/maskin/ci.yml?label=CI)](https://github.com/sindre-ai/maskin/actions/workflows/ci.yml)
  4. [![GitHub Stars](https://img.shields.io/github/stars/sindre-ai/maskin?style=flat)](https://github.com/sindre-ai/maskin/stargazers)
  5. [![TypeScript](https://img.shields.io/badge/TypeScript-5.7+-blue.svg)](https://www.typescriptlang.org/)
  6. [![Node](https://img.shields.io/badge/Node-%3E%3D20-green.svg)](https://nodejs.org/)
  7. An open-source workspace where AI agents run product development autonomously. Humans set direction, agents execute.
  8. ## What is this?
  9. - **Open-source workspace** where AI agents run product development end-to-end
  10. - **Core pipeline:** Insights (signals from users, data, market) -> Bets (hypotheses to validate) -> Tasks (concrete work items) -> Feedback Loop
  11. - **Agents are first-class citizens** -- they create insights, propose bets, break down tasks, and execute. Humans course-correct
  12. - **Everything is an API** -- UI and agents use the same endpoints. No special agent interface, no separate human interface
  13. - **Unified object model** -- insights, bets, and tasks are all "objects" with the same schema, connected by relationships
  14. ## Prerequisites
  15. - **Node.js β‰₯ 20**
  16. - **pnpm 9.15.0** (`npm install -g pnpm@9.15.0`)
  17. - **Docker + Docker Compose** β€” must be installed and running. `pnpm dev` / `pnpm dev:win` boot PostgreSQL + SeaweedFS via `docker-compose`, so the app cannot start without Docker. Docker Desktop (macOS/Windows) bundles Compose; on Linux install `docker-compose-plugin`.
  18. ## Quick Start
  19. ### πŸš€ Zero-click setup (from Claude Code)
  20. Paste this single prompt into Claude Code (or any MCP-compatible agent) to have it bootstrap the whole thing for you:
  21. ```
  22. Clone https://github.com/sindre-ai/maskin, cd into it, follow the "Onboarding a new user from Claude Code" section of CLAUDE.md, and hand off to the list_marketplace MCP tool.
  23. ```
  24. Claude will clone, `pnpm install`, start the dev stack in the background, wait for the startup banner, wire the MCP server into your Claude Code config using the auto-provisioned API key + workspace, run `/reload-plugins` so the Maskin tools are immediately available in the same session, and then ask you which template to set up (development / growth / custom). From clone to a running pipeline in one message, no session restart.
  25. ### Manual setup
  26. ```bash
  27. # Clone and install
  28. git clone https://github.com/sindre-ai/maskin.git && cd maskin
  29. pnpm install
  30. # Start everything (Docker + migrations + backend + frontend)
  31. pnpm dev # macOS / Linux
  32. pnpm dev:win # Windows (cmd / PowerShell)
  33. ```
  34. `pnpm dev` boots PostgreSQL + SeaweedFS via Docker, runs migrations, then starts the backend (`http://localhost:3000`) and frontend (`http://localhost:5173`). When the backend prints its startup banner, pick one of the two paths below.
  35. ### β‘  Get started from the browser
  36. 1. Open `http://localhost:5173` and create an account.
  37. 2. Create your first workspace from the UI.
  38. 3. (Optional) Connect MCP from **Settings β†’ MCP** later if you want agents to drive the workspace.
  39. ### β‘‘ Get started from Claude Code (no UI)
  40. On a fresh database, `pnpm dev` automatically creates a default actor + workspace and prints a ready-to-run `claude mcp add` command in the startup banner β€” including the API key. Two steps from there:
  41. 1. **Connect MCP** β€” copy the `claude mcp add maskin …` line from the dev banner and run it. (Disable this auto-bootstrap with `MASKIN_AUTO_BOOTSTRAP=false` if you want to create credentials yourself.)
  42. 2. **Configure the workspace.** In Claude Code, paste one of:
  43. ```
  44. Configure my Maskin workspace with the "development" template.
  45. ```
  46. ```
  47. Configure my Maskin workspace with the "growth" template.
  48. ```
  49. ```
  50. Configure my Maskin workspace with a custom template.
  51. ```
  52. The first two apply pre-built templates (object types, statuses, custom fields, seed objects). The third walks you through a short questionnaire and tailors the workspace to whatever you're working on. Claude will ask a couple of light tailoring questions (workspace name, what you're building, near-term goal) β€” answer any, all, or none. Total time: under 3 minutes.
  53. Rename the default actor and workspace whenever you're ready β€” from the UI (Settings β†’ Profile / Workspace) or via MCP (`update_actor`, `update_workspace`). Run `list_marketplace` again any time on a different workspace by passing `workspace_id`.
  54. > Want demo data instead? Run `pnpm db:seed` for a pre-populated example workspace.
  55. ## Architecture
  56. ```
  57. maskin/
  58. β”œβ”€β”€ apps/
  59. β”‚ β”œβ”€β”€ dev/ # Backend API server (Hono.js)
  60. β”‚ β”‚ β”œβ”€β”€ src/
  61. β”‚ β”‚ β”‚ β”œβ”€β”€ index.ts # App entry, middleware, route mounting
  62. β”‚ β”‚ β”‚ β”œβ”€β”€ routes/ # REST endpoints
  63. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ objects.ts
  64. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ actors.ts
  65. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ workspaces.ts
  66. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ relationships.ts
  67. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ triggers.ts
  68. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ events.ts
  69. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ sessions.ts
  70. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ integrations.ts
  71. β”‚ β”‚ β”‚ β”‚ └── graph.ts
  72. β”‚ β”‚ β”‚ β”œβ”€β”€ services/
  73. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ trigger-runner.ts # Cron + event-based automation
  74. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ session-manager.ts # Container-based agent sessions
  75. β”‚ β”‚ β”‚ β”‚ β”œβ”€β”€ container-manager.ts # Docker container lifecycle
  76. β”‚ β”‚ β”‚ β”‚ └── agent-storage.ts # S3 agent file pull/push
  77. β”‚ β”‚ β”‚ └── lib/
  78. β”‚ β”‚ β”‚ └── llm/ # LLM provider adapters
  79. β”‚ β”‚ β”‚ β”œβ”€β”€ openai.ts
  80. β”‚ β”‚ β”‚ └── anthropic.ts
  81. β”‚ β”‚ └── Dockerfile
  82. β”‚ β”œβ”€β”€ web/ # Frontend (React + TanStack)
  83. β”‚ β”‚ └── src/
  84. β”‚ β”‚ β”œβ”€β”€ routes/ # File-based routing (TanStack Router)
  85. β”‚ β”‚ β”œβ”€β”€ components/ # UI primitives, shared, and feature components
  86. β”‚ β”‚ β”œβ”€β”€ hooks/ # TanStack Query hooks per resource
  87. β”‚ β”‚ └── lib/ # API client, auth, SSE, utilities
  88. β”‚ └── e2e/ # E2E tests (Playwright)
  89. β”‚ └── src/
  90. β”‚ β”œβ”€β”€ tests/ # Test specs (auth, CRUD, navigation)
  91. β”‚ β”œβ”€β”€ fixtures/ # Auth fixtures
  92. β”‚ └── helpers/ # API test helpers
  93. β”œβ”€β”€ scripts/
  94. β”‚ β”œβ”€β”€ dev.sh # Dev startup script (bash/macOS/Linux)
  95. β”‚ β”œβ”€β”€ dev.mjs # Dev startup script (Windows cmd/PowerShell)
  96. β”‚ └── openrouter-conformance.mjs # Tool-use + reply-language check of a model on the funded OpenRouter route (spends credit; see header)
  97. β”œβ”€β”€ packages/
  98. β”‚ β”œβ”€β”€ db/ # Drizzle ORM schema + migrations
  99. β”‚ β”œβ”€β”€ auth/ # API key auth (keys stored as issued; hashing planned)
  100. β”‚ β”œβ”€β”€ shared/ # Zod schemas for validation
  101. β”‚ β”œβ”€β”€ realtime/ # PG NOTIFY -> SSE bridge
  102. β”‚ β”œβ”€β”€ storage/ # Abstract StorageProvider with S3 implementation
  103. β”‚ └── mcp/ # MCP server (39 tools, stdio + HTTP transport)
  104. β”œβ”€β”€ docker-compose.yml
  105. β”œβ”€β”€ turbo.json
  106. └── package.json
  107. ```
  108. **Key design decisions:**
  109. - **Modular monorepo** -- pnpm workspaces + Turborepo for builds. Each package is independently importable
  110. - **Event-sourced activity** -- every mutation logs an event. Agents and humans see the same audit trail
  111. - **Container-based agent execution** -- Docker container sessions (SessionManager) for running Claude Code, Codex, or custom CLIs
  112. ## Tech Stack
  113. | Layer | Choice | Why |
  114. |-------|--------|-----|
  115. | Runtime | Node.js >= 20 | Native fetch, stable ESM |
  116. | Language | TypeScript 5.7+ | Type safety across monorepo |
  117. | API Framework | Hono.js + OpenAPIHono | Fast, lightweight, edge-ready |
  118. | ORM | Drizzle ORM | Type-safe SQL, zero overhead |
  119. | Database | PostgreSQL 16 | JSONB for metadata, NOTIFY for real-time |
  120. | Validation | Zod | Shared schemas between API, frontend, and MCP |
  121. | Auth | API keys (stored as issued, hashing planned) | Simple, agent-friendly. No cookies or sessions |
  122. | Real-time | PG NOTIFY -> SSE | No extra infra (no Redis, no WebSocket server) |
  123. | Agent Protocol | MCP (Model Context Protocol) | Standard protocol for external AI agents |
  124. | Frontend | React 19 + TanStack Router + TanStack Query | File-based routing, server state caching |
  125. | Styling | Tailwind CSS 4 + shadcn/ui | Utility-first CSS with Radix UI primitives |
  126. | Object Storage | S3-compatible (SeaweedFS for dev) | Agent file persistence (skills, learnings, memory) |
  127. | Containers | Docker + dockerode | Ephemeral agent execution environments |
  128. | Build | Turborepo | Parallel builds, dependency-aware caching |
  129. | Linting | Biome | Fast, replaces ESLint + Prettier |
  130. ## Data Model
  131. All product work is represented as **unified objects** -- insights, bets, and tasks share the same table with a `type` discriminator. This keeps the schema flat and lets agents reason across object types uniformly.
  132. ### Tables
  133. | Table | Purpose |
  134. |-------|---------|
  135. | **actors** | Humans and AI agents. Both are first-class. Stores type, name, API key (stored as issued, hashing planned), system prompt, LLM config, and memory |
  136. | **workspaces** | Isolated environments. Each workspace has its own settings including valid statuses per object type |
  137. | **workspace_members** | Many-to-many join between actors and workspaces with roles (owner, member) |
  138. | **objects** | The core table. Every insight, bet, and task is an object with: type, title, content, status, metadata (JSONB), and owner |
  139. | **relationships** | Typed edges between objects: `informs`, `breaks_into`, `blocks`, `relates_to`, `duplicates` |
  140. | **events** | Append-only activity log. Every mutation is recorded with actor, action, entity reference, and data payload |
  141. | **triggers** | Automation rules. Either cron-based or event-based. Each trigger targets an actor and includes an action prompt |
  142. | **integrations** | External service connections per workspace (OAuth-based) |
  143. | **sessions** | Container-based agent execution sessions. Tracks lifecycle: pending -> running -> completed/paused/failed/timeout |
  144. | **session_logs** | Append-only log output from container sessions (stdout/stderr/system), used for SSE streaming |
  145. | **agent_files** | Metadata index for agent files stored in S3 (skills, learnings, memory) |
  146. ## API Endpoints
  147. All endpoints are under `/api`. Most require `Authorization: Bearer <api-key>` and `X-Workspace-Id` headers.
  148. ### Health and Metadata
  149. | Method | Path | Description |
  150. |--------|------|-------------|
  151. | GET | `/api/health` | Liveness check (no auth, no database) |
  152. | GET | `/api/health/db` | Database readiness check (no auth) |
  153. | GET | `/api/openapi.json` | OpenAPI spec (no auth) |
  154. ### Objects (Insights, Bets, Tasks)
  155. | Method | Path | Description |
  156. |--------|------|-------------|
  157. | POST | `/api/objects` | Create an object |
  158. | GET | `/api/objects` | List objects (filter by type, status, owner) |
  159. | GET | `/api/objects/search` | Search objects by text in title/content |
  160. | GET | `/api/objects/:id` | Get object by ID |
  161. | GET | `/api/objects/:id/graph` | Get object with all relationships and connected objects |
  162. | PATCH | `/api/objects/:id` | Update object (title, content, status, metadata) |
  163. | DELETE | `/api/objects/:id` | Delete object |
  164. ### Actors
  165. | Method | Path | Description |
  166. |--------|------|-------------|
  167. | POST | `/api/actors` | Create actor and get API key (no auth for humans; an agent needs the caller's API key and a workspace_id the caller belongs to) |
  168. | GET | `/api/actors` | List actors (optionally filtered by workspace) |
  169. | GET | `/api/actors/:id` | Get actor details |
  170. | PATCH | `/api/actors/:id` | Update actor |
  171. | POST | `/api/actors/:id/api-keys` | Regenerate API key |
  172. ### Workspaces
  173. | Method | Path | Description |
  174. |--------|------|-------------|
  175. | POST | `/api/workspaces` | Create workspace |
  176. | GET | `/api/workspaces` | List workspaces for current actor |
  177. | PATCH | `/api/workspaces/:id` | Update workspace (name, settings) |
  178. | POST | `/api/workspaces/:id/members` | Add member to workspace |
  179. | GET | `/api/workspaces/:id/members` | List workspace members |
  180. ### Relationships
  181. | Method | Path | Description |
  182. |--------|------|-------------|
  183. | POST | `/api/relationships` | Create relationship between objects |
  184. | GET | `/api/relationships` | List relationships (filter by source, target, type) |
  185. | DELETE | `/api/relationships/:id` | Delete relationship |
  186. ### Triggers
  187. | Method | Path | Description |
  188. |--------|------|-------------|
  189. | POST | `/api/triggers` | Create automation trigger |
  190. | GET | `/api/triggers` | List triggers in workspace |
  191. | PATCH | `/api/triggers/:id` | Update trigger |
  192. | DELETE | `/api/triggers/:id` | Delete trigger |
  193. ### Events
  194. | Method | Path | Description |
  195. |--------|------|-------------|
  196. | GET | `/api/events` | SSE stream of real-time events (supports `Last-Event-ID` for replay) |
  197. | GET | `/api/events/history` | Paginated event history (filter by entity_type, action, since) |
  198. ### Sessions (Container-based Agent Execution)
  199. | Method | Path | Description |
  200. |--------|------|-------------|
  201. | POST | `/api/sessions` | Create a container session |
  202. | GET | `/api/sessions` | List sessions |
  203. | GET | `/api/sessions/:id` | Get session details |
  204. | POST | `/api/sessions/:id/stop` | Stop a running session |
  205. | POST | `/api/sessions/:id/pause` | Pause and snapshot a session |
  206. | POST | `/api/sessions/:id/resume` | Resume a paused session |
  207. | GET | `/api/sessions/:id/logs` | Paginated log history |
  208. | GET | `/api/sessions/:id/logs/stream` | SSE stream of live logs |
  209. ### Graph (Batch Operations)
  210. | Method | Path | Description |
  211. |--------|------|-------------|
  212. | POST | `/api/graph` | Atomic batch create (objects + relationships in one transaction) |
  213. ### Integrations
  214. | Method | Path | Description |
  215. |--------|------|-------------|
  216. | GET | `/api/integrations` | List integrations for workspace |
  217. | GET | `/api/integrations/providers` | List available providers |
  218. | POST | `/api/integrations/:provider/connect` | Start OAuth/connection flow |
  219. | GET | `/api/integrations/:provider/callback` | OAuth callback (no auth) |
  220. | DELETE | `/api/integrations/:id` | Disconnect integration |
  221. ### Webhooks
  222. | Method | Path | Description |
  223. |--------|------|-------------|
  224. | POST | `/api/webhooks/:provider` | Incoming webhook handler (no auth) |
  225. ### MCP HTTP Transport
  226. | Method | Path | Description |
  227. |--------|------|-------------|
  228. | POST | `/mcp` | Streamable HTTP transport for MCP clients |
  229. ## Agent System
  230. Agents run as container sessions β€” ephemeral Docker containers running CLI agents (Claude Code, Codex, custom CLIs).
  231. - **Triggered by events or cron** -- the TriggerRunner watches for matching events or schedules and spawns container sessions
  232. - **All actions logged as events** -- every agent action appears in the event stream, attributed to the agent actor
  233. - **Configurable per agent** -- each agent has its own system prompt, tools list, and persistent memory
  234. - **Full lifecycle management** -- create, run, stop, pause (snapshot), resume
  235. - **Live log streaming** -- stdout/stderr streamed via SSE in real-time
  236. - **Persistent agent files** -- skills, learnings, and memory stored in S3-compatible storage, pulled into containers on start and pushed back on completion
  237. - **Configurable** -- custom images, environment variables, timeouts, working directories
  238. ### External Agents (MCP)
  239. External agents connect via the Model Context Protocol (39 tools available), supporting both stdio and HTTP transport.
  240. - **Full workspace access** -- CRUD for objects, relationships, actors, workspaces, triggers, sessions, integrations
  241. - **Works with any MCP-compatible client** -- Claude Code, Claude Desktop, OpenAI agents, custom implementations
  242. - **Authenticated via API key** -- same auth as any other actor
  243. ## MCP Reference
  244. Maskin exposes 73 MCP tools over both stdio and HTTP. See **Quick Start β†’ Get started from Claude Code** above for the one-command setup. Other clients (Claude Desktop, OpenAI agents, custom implementations) use the same env vars (`API_BASE_URL`, `API_KEY`, `WORKSPACE_ID`) β€” point them at `pnpm --filter @maskin/mcp start` for stdio, or `POST http://localhost:3000/mcp` for HTTP.
  245. The first tool a new agent should call is `list_marketplace` β€” it lists the available marketplace loops, and `install_loop` installs the one the user picks.
  246. ## Docker
  247. ```bash
  248. # Full stack (PostgreSQL + SeaweedFS + dev server)
  249. docker-compose up
  250. # Just the database and storage
  251. docker-compose up postgres seaweedfs -d
  252. ```
  253. The dev server container runs migrations on startup and serves at `http://localhost:3000`.
  254. ## Development
  255. ```bash
  256. # Start everything (Docker + migrations + dev servers)
  257. pnpm dev
  258. # On Windows (cmd/PowerShell):
  259. pnpm dev:win
  260. # Build all packages
  261. pnpm build
  262. # Run tests
  263. pnpm test
  264. # Run E2E tests (requires running dev server)
  265. pnpm test:e2e
  266. # Lint (Biome)
  267. pnpm lint
  268. # Lint and auto-fix
  269. pnpm lint:fix
  270. # Format
  271. pnpm format
  272. # Type checking
  273. pnpm type-check
  274. # Database: generate migration from schema changes
  275. pnpm db:generate
  276. # Database: run pending migrations (automatically run by pnpm dev)
  277. pnpm db:migrate
  278. # Database: seed demo data
  279. pnpm db:seed
  280. ```
  281. ### Environment Variables
  282. | Variable | Required | Default | Description |
  283. |----------|----------|---------|-------------|
  284. | `DATABASE_URL` | Yes | -- | PostgreSQL connection string |
  285. | `PORT` | No | `3000` | Server port |
  286. | `S3_ENDPOINT` | No | `http://localhost:8333` | S3-compatible storage endpoint (SeaweedFS for dev) |
  287. | `S3_BUCKET` | No | `agent-files` | Storage bucket name |
  288. | `S3_ACCESS_KEY` | No | `admin` | S3 access key |
  289. | `S3_SECRET_KEY` | No | `admin` | S3 secret key |
  290. | `S3_REGION` | No | `us-east-1` | S3 region |
  291. | `S3_PUBLIC_ENDPOINT` | No | `S3_ENDPOINT` | Address browsers use to reach storage for presigned uploads/downloads of large files. Set it when `S3_ENDPOINT` is an internal host. The bucket needs CORS: see `docs/runbooks/large-file-uploads.md` |
  292. ## License
  293. Apache 2.0 β€” see [LICENSE](LICENSE) for details.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.