스킬 prisma-compute
📦

prisma-compute

v1.4.1 콘텐츠 리비전 r2 높은 위험 🌐 네트워크 접근🔑 환경 변수📁 파일 시스템 접근⚙️ 외부 명령어

Prisma Compute 앱을 안전하게 배포하기

Prisma Compute를 배포하려면 올바른 구성, 인증, 환경 설정 및 런타임 포트가 필요합니다. 이 스킬은 지원되는 TypeScript 프레임워크의 설정, 배포, 검증 및 문제 해결 과정을 안내합니다.

지원: Claude Codex Code(CC)
Maintain this Skill? Claim it ⚠️ 38 나쁨

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청
Review the Skillstore skill "prisma-compute" from https://skillstore.io/skills/prisma-prisma-compute.md and its manifest at https://skillstore.io/api/skills/prisma-prisma-compute/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/prisma-prisma-compute.md 서명된 manifest GET /api/skills/prisma-prisma-compute/manifest 서명된 lockfile GET /api/skills/prisma-prisma-compute/lockfile

테스트해 보기

"prisma-compute" 사용 중입니다. 배포 전에 내 Next.js 앱을 검토해 주세요.

예상 결과:

  • 프레임워크: 독립 실행형 서버 출력이 필요한 Next.js.
  • 런타임: 배포 포트와 모든 인터페이스에 바인딩해야 합니다.
  • 다음 단계: 생성된 배포 스크립트와 구성을 확인합니다.

"prisma-compute" 사용 중입니다. 내 프리뷰 배포에서 데이터베이스에 연결할 수 없습니다.

예상 결과:

  • 브랜치 이름이 브랜치 환경 범위와 일치하는지 확인합니다.
  • 플레이스홀더가 아닌 데이터베이스 URL을 배포 환경에서 사용할 수 있는지 확인합니다.
  • 환경 구성을 확인한 후 런타임 로그를 사용합니다.

"prisma-compute" 사용 중입니다. Prisma 워크스페이스가 여러 개 있습니다.

예상 결과:

  • 프로젝트 또는 앱 상태를 변경하기 전에 활성 워크스페이스를 확인합니다.
  • 비대화형 작업에는 워크스페이스 식별자를 명시적으로 선택합니다.
  • 서비스 토큰이나 로컬 자격 증명 파일을 표시하지 않습니다.

보안 감사

높은 위험
v7 • 2026. 7. 23. 버전별 보고서 열기

No prompt injection or malicious collection endpoint was found; most static matches are Markdown or deployment documentation. The skill still handles secret-bearing environment files, executes mutable package versions, and documents non-interactive production mutations.

7
스캔된 파일
1,901
분석된 줄 수
16
검토 항목
0
오탐 무시됨

확인된 보안 우려 사항 (43)

