[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C48G27QZ9F5P2SNRKZXVB1":3,"skill-same:01M6C48G27QZ9F5P2SNRKZXVB1":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":5,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6C48G27QZ9F5P2SNRKZXVB1","cloudflare-workers",null,"Deploy serverless applications on Cloudflare Workers. Covers project setup, JavaScript handler patterns, routing, deployment with Wrangler, and API token configuration. Suitable for APIs, proxies, edge computing, and request transformation.","stakpak\u002Fcommunity-paks","stakpak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F86326525?v=4","01M6C48005ADA10YG0BQQX0J4Q","Stakpak","01M6C4804JD6KKZR9AQ9TYS0BT",4,"MIT","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fcloudflare-workers\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"cloudflare","cloudflare workers","javascript","deploy","setup","deployment","routing","dev","wrangler","edge","applications","api","serverless","team","2026-11-10 10:12:30",false,"---\nname: cloudflare-workers\ndescription: |\n  Deploy serverless applications on Cloudflare Workers. Covers project setup, JavaScript handler patterns, routing, deployment with Wrangler, and API token configuration. Suitable for APIs, proxies, edge computing, and request transformation.\nlicense: MIT\nmetadata:\n  author: Stakpak \u003Cteam@stakpak.dev>\n  version: 1.0.18\n---\n\n# Deploying Cloudflare Workers\n\n## Quick Start\n\n### Create and Deploy\n\n```bash\n# Create project\nnpm create cloudflare@latest my-worker -- --type=hello-world --ts=false --git=false --deploy=false\ncd my-worker\n\n# Deploy\nexport CLOUDFLARE_API_TOKEN=\"your-token-here\"\nexport CLOUDFLARE_ACCOUNT_ID=\"your-account-id\"\nnpx wrangler deploy\n```\n\n## Prerequisites\n\n* Node.js 16.17.0 or later installed\n* Cloudflare account (free tier works)\n* Cloudflare API token with Workers permissions\n\n## Setup\n\n### 1. Create API Token\n\nBefore deployment, create a Cloudflare API token with proper permissions:\n\n1. Go to https:\u002F\u002Fdash.cloudflare.com\u002Fprofile\u002Fapi-tokens\n2. Click **\"Create Token\"**\n3. Select **\"Edit Cloudflare Workers\"** template\n4. Click **\"Continue to summary\"** → **\"Create Token\"**\n5. Save the token securely\n\n**Required permissions:**\n* Account: Workers Scripts (Edit)\n* Account: Account Settings (Read)\n* User: User Details (Read)\n\n### 2. Register workers.dev Subdomain\n\nIf this is your first Worker deployment:\n\n1. Go to Cloudflare Dashboard → Workers & Pages\n2. Look for \"Your subdomain\" section\n3. Click \"Change\" or \"Set up\"\n4. Enter a unique subdomain name (e.g., `mycompany`)\n5. Save\n\nYour workers will be available at: `\u003Cworker-name>.\u003Csubdomain>.workers.dev`\n\n### 3. Create Worker Project\n\nUse C3 (create-cloudflare-cli) to scaffold the project:\n\n```bash\nnpm create cloudflare@latest my-worker -- --type=hello-world --ts=false --git=false --deploy=false\ncd my-worker\n```\n\n**Generated structure:**\n```\nmy-worker\u002F\n├── src\u002F\n│   └── index.js      # Worker entry point\n├── wrangler.jsonc    # Wrangler configuration\n├── package.json\n└── node_modules\u002F\n```\n\n### 4. Configure Wrangler\n\nUpdate `wrangler.jsonc` with your worker settings:\n\n```jsonc\n{\n  \"$schema\": \".\u002Fnode_modules\u002Fwrangler\u002Fconfig-schema.json\",\n  \"name\": \"my-worker\",\n  \"main\": \"src\u002Findex.js\",\n  \"compatibility_date\": \"2024-12-01\",\n  \"observability\": {\n    \"enabled\": true\n  }\n}\n```\n\n**Key settings:**\n* `name`: Worker name (becomes part of URL)\n* `main`: Entry point file\n* `compatibility_date`: Runtime compatibility version\n* `observability`: Enable logging and metrics\n\n### 5. Implement the Worker Handler\n\nWorkers use a fetch handler pattern. Create your worker logic in `src\u002Findex.js`:\n\n```javascript\n\u002F**\n * Worker Handler Template\n * Handles routing, JSON responses, and CORS\n *\u002F\n\nexport default {\n  async fetch(request, env, ctx) {\n    const url = new URL(request.url);\n    const path = url.pathname;\n\n    \u002F\u002F CORS headers for all responses\n    const corsHeaders = {\n      'Access-Control-Allow-Origin': '*',\n      'Access-Control-Allow-Methods': 'GET, POST, OPTIONS',\n      'Access-Control-Allow-Headers': 'Content-Type',\n    };\n\n    \u002F\u002F Handle OPTIONS preflight\n    if (request.method === 'OPTIONS') {\n      return new Response(null, { headers: corsHeaders });\n    }\n\n    \u002F\u002F Route handling\n    switch (path) {\n      case '\u002Fhealth':\n        return jsonResponse({\n          status: 'healthy',\n          service: 'my-worker',\n          timestamp: new Date().toISOString()\n        }, 200, corsHeaders);\n      \n      case '\u002Fapi\u002Fendpoint':\n        return handleApiEndpoint(request, url, corsHeaders);\n      \n      default:\n        return jsonResponse({\n          error: 'Not found',\n          available_endpoints: ['GET \u002Fhealth', 'GET \u002Fapi\u002Fendpoint']\n        }, 404, corsHeaders);\n    }\n  },\n};\n\nfunction handleApiEndpoint(request, url, corsHeaders) {\n  \u002F\u002F Parse query parameters\n  const params = url.searchParams;\n  const param1 = params.get('param1');\n  \n  \u002F\u002F Validate\n  if (!param1) {\n    return jsonResponse({\n      error: 'Missing required parameter: param1'\n    }, 400, corsHeaders);\n  }\n  \n  \u002F\u002F Process and return\n  return jsonResponse({\n    result: `Processed: ${param1}`\n  }, 200, corsHeaders);\n}\n\nfunction jsonResponse(data, status = 200, additionalHeaders = {}) {\n  return new Response(JSON.stringify(data, null, 2), {\n    status: status,\n    headers: {\n      'Content-Type': 'application\u002Fjson',\n      ...additionalHeaders\n    }\n  });\n}\n```\n\n**Handler parameters:**\n* `request`: Incoming HTTP Request object\n* `env`: Environment bindings (KV, D1, secrets, etc.)\n* `ctx`: Execution context (waitUntil, passThroughOnException)\n\n### 6. Test Locally\n\nRun the development server:\n\n```bash\nnpx wrangler dev\n```\n\nTest the worker at `http:\u002F\u002Flocalhost:8787`:\n```bash\ncurl http:\u002F\u002Flocalhost:8787\u002Fhealth\ncurl \"http:\u002F\u002Flocalhost:8787\u002Fapi\u002Fendpoint?param1=test\"\n```\n\n### 7. Deploy to Production\n\nDeploy using environment variables for authentication:\n\n```bash\nexport CLOUDFLARE_API_TOKEN=\"your-token-here\"\nexport CLOUDFLARE_ACCOUNT_ID=\"your-account-id\"\nnpx wrangler deploy\n```\n\n**Finding your Account ID:**\n* Dashboard → Workers & Pages → Account ID in sidebar\n* Or from the URL: `dash.cloudflare.com\u002F\u003Caccount-id>\u002Fworkers`\n\n### 8. Verify Deployment\n\nTest the live worker:\n\n```bash\n# Health check\ncurl https:\u002F\u002Fmy-worker.mysubdomain.workers.dev\u002Fhealth\n\n# API endpoint\ncurl \"https:\u002F\u002Fmy-worker.mysubdomain.workers.dev\u002Fapi\u002Fendpoint?param1=test\"\n```\n\n## Common Patterns\n\n### Request Method Handling\n\n```javascript\nswitch (request.method) {\n  case 'GET':\n    return handleGet(url);\n  case 'POST':\n    const body = await request.json();\n    return handlePost(body);\n  case 'PUT':\n    return handlePut(request);\n  case 'DELETE':\n    return handleDelete(url);\n  default:\n    return jsonResponse({ error: 'Method not allowed' }, 405);\n}\n```\n\n### Path Parameter Extraction\n\n```javascript\n\u002F\u002F For paths like \u002Fusers\u002F123\nconst match = path.match(\u002F^\\\u002Fusers\\\u002F(\\d+)$\u002F);\nif (match) {\n  const userId = match[1];\n  return handleUser(userId);\n}\n```\n\n### Environment Variables and Secrets\n\nAdd to `wrangler.jsonc`:\n```jsonc\n{\n  \"vars\": {\n    \"API_VERSION\": \"v1\"\n  }\n}\n```\n\nAdd secrets via CLI:\n```bash\nnpx wrangler secret put API_KEY\n```\n\nAccess in handler:\n```javascript\nasync fetch(request, env, ctx) {\n  const version = env.API_VERSION;\n  const apiKey = env.API_KEY;\n}\n```\n\n### KV Storage Binding\n\nAdd to `wrangler.jsonc`:\n```jsonc\n{\n  \"kv_namespaces\": [\n    { \"binding\": \"CACHE\", \"id\": \"your-kv-namespace-id\" }\n  ]\n}\n```\n\nUse in handler:\n```javascript\n\u002F\u002F Read\nconst value = await env.CACHE.get('key');\n\n\u002F\u002F Write\nawait env.CACHE.put('key', 'value', { expirationTtl: 3600 });\n```\n\n## Deployment Options\n\n| Method | Use Case |\n|--------|----------|\n| `workers.dev` subdomain | Quick testing, hobby projects |\n| Custom Domain | Production deployments |\n| Routes | Add Workers to existing domains |\n\n### Custom Domain Setup\n\nAdd to `wrangler.jsonc`:\n```jsonc\n{\n  \"routes\": [\n    { \"pattern\": \"api.example.com\u002F*\", \"custom_domain\": true }\n  ]\n}\n```\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Authentication error | Verify API token has correct permissions, check CLOUDFLARE_ACCOUNT_ID is set correctly, ensure token hasn't expired |\n| workers.dev subdomain not registered | Go to Dashboard → Workers & Pages → Set up subdomain (must be done before first deployment) |\n| SSL handshake failures | New deployments may take 1-2 minutes for SSL provisioning, try accessing via browser first, check with `curl --insecure` to bypass local SSL issues |\n| Worker not updating | Clear browser cache, check deployment version ID in output, use `wrangler tail` to see live logs |\n\n## References\n\n* [Cloudflare Workers Documentation](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fworkers\u002F)\n* [Wrangler Configuration](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fworkers\u002Fwrangler\u002Fconfiguration\u002F)\n* [Workers Runtime APIs](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fworkers\u002Fruntime-apis\u002F)\n* [Fetch Handler Reference](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fworkers\u002Fruntime-apis\u002Fhandlers\u002Ffetch\u002F)\n* [API Token Creation](https:\u002F\u002Fdevelopers.cloudflare.com\u002Ffundamentals\u002Fapi\u002Fget-started\u002Fcreate-token\u002F)","# Deploying Cloudflare Workers\n\n## Quick Start\n\n### Create and Deploy\n\n```bash\n# Create project\nnpm create cloudflare@latest my-worker -- --type=hello-world --ts=false --git=false --deploy=false\ncd my-worker\n\n# Deploy\nexport CLOUDFLARE_API_TOKEN=\"your-token-here\"\nexport CLOUDFLARE_ACCOUNT_ID=\"your-account-id\"\nnpx wrangler deploy\n```\n\n## Prerequisites\n\n* Node.js 16.17.0 or later installed\n* Cloudflare account (free tier works)\n* Cloudflare API token with Workers permissions\n\n## Setup\n\n### 1. Create API Token\n\nBefore deployment, create a Cloudflare API token with proper permissions:\n\n1. Go to https:\u002F\u002Fdash.cloudflare.com\u002Fprofile\u002Fapi-tokens\n2. Click **\"Create Token\"**\n3. Select **\"Edit Cloudflare Workers\"** template\n4. Click **\"Continue to summary\"** → **\"Create Token\"**\n5. Save the token securely\n\n**Required permissions:**\n* Account: Workers Scripts (Edit)\n* Account: Account Settings (Read)\n* User: User Details (Read)\n\n### 2. Register workers.dev Subdomain\n\nIf this is your first Worker deployment:\n\n1. Go to Cloudflare Dashboard → Workers & Pages\n2. Look for \"Your subdomain\" section\n3. Click \"Change\" or \"Set up\"\n4. Enter a unique subdomain name (e.g., `mycompany`)\n5. Save\n\nYour workers will be available at: `\u003Cworker-name>.\u003Csubdomain>.workers.dev`\n\n### 3. Create Worker Project\n\nUse C3 (create-cloudflare-cli) to scaffold the project:\n\n```bash\nnpm create cloudflare@latest my-worker -- --type=hello-world --ts=false --git=false --deploy=false\ncd my-worker\n```\n\n**Generated structure:**\n```\nmy-worker\u002F\n├── src\u002F\n│   └── index.js      # Worker entry point\n├── wrangler.jsonc    # Wrangler configuration\n├── package.json\n└── node_modules\u002F\n```\n\n### 4. Configure Wrangler\n\nUpdate `wrangler.jsonc` with your worker settings:\n\n```jsonc\n{\n  \"$schema\": \".\u002Fnode_modules\u002Fwrangler\u002Fconfig-schema.json\",\n  \"name\": \"my-worker\",\n  \"main\": \"src\u002Findex.js\",\n  \"compatibility_date\": \"2024-12-01\",\n  \"observability\": {\n    \"enabled\": true\n  }\n}\n```\n\n**Key settings:**\n* `name`: Worker name (becomes part of URL)\n* `main`: Entry point file\n* `compatibility_date`: Runtime compatibility version\n* `observability`: Enable logging and metrics\n\n### 5. Implement the Worker Handler\n\nWorkers use a fetch handler pattern. Create your worker logic in `src\u002Findex.js`:\n\n```javascript\n\u002F**\n * Worker Handler Template\n * Handles routing, JSON responses, and CORS\n *\u002F\n\nexport default {\n  async fetch(request, env, ctx) {\n    const url = new URL(request.url);\n    const path = url.pathname;\n\n    \u002F\u002F CORS headers for all responses\n    const corsHeaders = {\n      'Access-Control-Allow-Origin': '*',\n      'Access-Control-Allow-Methods': 'GET, POST, OPTIONS',\n      'Access-Control-Allow-Headers': 'Content-Type',\n    };\n\n    \u002F\u002F Handle OPTIONS preflight\n    if (request.method === 'OPTIONS') {\n      return new Response(null, { headers: corsHeaders });\n    }\n\n    \u002F\u002F Route handling\n    switch (path) {\n      case '\u002Fhealth':\n        return jsonResponse({\n          status: 'healthy',\n          service: 'my-worker',\n          timestamp: new Date().toISOString()\n        }, 200, corsHeaders);\n      \n      case '\u002Fapi\u002Fendpoint':\n        return handleApiEndpoint(request, url, corsHeaders);\n      \n      default:\n        return jsonResponse({\n          error: 'Not found',\n          available_endpoints: ['GET \u002Fhealth', 'GET \u002Fapi\u002Fendpoint']\n        }, 404, corsHeaders);\n    }\n  },\n};\n\nfunction handleApiEndpoint(request, url, corsHeaders) {\n  \u002F\u002F Parse query parameters\n  const params = url.searchParams;\n  const param1 = params.get('param1');\n  \n  \u002F\u002F Validate\n  if (!param1) {\n    return jsonResponse({\n      error: 'Missing required parameter: param1'\n    }, 400, corsHeaders);\n  }\n  \n  \u002F\u002F Process and return\n  return jsonResponse({\n    result: `Processed: ${param1}`\n  }, 200, corsHeaders);\n}\n\nfunction jsonResponse(data, status = 200, additionalHeaders = {}) {\n  return new Response(JSON.stringify(data, null, 2), {\n    status: status,\n    headers: {\n      'Content-Type': 'application\u002Fjson',\n      ...additionalHeaders\n    }\n  });\n}\n```\n\n**Handler parameters:**\n* `request`: Incoming HTTP Request object\n* `env`: Environment bindings (KV, D1, secrets, etc.)\n* `ctx`: Execution context (waitUntil, passThroughOnException)\n\n### 6. Test Locally\n\nRun the development server:\n\n```bash\nnpx wrangler dev\n```\n\nTest the worker at `http:\u002F\u002Flocalhost:8787`:\n```bash\ncurl http:\u002F\u002Flocalhost:8787\u002Fhealth\ncurl \"http:\u002F\u002Flocalhost:8787\u002Fapi\u002Fendpoint?param1=test\"\n```\n\n### 7. Deploy to Production\n\nDeploy using environment variables for authentication:\n\n```bash\nexport CLOUDFLARE_API_TOKEN=\"your-token-here\"\nexport CLOUDFLARE_ACCOUNT_ID=\"your-account-id\"\nnpx wrangler deploy\n```\n\n**Finding your Account ID:**\n* Dashboard → Workers & Pages → Account ID in sidebar\n* Or from the URL: `dash.cloudflare.com\u002F\u003Caccount-id>\u002Fworkers`\n\n### 8. Verify Deployment\n\nTest the live worker:\n\n```bash\n# Health check\ncurl https:\u002F\u002Fmy-worker.mysubdomain.workers.dev\u002Fhealth\n\n# API endpoint\ncurl \"https:\u002F\u002Fmy-worker.mysubdomain.workers.dev\u002Fapi\u002Fendpoint?param1=test\"\n```\n\n## Common Patterns\n\n### Request Method Handling\n\n```javascript\nswitch (request.method) {\n  case 'GET':\n    return handleGet(url);\n  case 'POST':\n    const body = await request.json();\n    return handlePost(body);\n  case 'PUT':\n    return handlePut(request);\n  case 'DELETE':\n    return handleDelete(url);\n  default:\n    return jsonResponse({ error: 'Method not allowed' }, 405);\n}\n```\n\n### Path Parameter Extraction\n\n```javascript\n\u002F\u002F For paths like \u002Fusers\u002F123\nconst match = path.match(\u002F^\\\u002Fusers\\\u002F(\\d+)$\u002F);\nif (match) {\n  const userId = match[1];\n  return handleUser(userId);\n}\n```\n\n### Environment Variables and Secrets\n\nAdd to `wrangler.jsonc`:\n```jsonc\n{\n  \"vars\": {\n    \"API_VERSION\": \"v1\"\n  }\n}\n```\n\nAdd secrets via CLI:\n```bash\nnpx wrangler secret put API_KEY\n```\n\nAccess in handler:\n```javascript\nasync fetch(request, env, ctx) {\n  const version = env.API_VERSION;\n  const apiKey = env.API_KEY;\n}\n```\n\n### KV Storage Binding\n\nAdd to `wrangler.jsonc`:\n```jsonc\n{\n  \"kv_namespaces\": [\n    { \"binding\": \"CACHE\", \"id\": \"your-kv-namespace-id\" }\n  ]\n}\n```\n\nUse in handler:\n```javascript\n\u002F\u002F Read\nconst value = await env.CACHE.get('key');\n\n\u002F\u002F Write\nawait env.CACHE.put('key', 'value', { expirationTtl: 3600 });\n```\n\n## Deployment Options\n\n| Method | Use Case |\n|--------|----------|\n| `workers.dev` subdomain | Quick testing, hobby projects |\n| Custom Domain | Production deployments |\n| Routes | Add Workers to existing domains |\n\n### Custom Domain Setup\n\nAdd to `wrangler.jsonc`:\n```jsonc\n{\n  \"routes\": [\n    { \"pattern\": \"api.example.com\u002F*\", \"custom_domain\": true }\n  ]\n}\n```\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Authentication error | Verify API token has correct permissions, check CLOUDFLARE_ACCOUNT_ID is set correctly, ensure token hasn't expired |\n| workers.dev subdomain not registered | Go to Dashboard → Workers & Pages → Set up subdomain (must be done before first deployment) |\n| SSL handshake failures | New deployments may take 1-2 minutes for SSL provisioning, try accessing via browser first, check with `curl --insecure` to bypass local SSL issues |\n| Worker not updating | Clear browser cache, check deployment version ID in output, use `wrangler tail` to see live logs |\n\n## References\n\n* [Cloudflare Workers Documentation](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fworkers\u002F)\n* [Wrangler Configuration](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fworkers\u002Fwrangler\u002Fconfiguration\u002F)\n* [Workers Runtime APIs](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fworkers\u002Fruntime-apis\u002F)\n* [Fetch Handler Reference](https:\u002F\u002Fdevelopers.cloudflare.com\u002Fworkers\u002Fruntime-apis\u002Fhandlers\u002Ffetch\u002F)\n* [API Token Creation](https:\u002F\u002Fdevelopers.cloudflare.com\u002Ffundamentals\u002Fapi\u002Fget-started\u002Fcreate-token\u002F)",{"name":5,"license":15,"metadata":43,"description":46},{"author":44,"version":45},"Stakpak \u003Cteam@stakpak.dev>","1.0.18","Deploy serverless applications on Cloudflare Workers. Covers project setup, JavaScript handler patterns, routing, deployment with Wrangler, and API token configuration. Suitable for APIs, proxies, edge computing, and request transformation.\n","main","d9bbde9885439c55adad930456b2660b0c37c052",1,"https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks","https:\u002F\u002Fgithub.com\u002Fstakpak","https:\u002F\u002Fwww.stakpak.dev","AI that runs your Infra","2026-07-04 20:18:32",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add stakpak\u002Fcommunity-paks --skill cloudflare-workers",{"tool":61,"command":62},"bunx","bunx skills add stakpak\u002Fcommunity-paks --skill cloudflare-workers",{"tool":64,"command":65},"pnpm","pnpm dlx skills add stakpak\u002Fcommunity-paks --skill cloudflare-workers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fcloudflare-workers\u002FSKILL.md",true,[],[70,100,124,142,161,179],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":85,"publishedAt":38},"01M6C49TTAVC8Q9CTTC05F6VSR","vllm-deployment","Deploy vLLM for high-performance LLM inference. Covers Docker CPU\u002FGPU deployments and cloud VM provisioning with OpenAI-compatible API endpoints.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fvllm-deployment\u002FSKILL.md",[76,79,80],{"categoryNo":77,"categoryName":78,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[86,87,29,88,89,90,91,92,37,35,93,94,95,96,31,97,27,98,99],"vllm deployment","vLLM","docker","cloud","openai-api","llm inference","learning","provisioning","machine-learning","gpu","openai","vm","performance","inference",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":38},"01M6C49R31XN7KJ7Y0Y78XVYTQ","terrateam-usage-guide","A comprehensive guide for configuring and using Terrateam, an open-source GitOps CI\u002FCD platform for Terraform and OpenTofu. Covers configuration file structure, access control, workflows, OIDC authentication, drift detection, and best practices for managing infrastructure through pull requests.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fterrateam-usage-guide\u002FSKILL.md",[106],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[108,109,110,111,112,37,113,114,115,116,117,31,118,119,120,121,122,123],"terrateam usage guide","guide","file","opentofu","access","open","detection","oidc","ci","pull","terraform","best practices","authentication","infrastructure","pull requests","workflows",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":38},"01M6C49N78AMM570EGPDXEZZDY","simple-deployment-on-vm","How to do simple but secure deployments using virtual machines on different cloud providers","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fsimple-deployment-on-vm\u002FSKILL.md",[],[131,97,29,132,31,133,134,37,135,136,137,138,139,89,140,27,141],"simple deployment on vm","tls configuration","virtual","how","ec2","Providers","tls","aws","dns","secure","security",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":38},"01M6C49J8PRVT623JWRTTKFNJV","nextjs-on-aws","This document compares various AWS deployment options for Next.js applications, analyzing costs, benefits, limitations, and providing recommendations based on different use cases.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fnextjs-on-aws\u002FSKILL.md",[],[149,138,150,151,152,153,37,154,155,34,156,157,31,29,158,159,160],"nextjs on aws","nextjs","use","aws deployment","js","Next.js","analysis","analyzing","cost","architecture","migration","cost-analysis",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":38},"01M6C49F5B4BF2CHNT4X08XP69","migrating-bitnami-to-bitnami-legacy","This rule book helps you migrate Bitnami Helm charts and container images from the bitnami repository to the bitnamilegacy repository.\n\nThis migration is necessary due to Bitnami's transition, effective August 28th, 2025, where existing images will be moved to the legacy repo","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fmigrating-bitnami-to-bitnami-legacy\u002FSKILL.md",[],[168,169,37,170,171,172,173,174,175,176,31,177,178],"migrating bitnami to bitnami legacy","container images","helm","migrate","bitnami-helm-charts","bitnami-legacy","bitnami","container","repo","repository","Charts",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":38},"01M6C49CHCPGZZ42P5W1MTV3WS","k3s-backup","Backup and recovery solution for K3s clusters. Includes scheduled, pre-shutdown, and manual backup strategies with recovery procedures.","https:\u002F\u002Fgithub.com\u002Fstakpak\u002Fcommunity-paks\u002Fblob\u002Fmain\u002Fk3s-backup\u002FSKILL.md",[],[186,187,188,31,189,37],"backup","k3s","k3s backup","recovery"]