August was about rounding off last month’s features — volumes now work with shared apps and services, the Runway CLI moved to a proper Homebrew tap, and runway app logs keeps tailing through a deploy.
Last month we shipped storage expansion for PostgreSQL. This month, volumes learned about sharing: if someone shares an app or service with you, you can now see its volumes too — including additional storage and replicas.
They show up everywhere you’d expect:
runway volume ls
runway app show <app>
runway service show <service>
And on the app and service pages in the UI. Anyone with access can see volumes; resizing stays with the owner, since it incurs charges.
For API users, there are two new endpoints:
/v3/apps/<appname>/volumes
/v3/services/<servicename>/volumes
We consolidated our Homebrew setup into a single tap: hostwithquantum/homebrew-tap. The Runway CLI is now published as a cask:
brew install --cask hostwithquantum/tap/runway
If you installed from the old tap, we added a migration — brew upgrade should move you over. If anything looks off, uninstall and install from the new tap once.
runway app logs sometimes caught a timeout and stopped scrolling when you deployed — quietly, without any error. Thanks for the report! The command now reconnects your app’s logs across deployments, so you can keep a log window open while you ship.
Two fixes around app configuration:
In related news: the release list on the app details page also shows a clearer status for releases that haven’t been deployed yet.
We swapped out the renderer for our API reference — it’s now powered by Scalar. Endpoints are grouped properly and the whole thing is easier to navigate.
While we were at it, our website (www.runway.horse) now shows your login status — no more guessing whether you’re signed in.
Procfiles caused some confusion — when do you need one, and what happens to the web process once you add one? We wrote it down properly.
There’s a new multi-process guide covering the web, init, and worker process types and when each one runs. It comes with language-specific recipes for JavaScript and PHP.
The short version: no Procfile means Runway runs your web server automatically. The moment you add one, declare web in it too.
git push deployments could fail with an “internal error” when your local git offered SSH keys Runway didn’t know about. That’s fixed — and the error messages are clearer now.
A few things you shouldn’t notice, but should know about:
That’s it for August. Give the new bits a spin and let us know what you think — and if you’re new here: Runway runs your apps and managed databases, hosted entirely in the EU.