높음
references/app-deploy-cli.md:148
Environment file access
bunx @prisma/cli@latest project env add --file .env --role production
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:149
Environment file access
bunx @prisma/cli@latest project env add --file .env.preview --role preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:151
Environment file access
bunx @prisma/cli@latest project env update --file .env --role production
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:157
Environment file access
`app deploy --env .env` loads environment variables from a file for the deployment. A config-backed
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:247
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:263
Environment file access
--env .env.preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:281
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:292
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
확인된 43건 모두 보기
높음
references/app-deploy-cli.md:303
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:317
Environment file access
--env .env.preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:329
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/app-deploy-cli.md:337
Environment file access
bunx @prisma/cli@latest app deploy api --prod --yes --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/compute-config.md:47
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/compute-config.md:83
Environment file access
file: [".env", ".env.production"],
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/compute-config.md:141
Environment file access
env: "apps/web/.env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/compute-config.md:149
Environment file access
file: "apps/api/.env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/compute-config.md:83
Environment variant files
file: [".env", ".env.production"],
The configuration explicitly loads .env and .env.production files. These variants commonly contain deployment secrets and therefore require deliberate scope and repository controls.
높음
references/create-prisma.md:65
Environment file access
- a `.env` file containing `DATABASE_URL`
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/create-prisma.md:66
Environment file access
- an initial Compute deployment with env vars loaded from `.env`
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:80
Environment file access
bunx @prisma/cli@latest app deploy --framework nextjs --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:107
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:118
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:144
Environment file access
bunx @prisma/cli@latest app deploy --framework nestjs --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:153
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:178
Environment file access
bunx @prisma/cli@latest app deploy --framework tanstack-start --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:222
Environment file access
bunx @prisma/cli@latest app deploy --framework nuxt --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:231
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:243
Environment file access
bunx @prisma/cli@latest app deploy --framework astro --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:253
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:280
Environment file access
--env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:313
Environment file access
env: ".env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:359
Environment file access
env: "packages/db/.env",
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/frameworks.md:379
Environment file access
--env packages/db/.env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/sdk-api.md:126
Environment file access
bunx @prisma/cli@latest project env add --file .env.preview --branch feature/foo
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/troubleshooting.md:22
Environment file access
test -f .env && sed -n 's/=.*/=<redacted>/p' .env
The command reads a local .env file and prints variable names while redacting values. Redaction reduces exposure, but access to a secret-bearing file is real.
높음
references/troubleshooting.md:153
Environment file access
bunx @prisma/cli@latest app deploy --json --no-interactive --prod --yes --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/troubleshooting.md:197
Environment file access
1. Put a real production-ready `DATABASE_URL` in `.env` or project env.
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/troubleshooting.md:200
Environment file access
4. Redeploy with `--env .env` or project env configured.
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/troubleshooting.md:389
Environment file access
bunx @prisma/cli@latest app deploy --prod --yes --env .env
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
references/troubleshooting.md:390
Environment file access
bunx @prisma/cli@latest app deploy --branch feature/foo --env .env.preview
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
SKILL.md:148
Environment file access
- `env-deploy-loads-dotenv` - Generated deploy scripts may load env via `prisma.compute.ts` or `--en
The guidance configures a local .env file as deployment input, causing secret-bearing values to be read and potentially uploaded to Prisma Compute. This is intended but security-sensitive behavior.
높음
SKILL.md:18-25references/create-prisma.md:11-16
Unpinned Remote Package Execution
Commands repeatedly execute @prisma/cli@latest and create-prisma@latest through package runners. A compromised or unexpectedly changed release would execute with the agent's local privileges.
The cited commands explicitly use the mutable latest tag with bunx. Package runners download and execute that resolved release.
높음
SKILL.md:157-164references/app-deploy-cli.md:351-359
Production Mutation Confirmation Bypass
The skill documents production deploy, promotion, rollback, removal, and other remote mutations with non-interactive confirmation flags. Incorrect target inference could alter live infrastructure.
The cited guidance explicitly combines production operations with --yes. Intent guardrails are present, but the commands bypass interactive confirmation once run.
기능 검토 항목 (16)

이 스킬에 대해 예상될 수 있는 실제 로컬 기능이므로 검토가 필요하지만, 확인된 악의적 동작으로는 집계되지 않습니다.

높음
references/app-deploy-cli.md:150
Database connection strings
bunx @prisma/cli@latest project env add DATABASE_URL=postgresql://... --branch feature/foo
The guidance permits a database URL in command arguments, so substituted credentials can enter shell history or process listings. The example is legitimate but security-sensitive.
높음
references/app-deploy-cli.md:152
Database connection strings
bunx @prisma/cli@latest project env update DATABASE_URL=postgresql://... --branch feature/foo
The guidance permits a database URL in command arguments, so substituted credentials can enter shell history or process listings. The example is legitimate but security-sensitive.
높음
references/app-deploy-cli.md:165
Database connection strings
- Existing database env values supplied through `--env DATABASE_URL=...`, `--env DIRECT_URL=...`, an
The guidance permits a database URL in command arguments, so substituted credentials can enter shell history or process listings. The example is legitimate but security-sensitive.
높음
references/create-prisma.md:65
Database connection strings
- a `.env` file containing `DATABASE_URL`
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
높음
references/sdk-api.md:47
Database connection strings
const databaseUrl = process.env.DATABASE_URL
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
높음
references/sdk-api.md:48
Database connection strings
if (!databaseUrl) throw new Error("DATABASE_URL is required")
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
높음
references/sdk-api.md:58
Database connection strings
envVars: { DATABASE_URL: databaseUrl },
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
높음
references/troubleshooting.md:197
Database connection strings
1. Put a real production-ready `DATABASE_URL` in `.env` or project env.
The documented workflow creates, reads, stores, or transmits a real DATABASE_URL. This is intended deployment behavior, but the value is a credential requiring strict redaction and scope controls.
중간
references/compute-config.md:141
Hidden file access
env: "apps/web/.env",
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
중간
references/compute-config.md:149
Hidden file access
file: "apps/api/.env",
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
중간
references/frameworks.md:359
Hidden file access
env: "packages/db/.env",
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
중간
references/frameworks.md:379
Hidden file access
--env packages/db/.env
The configuration or command explicitly references a hidden .env file as deployment input. That file commonly contains credentials and is read during the intended workflow.
중간
references/sdk-api.md:35
Environment variable access (dot notation)
token: process.env.PRISMA_API_TOKEN,
The SDK example reads PRISMA_API_TOKEN from the process environment and supplies it to an authenticated client. This is legitimate secret access that requires redaction and least privilege.
중간
references/sdk-api.md:47
Environment variable access (dot notation)
const databaseUrl = process.env.DATABASE_URL
The SDK example reads DATABASE_URL from the process environment before deployment. This is legitimate credential handling, but accidental logging or broad process access could expose it.
중간
references/sdk-api.md:35
Environment variable object
token: process.env.PRISMA_API_TOKEN,
The SDK example reads PRISMA_API_TOKEN from the process environment and supplies it to an authenticated client. This is legitimate secret access that requires redaction and least privilege.
중간
references/sdk-api.md:47
Environment variable object
const databaseUrl = process.env.DATABASE_URL
The SDK example reads DATABASE_URL from the process environment before deployment. This is legitimate credential handling, but accidental logging or broad process access could expose it.

위험 요인

🌐 네트워크 접근 (6)
references/app-deploy-cli.md:269 references/frameworks.md:296 references/troubleshooting.md:350 references/troubleshooting.md:351 SKILL.md:3 SKILL.md:128
🔑 환경 변수 (40)
references/app-deploy-cli.md:150 references/app-deploy-cli.md:152 references/app-deploy-cli.md:165 references/app-deploy-cli.md:195 references/compute-config.md:92 references/create-prisma.md:107 references/create-prisma.md:65 references/create-prisma.md:82 references/create-prisma.md:109 references/frameworks.md:127 references/frameworks.md:133 references/frameworks.md:162 references/frameworks.md:169 references/frameworks.md:289 references/frameworks.md:295 references/frameworks.md:127 references/frameworks.md:133 references/frameworks.md:162 references/frameworks.md:169 references/frameworks.md:289 references/frameworks.md:295 references/sdk-api.md:35 references/sdk-api.md:47 references/sdk-api.md:35 references/sdk-api.md:47 references/sdk-api.md:47 references/sdk-api.md:48 references/sdk-api.md:58 references/troubleshooting.md:333 references/troubleshooting.md:333 references/troubleshooting.md:187 references/troubleshooting.md:191 references/troubleshooting.md:197 references/troubleshooting.md:216 references/troubleshooting.md:244 SKILL.md:129 SKILL.md:129 SKILL.md:148 SKILL.md:147 SKILL.md:191
📁 파일 시스템 접근 (5)
references/compute-config.md:141 references/compute-config.md:149 references/frameworks.md:359 references/frameworks.md:379 references/troubleshooting.md:371
⚙️ 외부 명령어 (50)
SKILL.md:3 SKILL.md:18-23 SKILL.md:23-25 SKILL.md:25 SKILL.md:29-31 SKILL.md:31-34 SKILL.md:34-36 SKILL.md:36 SKILL.md:42 SKILL.md:43 SKILL.md:53-55 SKILL.md:55 SKILL.md:56-59 SKILL.md:59-60 SKILL.md:60-61 SKILL.md:61-62 SKILL.md:62-67 SKILL.md:67-70 SKILL.md:70-73 SKILL.md:73-76 SKILL.md:76-79 SKILL.md:79-82 SKILL.md:82-88 SKILL.md:88-89 SKILL.md:89-90 SKILL.md:90-91 SKILL.md:91-92 SKILL.md:92-93 SKILL.md:93-94 SKILL.md:94-95 SKILL.md:95-101 SKILL.md:101-102 SKILL.md:102 SKILL.md:103 SKILL.md:104-105 SKILL.md:105 SKILL.md:106 SKILL.md:110 SKILL.md:111 SKILL.md:112 SKILL.md:113 SKILL.md:114 SKILL.md:115 SKILL.md:116 SKILL.md:117 SKILL.md:121 SKILL.md:122 SKILL.md:123 SKILL.md:124-128 SKILL.md:128
감사자: codex 감사 이력 보기 →
이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기
보안 평가

보고서 링크 복사

https://skillstore.io/skills/prisma-prisma-compute/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/prisma-prisma-compute/security.svg)](https://skillstore.io/skills/prisma-prisma-compute?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/prisma-prisma-compute?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prisma-prisma-compute/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/prisma-prisma-compute.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
학술 인용 (APA · BibTeX · CFF)

APA 인용

prisma. (2026). prisma-compute security audit report (audit version 7) [Author version 1.4.1]. Skillstore. https://skillstore.io/skills/prisma-prisma-compute/audits/7

BibTeX 인용

@techreport{prisma-prisma-prisma-compute-2026, author = {prisma}, title = {prisma-compute security audit report (audit version 7)}, institution = {Skillstore}, year = {2026}, number = {7}, url = {https://skillstore.io/skills/prisma-prisma-compute/audits/7}, note = {Author version 1.4.1} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "prisma-compute security audit report (audit version 7)" version: "1.4.1" type: report authors: - name: "prisma" date-released: "2026-07-23" url: "https://skillstore.io/skills/prisma-prisma-compute/audits/7" identifiers: - type: other value: "skillstore:prisma-prisma-compute:audit:7" description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간
45
아키텍처
100
유지보수성
87
콘텐츠
65
커뮤니티
91
사양 준수

만들 수 있는 것

기존 서비스 준비

기존 TypeScript 서비스의 Compute 구성, 빌드 출력, 환경 입력값 및 포트 바인딩을 검토합니다.

프리뷰 브랜치 배포

프로젝트, 앱, 브랜치 및 프리뷰 환경 설정을 명시하여 브랜치 배포를 계획합니다.

배포 실패 해결

올바른 CLI 출력과 로그를 사용하여 인증, 빌드, 데이터베이스 및 런타임 실패를 구분합니다.

이 프롬프트를 사용해 보세요

배포 준비 상태 검토 
Prisma Compute 배포 준비 상태를 확인하기 위해 내 프로젝트를 검토해 주세요. 프레임워크, 빌드 명령어, 포트 바인딩 및 필수 구성을 확인해 주세요.
Compute 구성 생성 
내 애플리케이션을 위한 prisma.compute.ts 구성을 만드는 데 도움을 주세요. 앱 루트, 프레임워크, 엔트리포인트, HTTP 포트 및 환경 파일 경로를 물어봐 주세요.
프리뷰 배포 계획 
내 브랜치를 위한 안전한 Prisma Compute 프리뷰 배포를 계획해 주세요. 명령어를 제안하기 전에 프로젝트, 앱, 브랜치 및 환경 설정을 명확하게 파악해 주세요.
실패한 배포 문제 해결 
내 Prisma Compute 배포 실패를 진단해 주세요. 먼저 인증, 빌드, 환경, 데이터베이스 또는 런타임 문제로 분류한 다음, 가장 비침습적인 점검 항목을 나열해 주세요.

모범 사례

  • 배포 명령어를 실행하기 전에 CLI 도움말과 기존 프로젝트 구성을 확인합니다.
  • 자동화 작업에는 워크스페이스, 프로젝트, 앱 및 브랜치 식별자를 명시적으로 사용합니다.
  • 비밀 값은 플랫폼 또는 CI 저장소에 보관하고 연결 URL이나 토큰을 절대 출력하지 않습니다.

피하기

  • 사용자의 명확한 의도와 대상 검토 없이 프로덕션에 배포하지 않습니다.
  • 플레이스홀더 데이터베이스 URL을 사용하거나 비밀 값을 구성 파일에 커밋하지 않습니다.
  • 로컬 준비 상태를 공개 배포에 접근할 수 있다는 증거로 간주하지 않습니다.

자주 묻는 질문

이 스킬은 애플리케이션을 자동으로 배포하나요?
아니요. 이 스킬은 안내를 제공하며 원격 애플리케이션을 변경하는 명령어를 실행하기 전에 확인을 요청해야 합니다.
어떤 프레임워크를 다루나요?
Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, 사용자 지정 앱 및 Bun에 대해 문서화된 Compute 준비 지침을 다룹니다.
prisma.compute.ts를 커밋해야 하나요?
비밀 값이 아닌 배포 기본값은 커밋할 수 있습니다. 토큰, 연결 문자열 및 비밀 값은 버전 관리 외부에 보관하세요.
여러 워크스페이스를 어떻게 처리해야 하나요?
로컬 세션을 확인하고 비대화형 변경 작업 전에 워크스페이스 식별자를 명시적으로 선택하세요.
배포 시 데이터베이스 마이그레이션이 실행되나요?
아니요. 적절한 데이터베이스 워크플로를 통해 마이그레이션과 시드 작업을 별도로 실행하세요.
실패 후 어떤 로그를 확인해야 하나요?
빌드 실패에는 빌드 로그를 사용하고 런타임 배포 실패에는 애플리케이션 로그를 사용하세요.

개발자 세부 정보

작성자

prisma

라이선스

MIT

작성자 버전

v1.4.1

Skillstore 리비전

r2

리포지토리

https://github.com/prisma/skills/tree/1a9f427e9fe2137298abbcc1a6f372db92e8c40d/prisma-compute

참조

ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006

유지보수 최신성

2026. 7. 25.

사용량

0 다운로드 · 0 조회

파일 구조

📁 references/

📄 app-deploy-cli.md

📄 compute-config.md

📄 create-prisma.md

📄 frameworks.md

📄 sdk-api.md

📄 troubleshooting.md

📄 SKILL.md

prisma의 다른 스킬

전체 보기

관련 스킬

전체 보기