using-crabnebula-cloud-with-tauri

Configures Tauri application distribution via CrabNebula Cloud with CI/CD releases and auto-updates.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/dt418/better-shot-x --skill using-crabnebula-cloud-with-tauri-dt418
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-crabnebula-cloud-with-tauri
Source: https://github.com/dt418/better-shot-x/tree/main/.agents/skills/using-crabnebula-cloud-with-tauri
Command: npx skills add https://github.com/dt418/better-shot-x --skill using-crabnebula-cloud-with-tauri-dt418

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Distributing Tauri desktop applications and wiring up auto-updates requires coordinating release pipelines, signing keys, updater endpoints, and CI workflows, which is error-prone when done manually. ## Core Features & Use Cases - Release Pipeline Setup: Walks through CrabNebula Cloud account creation, API key generation, CLI installation, and the draft-upload-publish release workflow. - GitHub Actions CI/CD: Provides a complete multi-platform workflow (Linux, macOS, Windows) that builds Tauri bundles and uploads them to CrabNebula Cloud. - Auto-Update Integration: Covers signing key generation, tauri.conf.json updater endpoints, capabilities, Rust plugin registration, and a TypeScript update-check implementation. - Use Case: A team shipping a Tauri 2 desktop app uses this Skill to configure a GitHub Actions release pipeline that publishes signed builds to CrabNebula Cloud and delivers automatic updates to users on the stable channel. ## Quick Start Set up CrabNebula Cloud distribution with auto-updates for my Tauri application, including the GitHub Actions release workflow.

Frequently Asked Questions about using-crabnebula-cloud-with-tauri

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I distribute a Tauri app with CrabNebula Cloud?

Create a CrabNebula Cloud organization and application, generate an API key, then use the cn CLI or the cloud-release GitHub Action to draft, upload, and publish releases. The upload command with --framework tauri auto-detects Tauri bundles.

How to set up auto-updates in a Tauri 2 application?

Generate signing keys with cargo tauri signer generate, enable createUpdaterArtifacts in tauri.conf.json, and point the updater plugin endpoint at your CrabNebula Cloud URL. Then register tauri-plugin-updater in Rust and call check() from the frontend.

Does CrabNebula Cloud support multiple release channels?

Yes, CrabNebula Cloud supports channels like stable, beta, and nightly via the --channel flag on draft and upload commands. Alternatively, you can create separate applications per channel with distinct update endpoints.

Why does my Tauri update check fail with CrabNebula Cloud?

Update checks fail when the endpoint URL does not match your organization and app slugs, the public key in tauri.conf.json mismatches the signing key, or createUpdaterArtifacts is not enabled. Also verify capabilities include updater and process permissions.

What secrets are needed for the Tauri CrabNebula GitHub Actions workflow?

The workflow requires CN_API_KEY for CrabNebula Cloud authentication, plus TAURI_SIGNING_PRIVATE_KEY and TAURI_SIGNING_PRIVATE_KEY_PASSWORD for signing updater artifacts. Store them as repository secrets, not environment secrets, to avoid log exposure.