Changelog

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.