Cryptlex Documentation
  • Welcome to Cryptlex!
  • Getting Started
    • Overview
    • Licensing Models
  • License Management
    • License Templates
    • Implementing License Models
    • Custom License Fields
    • Meter Attributes
    • Creating Licenses
    • Renewing Licenses
    • Extending Licenses
    • Suspending Licenses
    • Revoking Licenses
    • Maintenance Policies
  • User Management
    • Roles
    • Creating Users
    • Authenticating Users
    • Organizations
    • Resellers
    • Customer Portal
    • Reseller Portal
    • Google SSO
    • SAML SSO
  • Feature Management
    • Overview
    • Feature Flags and Product Versions
    • Use Cases
    • Creating Product Versions
  • Release Management
    • Overview
    • Creating Releases
    • Distributing Releases
  • Node Locked Licenses
    • Overview
    • Using LexActivator
      • Using LexActivator with C, C++ and Objective C
      • Using LexActivator with C#
      • Using LexActivator with VB.NET
      • Using LexActivator with Java
      • Using LexActivator with Delphi
      • Using LexActivator with Python
      • Using LexActivator with Go
      • Using LexActivator with Node.js
      • Using LexActivator with Ruby
      • Using LexActivator with Android
      • Using LexActivator with iOS
      • Using LexActivator with Flutter
    • Using Web API
    • Offline Activations
    • Proxies and Firewall
  • Floating Licenses
    • Overview
    • Hosted Floating License Server
    • On-Premise Floating Licenses
      • LexFloatServer
      • Using LexFloatClient
        • Using LexFloatClient with C, C++ & Objective C
        • Using LexFloatClient with C#
        • Using LexFloatClient with VB.NET
        • Using LexFloatClient with Java
        • Using LexFloatClient with Delphi
        • Using LexFloatClient with Python
        • Using LexFloatClient with Node.js
        • Using LexFloatClient with Go
        • Using LexFloatClient with Android
        • Using LexFloatClient with iOS
      • Offline Floating License
  • Named User Licenses
  • Timed Trials
    • Verified Trials
    • Unverified Trials
  • Licensing Docker Apps
  • Webhooks
  • Automated Emails
  • Web Integration
    • Personal Access Tokens
    • Using Web API
    • Using Zapier
    • Using FastSpring
    • Custom Development
  • Changelog
    • Web API
    • LexActivator
    • LexFloatClient
    • LexFloatServer
  • Legal
    • Terms of Service
    • Privacy Policy
    • Subprocessors
    • Data Processing Addendum
    • Service Level Agreement
    • Security, Privacy, and Compliance
    • Open Source Licenses
  • Cryptlex On-Premise
    • Overview
    • System Requirements
    • Server Layout
    • Installation Guide
      • Docker Compose
      • Kubernetes
    • Configuring Client Libraries
    • Monitoring and Error Reporting
Powered by GitBook
On this page
  • Creating a release
  • Uploading release file
  • Adding an external release file
  • Publishing release
  1. Release Management

Creating Releases

Whenever you release a new version of your software, you will need to create a new release in the Cryptlex admin portal (or through Web API). After you create the release, you have to upload your software bundle with the release. You can also host the software bundle on your server.

Creating a release

You can easily create a release through the admin portal. Go to the Releases section in the sidebar and click the Add button. A create release form with the following fields will popup:

Name

The name of the release. This can be a user-friendly name to identify the release e.g. MyApp v1.2.

Version

The version format syntax in Cryptlex is $MAJOR.$MINOR.$PATCH.$BUILD. So, only the following three formats are allowed:

  • x.x - $MAJOR.$MINOR

  • x.x.x - $MAJOR.$MINOR.$PATCH

  • x.x.x.x - $MAJOR.$MINOR.$PATCH.$BUILD

It must only contain dot-separated digits e.g. 1.2, 1.2.3, 1.2.3.4, etc.

Platforms

The platforms of the release. It will usually have any of the following values: windows, linux, macos, win32, win64, etc.

Channel

The channel of the release. The default value is stable. You can use it to differentiate between alpha, beta, RC, stable, etc. release types.

Notes

Uploading release file

In the create release form you need to upload the release files too which need to be distributed securely to your licensed users.

The release file can also be uploaded using any command-line HTTP client like curl. To upload the release file using curl execute the following command:

curl -X PUT https://releases.cryptlex.com/v3/{RELEASE_ID}/myapp.zip \
     -H "Authorization: Bearer {ACCESS_TOKEN}" \
     -T "/path/to/myapp.zip"

# In case you are using Cryptlex On-Premise then use following instead
curl -X PUT https://releases.mycompany.com/v3/{RELEASE_ID}/myapp.zip \
     -H "Authorization: Bearer {ACCESS_TOKEN}" \
     -F "file=@/path/to/myapp.zip"

The access token must have at least the following two permissions: release:read, release:write.

The file name in the upload URL must only contain letters, numbers and some special characters, including. (period), - (hyphen) and _ (underscore).

Adding an external release file

Instead of uploading release files to our server, you can also add the release files hosted on your server.

To add the external release files click the Add External File option in the actions menu. Put in the details of your external release file in the form and click the Add File button. After that, you can see the entry in the Files column of the table.

Publishing release

Once all the changes have been finalized you can click the Publish button to freeze the release. After a release is published it becomes read-only.

PreviousOverviewNextDistributing Releases

Last updated 9 months ago

The release notes for the release. It also supports .

markdown