v0.1.0 - 21/03/25

March 21, 2025

This update introduces several new features and improvements aimed at enhancing deployment capabilities and user experience. Key features include support for deploying Docker containers, improved DNS routing options, and embedded user guides. Enhancements focus on expanded logging functions, decoupled ingress management for flexible deployments, and enhanced error messaging for ESM projects. Additionally, navigation within the project settings is streamlined. Bug fixes are addressed to improve overall system stability and functionality.

New Features

Docker containers: Deploy any docker container application. It is automatically put behind a CDN, given an SSL certificate, and configured for horizontal autoscaling.
DNS Routing: After routing your domain to the sherpa.sh nameservers you can create and manage your DNS records from the domain detail page.
Manual DNS Routing: If you cannot route your nameservers to sherpa, you can now manually create CNAME records on your provider to route your domain to your sherpa.sh project.
We've created our first training video. These will be embedded in the site to improve the experience and help users.

Improvements

ESM projects with build errors now have more verbose messaging
Logging is moved to its own dedicated page instead of living under each deployment. View the CDN logs as well as your application console output.
Backend change: Decoupled ingress from deployments. This gives us greater control and flexibility in managing routes and unlocks more complicated deployment strategies. Whenever you change your domain settings, the new url will automatically be generated and applied to your application.
Add logging and deployment links to the sidebars in project settings, as well as in the individual deployment detail pages. This makes navigation easier.

Bug Fixes

When changing an application framework (from nextjs to docker for example) those changes broke the connection between logs and the deployment. This is fixed.
Branch deployment links not being saved and linked to the GUI despite being deployed. This is fixed.
In some instances deployments were not getting their preview / production badges tagged appropriately due to a race condition. This prevented rollbacks as well as log monitoring. This is now patched.
CommonJS projects not utilizing cjs file extensions for the next config file would result in a build error. This has been patch, and now CommonJS projects support all valid extension types (cjs, js, ts)
Fix environment variable bug where you cannot save if one of the env keys has an invalid character.
Fix Github integration where some projects won't receive active links on the the PR comment.
Branches with "/" or "." would cause URL errors on ingress controllers. We now replace non-compatible characters in branch names with urls to hyphens to make url compatible. And any periods are replaced with hyphens as well so the branch name is all a single subdomain compatible with the wildcard SSL cert.
Ignore eslint and other type/format checkers in our custom cache handler and next config files when compiling.
Only allow root domains in the new domain form. Limit to 63 characters per part to comply with RFC 1035

Previousv0.2.0 - 27/03/25

Last updated 13 days ago

New Features

Docker containers: Deploy any docker container application. It is automatically put behind a CDN, given an SSL certificate, and configured for horizontal autoscaling.

DNS Routing: After routing your domain to the sherpa.sh nameservers you can create and manage your DNS records from the domain detail page.

Manual DNS Routing: If you cannot route your nameservers to sherpa, you can now manually create CNAME records on your provider to route your domain to your sherpa.sh project.

We've created our first training video. These will be embedded in the site to improve the experience and help users.

Improvements

ESM projects with build errors now have more verbose messaging

Logging is moved to its own dedicated page instead of living under each deployment. View the CDN logs as well as your application console output.

Backend change: Decoupled ingress from deployments. This gives us greater control and flexibility in managing routes and unlocks more complicated deployment strategies. Whenever you change your domain settings, the new url will automatically be generated and applied to your application.

Add logging and deployment links to the sidebars in project settings, as well as in the individual deployment detail pages. This makes navigation easier.

Bug Fixes

When changing an application framework (from nextjs to docker for example) those changes broke the connection between logs and the deployment. This is fixed.

Branch deployment links not being saved and linked to the GUI despite being deployed. This is fixed.

In some instances deployments were not getting their preview / production badges tagged appropriately due to a race condition. This prevented rollbacks as well as log monitoring. This is now patched.

CommonJS projects not utilizing cjs file extensions for the next config file would result in a build error. This has been patch, and now CommonJS projects support all valid extension types (cjs, js, ts)

Fix environment variable bug where you cannot save if one of the env keys has an invalid character.

Fix Github integration where some projects won't receive active links on the the PR comment.

Branches with "/" or "." would cause URL errors on ingress controllers. We now replace non-compatible characters in branch names with urls to hyphens to make url compatible. And any periods are replaced with hyphens as well so the branch name is all a single subdomain compatible with the wildcard SSL cert.

Ignore eslint and other type/format checkers in our custom cache handler and next config files when compiling.

Only allow root domains in the new domain form. Limit to 63 characters per part to comply with RFC 1035