المهارات prisma-compute
📦
prisma-compute
v1.4.1 مراجعة المحتوى r2 مخاطر عالية 🌐 الوصول إلى الشبكة🔑 متغيرات البيئة📁 الوصول إلى نظام الملفات⚙️ الأوامر الخارجية
نشر تطبيقات Prisma Compute بأمان
تتطلب عمليات نشر Prisma Compute إعدادات صحيحة ومصادقة وتهيئة للبيئة ومنافذ مناسبة لوقت التشغيل. ترشد هذه المهارة إلى إعداد أطر عمل TypeScript المدعومة ونشرها والتحقق منها واستكشاف أخطائها وإصلاحها.
يدعم: Claude Codex Code(CC)
توقف واطلب التأكيد قبل التثبيت.
راجع الخطة واحصل على موافقة صريحة من المستخدم قبل تغيير الملفات.
التثبيت باستخدام Agent لدي
انسخ هذا الطلب إلى Agent لديك. يتضمن صفحة Skill المعتمدة وملف manifest.
طلب الوكيل
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.يجب أن يواصل Agent عرض خطته وطلب أي تأكيد تفرضه سياسة الأمان.
موارد مهيّأة لـ Agents
استخدم هذه الروابط عندما يحتاج AI Agent أو crawler أو script إلى سياق نظيف بدلًا من قراءة الصفحة كاملة.
اختبرها
جارٍ استخدام "prisma-compute". راجع تطبيق Next.js الخاص بي قبل النشر.
النتيجة المتوقعة:
- إطار العمل: Next.js مع ضرورة استخدام مخرجات خادم standalone.
- وقت التشغيل: اربط التطبيق بمنفذ النشر وجميع الواجهات.
- الخطوة التالية: تحقق من نص النشر البرمجي والإعدادات اللذين تم إنشاؤهما.
جارٍ استخدام "prisma-compute". يتعذر على نشر المعاينة الخاص بي الاتصال بقاعدة البيانات.
النتيجة المتوقعة:
- تحقق من تطابق اسم الفرع مع نطاق بيئة الفرع.
- تأكد من إتاحة عنوان URL فعلي، وليس قيمة نائبة، لقاعدة البيانات في بيئة النشر.
- استخدم سجلات وقت التشغيل بعد التحقق من إعدادات البيئة.
جارٍ استخدام "prisma-compute". لدي عدة مساحات عمل في Prisma.
النتيجة المتوقعة:
- افحص مساحة العمل النشطة قبل تغيير حالة المشروع أو التطبيق.
- حدد معرّفًا صريحًا لمساحة العمل للعمليات غير التفاعلية.
- لا تعرض رموز الخدمة أو ملفات بيانات الاعتماد المحلية.
التدقيق الأمني
مخاطر عاليةv7 • ٢٣/٧/٢٠٢٦ فتح التقرير المرتبط بالإصدار
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)
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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)
هذه قدرات محلية حقيقية قد يُتوقع وجودها لهذه المهارة، لذا فهي تتطلب مراجعة ولكن لا تُحتسب كسلوك خبيث مؤكد.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
مرتفع
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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.
متوسط
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)
🔑 متغيرات البيئة (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)
⚙️ الأوامر الخارجية (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 الأدلة من دون أن تقرر ما إذا كانت هذه المهارة آمنة.
نسخ رابط التقرير
https://skillstore.io/skills/prisma-prisma-compute/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportشارة Markdown
[](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 نائبة لقواعد البيانات، ولا تودع القيم السرية في ملفات الإعداد.
- لا تعتبر الجاهزية المحلية دليلًا على إمكانية الوصول إلى النشر العام.
الأسئلة المتكررة
هل تنشر هذه المهارة تطبيقًا تلقائيًا؟
لا. إنها تقدم إرشادات ويجب أن تطلب التأكيد قبل تنفيذ الأوامر التي تغيّر التطبيقات البعيدة.
ما أطر العمل التي تغطيها؟
تغطي إرشادات الجاهزية الموثقة لـ Compute الخاصة بكل من Next.js وNuxt وAstro وHono وNestJS وTanStack Start والتطبيقات المخصصة وBun.
هل ينبغي أن أودع prisma.compute.ts؟
يمكنك إيداع إعدادات النشر الافتراضية غير السرية. احتفظ بالرموز وسلاسل الاتصال والقيم السرية خارج نظام التحكم في الإصدارات.
كيف ينبغي أن أتعامل مع عدة مساحات عمل؟
افحص الجلسات المحلية وحدد معرّفًا صريحًا لمساحة العمل قبل إجراء تغييرات غير تفاعلية.
هل يشغّل النشر عمليات ترحيل قاعدة البيانات؟
لا. شغّل عمليات الترحيل ومهام إدخال البيانات الأولية بشكل منفصل من خلال مسار العمل المناسب لقاعدة البيانات.
ما السجلات التي ينبغي أن أفحصها بعد حدوث فشل؟
استخدم سجلات البناء لحالات فشل البناء وسجلات التطبيق لحالات فشل النشر أثناء وقت التشغيل.
تفاصيل المطور
المؤلف
prismaالترخيص
MIT
إصدار المؤلف
v1.4.1
مراجعة Skillstore
r2
المستودع
https://github.com/prisma/skills/tree/1a9f427e9fe2137298abbcc1a6f372db92e8c40d/prisma-computeمرجع
ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
حداثة الصيانة
٢٦/٧/٢٠٢٦
الاستخدام
0 تنزيلات · 0 مشاهدات
بنية الملفات