Setting Up

Application distribution is done through the CrabNebula Cloud. To trigger a new build for your application, first you need to prepare your configuration and environment variables:

1. Setup Cloud

   The first step is to sign-in to Cloud in the website, create an organization and an application and store their slugs in the cloudOrgSlug and cloudAppSlug configuration values respectively.

2. API Key

   A Cloud API key is required for the build server to upload your application installers to a new Cloud release. Create a new API key in the Cloud website and set it to the CN_API_KEY environment variable.

3. Updater Signing

   The desktop application updates are shipped through Cloud via the Packager Updater. For security reasons each update bundle is signed with a keypair you must own. Run the taurify keypair generate command and safely store the private key and password. The private key and its password must be provided in the PRIVATE_KEY and PRIVATE_KEY_PASSWORD environment variables, and the public key is stored in the taurify.json file.

   Caution

   A keypair is generated when you execute taurify init. Running the taurify keypair generate command overwrites it and can be used when you need to rotate the key.

   Tip

   To rotate the keypair, generate a new one with taurify keypair generate to update the app public key used to verify future updates, but use the previous private key to trigger the next build, so the existing application can verify it as a valid update.

4. App Icon

   Your application icon can be provided in the icon configuration option. Taurify automatically generates icons in the appropriate sizes and formats for all platforms.

To trigger a new release, run taurify build. For platform-specific configuration and code signing, see the following guides.

macOS Distribute macOS applications

Windows Distribute Windows applications

Linux Distribute Linux applications

Android Distribute Android applications to Google Play

iOS Distribute iOS applications to the App Store