vefaas
Deploy and manage serverless applications on Volcengine veFaaS. Use when the user wants to deploy web apps, manage functions (pull code, upload and deploy), configure environment variables, or work with veFaaS services.
What this skill does
# vefaas: Volcengine FaaS CLI **vefaas** is the command-line tool for Volcengine Function Service (veFaaS). It enables serverless application deployment, function management, and configuration through a streamlined workflow. ## Installation ```bash npm i -g https://vefaas-cli.tos-cn-beijing.volces.com/volcengine-vefaas-latest.tgz ``` Verify installation: ```bash vefaas --version ``` ## Core Workflow The typical deployment pattern: 1. **Check Node.js**: `node --version` (requires >= 18, recommended 20+) - If version is too low, switch using nvm (`nvm use 20`) or fnm (`fnm use 20`), or manually install a newer version 2. **Check CLI**: `vefaas --version` to verify installation 3. **Check Auth**: `vefaas login --check` to verify login status - If not logged in, run `vefaas login --sso` (opens browser, auto-completes when user authorizes - no manual input needed) 4. **Deploy**: `vefaas deploy --newApp <name> --gatewayName $(vefaas run listgateways --first) --yes` 5. **Access**: `vefaas domains` to view URLs ## Quick Commands | Purpose | Command | |---------|---------| | Check auth | `vefaas login --check` | | Login (SSO) | `vefaas login --sso` (non-interactive: opens browser, auto-completes when authorized, **recommended**) | | Login (AK/SK) | `vefaas login --accessKey <AK> --secretKey <SK>` | | Init from template | `vefaas init --template <name>` | | Deploy new app | `vefaas deploy --newApp <name> --gatewayName $(vefaas run listgateways --first) --yes` | | Deploy existing | `vefaas deploy --app <name> --yes` | | List gateways | `vefaas run listgateways --first` | | View URLs | `vefaas domains` | | Set env var | `vefaas env set KEY VALUE` | | View config | `vefaas config list` | | Pull code | `vefaas pull --func <name>` | | Inspect project | `vefaas inspect` | ## Global Options | Option | Description | |--------|-------------| | `-d, --debug` | Enable debug mode for troubleshooting | | `--yes` | Non-interactive mode (required for CI/AI coding) | | `--region` | Region override (e.g., cn-beijing) | ## Cookbooks Step-by-step guides for common scenarios: - **[Template Quickstart](cookbooks/template-quickstart.md)** - Create and deploy from official templates - **[Deploy Existing Code](cookbooks/deploy-existing-code.md)** - Deploy your existing project - **[Manage Functions](cookbooks/manage-functions.md)** - Manage functions (pull code, upload and deploy) ## References Detailed documentation on specific topics: - **[Authentication](references/authentication.md)** - Login methods and credentials - **[Configuration](references/configuration.md)** - Config files and settings - **[Environment Variables](references/environment-variables.md)** - Managing env vars - **[Framework Detection](references/framework-detection.md)** - Supported frameworks and auto-detection - **[Troubleshooting](references/troubleshooting.md)** - Debug mode, common issues, and solutions ## Important Notes - Always use `--yes` for non-interactive mode in CI/CD and AI coding scenarios - Use `$(vefaas run listgateways --first)` to get an available gateway - Config is stored in `.vefaas/config.json` after linking - Use `--debug` or `-d` to troubleshoot issues
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.