skilld
All skills
denoland avatar

/deno-deploy

@2311d69 official
by Denodenoland/skills99 stars
8

Use when deploying Deno apps to production, asking about Deno Deploy, or working with `deno deploy` CLI commands. Covers deployment workflows, environment variables, KV database access, custom domains, the --tunnel flag for local development, and the `deno deploy` command reference.

Ask your Agent

Use this Skill: https://skilld.dev/gh/denoland/skills/deno-deploy

This session only. Nothing lands on disk.

referencesORGANIZATIONS.md

≈527 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Organizations

What is an Organization?

In Deno Deploy, an organization is a group where users collectively own apps and domains. Every user belongs to an organization - all resources (apps, domains, environment variables) exist at the organization level.

Each organization has:

  • Name: Displayed in the dashboard
  • Slug: Part of your default domain (e.g., acme-inc.deno.net)

Important: The slug cannot be changed after creation.

Creating an Organization

Organizations are created automatically during Deno Deploy signup:

  1. Visit https://console.deno.com
  2. Sign in with GitHub
  3. Create your organization as part of setup

Finding Your Organization

Your org name appears in the console URL:

https://console.deno.com/YOUR-ORG-NAME

Use this for CLI commands:

deno deploy create --org YOUR-ORG-NAME
deno deploy --org YOUR-ORG-NAME --prod

Managing Members

Inviting Users

  1. Go to organization settings in the dashboard
  2. Click "+ Invite User"
  3. Enter the person's GitHub username (e.g., ry)
  4. Optionally add their email address
  5. Send the invitation

The invitee receives an email with a link to accept.

Removing Members

  1. Go to organization settings
  2. Find the user in the members table
  3. Click remove and confirm

Canceling Invitations

Pending invitations can be cancelled before the person accepts.

Permissions

Currently, all members have owner permissions. Every member can:

  • Invite and remove other members
  • Create and delete apps
  • Manage domains
  • Configure environment variables
  • Deploy to production

There is no tiered permission system yet.

Organization Deletion

Organizations cannot be deleted through the dashboard. Contact Deno support if you need to delete an organization.

Best Practices

  • Choose your slug carefully - it's permanent and visible in URLs
  • Limit membership - since all members have full access
  • Use descriptive app names - they become part of URLs too

Documentation

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides safe and standard reference guidelines and deployment documentation for the Deno Deploy CLI. It covers configuration files, environment variables, command references, and databases without introducing dangerous command scripts, malicious prompt adjustments, obfuscated paths, or external download vulnerabilities.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    9/9 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 2311d69. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Steadyupdated 2 months ago

Capability

metadata
{
  "author": "denoland",
  "version": "1.5"
}

Topics

  • CLI
  • deno
  • deno-deploy
  • deployment
  • environment-variables
  • kv
  • custom-domains
  • production

README badge

README badge for denoland/skills/deno-deploy

What it does

Guides deployment of Deno applications to Deno Deploy using the `deno deploy` CLI (requires Deno >= 2.4.2). Covers app creation, production and preview deploys, environment variables across contexts, KV database provisioning, and the `--tunnel` flag for local development.

Generated from the current SKILL.md.

Frequently asked

Does this skill cover the deprecated `deployctl` command?
No. This skill uses only the modern `deno deploy` command (requires Deno >= 2.4.2). The `deployctl` command is deprecated and not covered.
Can I use this skill to deploy to other platforms like Vercel or AWS Lambda?
No. This skill applies only to Deno Deploy. For other platforms, use their platform-specific guidance directly.
What should I do if my app connects to a database at startup?
Create the app with `--no-wait`, provision and assign the database with `deno deploy database` commands, then redeploy so the database exists before warmup.
Do I need to add configuration to deno.json before deploying?
Only if you have an existing app on Deno Deploy. For new apps, `deno deploy create` sets up the config automatically. For subsequent deploys, `deno deploy --prod` uses the stored org and app names.
How do I set different environment variables for production and preview deployments?
Deno Deploy supports separate contexts: Production (live traffic), Development (previews), and Build (during builds). You can set different values for the same variable in each context using the CLI.

Generated from the current SKILL.md. These answers refresh after source changes.