Skip to content
All releases

Catch a bad resource limit before it stalls your deploy

Release 11 Jul 30 to Aug 5

A small week with one fix that saves a confusing afternoon. Settings for apps on your own cloud now refuse a CPU or memory limit that sits below its request, and saving a change ends with a clearer confirmation.

A limit below its request is refused on the field

On your own cloud, a CPU or memory limit set below its request shows an error on the field and blocks the save, instead of leaving the deployment stuck on Deploying.

On your own cloud, the request is the guaranteed floor and the limit is the ceiling the container cannot exceed, so the limit has to be at least the request. The Resources section on the Settings tab checks this as you type, for both CPU and memory.

Configuration docs

More in this release

  • Save ends with a check mark. When you save changes on a settings tab, the save bar ends with a slide-to-confirm animation that flips to a check.

Deploy your first app in five minutes.

Push a repo and get a live URL, with no cloud account or config.

$5 of signup credit.