'resource-management' 검색 결과

Structure Python code to release files and database connections reliably, including when errors occur. Covers context managers, which handle setup and cleanup, asynchronous resources, nested cleanup, and streaming responses that retain accumulated state.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Releasing database connections when errors occur
• Cleaning up files and temporary files
• Creating asynchronous context managers

Build server-side Zoom integrations for meeting scheduling, user management, and recording downloads. This reference guides API endpoint selection, OAuth authentication, request limits, and error diagnosis, with examples for automated workflows and event notifications.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automating meeting creation and updates
• Managing Zoom users in bulk
• Downloading recordings after event notifications

Best-practices reference for preparing and instrumenting applications on Temps. Covers the app runtime contract (`.temps.yaml` health, HOST/PORT, readiness, SIGTERM, replicas, migrations) and production observability (errors, traces, metrics, logs, analytics, privacy, sampling, cardinality, credential boundaries). Use whenever building or reviewing an app for Temps, configuring health checks, adding telemetry, diagnosing missing/noisy signals, or checking OTLP/Sentry/analytics ingestion. Triggers include "temps best practices", "prepare this app for Temps", ".temps.yaml health", "temps health check", "ignore health checks in otel", "temps observability", "wire up telemetry", and "instrument this app for temps". Prefer focused setup skills for a single SDK. Use temps-cli for executing deploy and resource-management commands.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tracks quotas, monitors thresholds, and degrades gracefully for rate-limited APIs. Use when integrating external services that impose rate or cost limits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement cloud cost optimization strategies for Kubernetes workloads using tools like Kubecost for visibility, right-sizing recommendations, horizontal and vertical pod autoscaling, spot/preemptible instances, and resource quotas. Covers cost allocation, showback reporting, and continuous optimization practices. Use when cloud costs are growing without proportional business value, when resource requests are misaligned with actual usage, when manual scaling leads to over-provisioning, or when implementing showback and chargeback for internal cost accountability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to create, configure, or tune Field Service Lightning scheduling policies — including work rules (pass/fail filters) and service objectives (weighted ranking criteria). Covers the four default policies, custom policy design, work rule type selection, and objective weighting strategy. NOT for running or tuning the Optimizer itself — use admin/fsl-scheduling-optimization-design. NOT for resource skills and preferences — use admin/fsl-resource-management. NOT for resource capacity records — use admin/fsl-capacity-planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure FSL Shifts, ShiftTemplates, ShiftPatterns, and Crew ServiceResources — availability windows layered on Operating Hours, bulk shift generation via ShiftPattern + ShiftPatternEntry, and the two Crew models (Static vs. Shell/Dynamic). NOT for setting up the resources themselves — types, skills, ResourcePreference — use admin/fsl-resource-management. NOT for capping how many hours or appointments a resource can take — use admin/fsl-capacity-planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure and manage Field Service Lightning work orders: work types, work order line items, service appointments, status flow, and auto-creation via maintenance plans. NOT for choosing which technician gets the appointment (work rules, scheduling policies) — use admin/fsl-scheduling-policies. NOT for setting up the technicians, their skills or capacity — use admin/fsl-resource-management.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to configure Field Service Lightning service resources — including ServiceResource types, skill assignments via ServiceResourceSkill, capacity-based resource setup, and ResourcePreference rules. NOT for territory-level WorkCapacityLimit throttling or capacity-vs-utilization reporting — use admin/fsl-capacity-planning. NOT for service territory setup — use admin/fsl-service-territory-setup. NOT for work rules and service objectives — use admin/fsl-scheduling-policies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to configure and manage Field Service Lightning workforce capacity — covering ServiceResourceCapacity for individual resource caps, WorkCapacityLimit for territory-level demand throttling, and reporting strategies for capacity vs. utilization analysis. NOT for resource skills, certifications, or preference setup — use admin/fsl-resource-management. NOT for work rules and service objectives — use admin/fsl-scheduling-policies. NOT for Omni-Channel agent capacity — use architect/omni-channel-capacity-model.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en Coolify avancé (self-hosting, Docker, déploiements, SSL, backups, gestion des ressources, multi-serveurs)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Coolify infrastructure — Traefik, services, deploy, SSL, backups, resource management

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.