Changelog

We’re thrilled to announce that Fermyon Serverless AI is in private beta. Developers can now use Spin to perform AI inferencing and embedding from within serverless Spin applications (that are either running locally or deployed to Fermyon Cloud). You can sign up for the private beta using this short form.

We’re thrilled to announce Fermyon Cloud’s NoOps SQLite Database is now in private beta. Spin developers can now persist relational data generated by their Spin application in a database that is provisioned and managed entirely by Fermyon Cloud on their behalf. No need to worry about database operations, connection strings, or resource management with Fermyon Cloud’s NoOps SQLite Database; we’ve got you covered. We’d love to hear what you think of the experience. You can sign up for the private beta using this short form.

Fermyon Cloud is excited to share that it now supports custom domains. Until today, Spin applications were limited to default randomly generated domain names or custom Fermyon subdomains; however, we heard your feedback that custom domains were essential in bringing blogs and personalized websites to Fermyon Cloud. Using a custom domain name with your Spin application can improve your workload’s SEO, build brand integrity, and improve discoverability. We encourage developers to bring their custom domains to Fermyon Cloud and assign them to their favorite Spin applications. Slats has already gotten a headstart at finickywhiskersdiary.com. Please let us know what you think about the feature at feedback@fermyon.com.

Fermyon Cloud now supports setting application variables through the API. Spin supports dynamic application variables. Instead of being static, their values can be updated without modifying the application, creating a simpler experience for rotating secrets, updating API endpoints, and more. These variables are defined in a Spin application manifest (in the [variables] section) and are provided by a configuration provider.

Now, when your application is deployed to Fermyon Cloud you can set and update variables for it using the spin cloud variables command. You can also set the variables when you initally deploy the application using spin cloud deploy --variables. The spin cloud variables command can also be used to list variables that have been set for an appplication. For a full explanation on how to configure variables and secrets in Spin applications, read the new tutorial.

Fermyon Cloud users can now apply custom Fermyon subdomains to their Spin applications. By default, every Spin application recieves a domain name that has the following format: <app-name>-<randomstring>.fermyon.app. With custom Fermyon subdomains, users can choose their preferred subdomain name to be appended to the .fermyon.app apex domain. To learn more, follow the custom Fermyon subdomain tutorial.

Fermyon Cloud now supports Key Value Store. While Spin applications are well suited for event-driven, stateless workloads, these serverless workloads often rely on external services to persist state beyond the lifespan of a single request. With the introduction of Fermyon Cloud Key Value Store, you can now persist non-relational data in a key/value store that is always available for your serverless application (within milliseconds and without cold starts). No infrastructure provisioning or maintenance is required. Developers can now deploy their Fermyon Cloud Key Value Store applications simply by running spin cloud deploy.

You can now see your Spin application’s request count over time in the Fermyon Cloud User Interface (UI). Request count is defined as the number of times your Spin application’s HTTP trigger has been called while running on Fermyon Cloud. To view an Spin application’s request count data over time, log into Fermyon Cloud and click on the application of interest. Feel free to reach out to us on Discord and let us know what you think.

Fermyon has recently released a collection of GitHub Actions for working with Spin that will empower you to pick up your development speed:

• fermyon/actions/spin/setup - installs the Spin CLI and necessary plugins
• fermyon/actions/spin/push - pushes a Spin application to a registry
• fermyon/actions/spin/deploy - deploys a Spin application to Fermyon Cloud

Using spin/deploy, you can now set up a Continuous Deployment pipeline on Fermyon Cloud. Whenever you merge a pull request into your GitHub repository of choice, spin/deploy will trigger a new Spin application deployment. You can learn more about the set-up for this process with our GitHub Actions tutorial.