October was primarily about clean-up and sweeping behind the scenes. We are in the middle of transitioning some infrastructure software to a new thing.
Unfortunately the old thing was deprecated and gets no love from the vendor anymore. And the new thing is exactly the same with new syntax and new unknown bugs included.
It’s particularly fun to write about these things (note sarcasm) because all it comes down to: we did maintenance and it took a long time. And I want to talk about features instead. But it is what it is: an unhealthy obsession of the industry to constantly reinvent itself with little gain for the user.
Yes, we did a little bit of this and a little bit of that.
First off: new quota visualizations. They are now part of the dashboard as well and show you your quota usage and also this month’s damage (cost). We are slowly working through these as time permits, so there are a few more things to come. Bottom line: cloud billing can be hard, not with Runway — you see what you pay for.
We build Runway for ourselves and when you build something, you naturally know the ins and outs and all the little things to overcome. So on that note: when we released Runway, we had each app pretty locked down — best practices etc.
Since the apps were a bit too locked down, the first experience was often having to fix something to make an app run and prevent it from crashing — most notably due to writable files. Of course writing files in a container is not just a bad practice, it’s also a security problem and goes against the philosophy of containers being immutable.
But we want you to see why Runway is great and that includes optimizing for the first deploy experience as well. So starting now, all apps come with a writable filesystem by default and once you are ready, you can enable lockdown mode to tighten security and sleep better at night.
Read more about lockdown mode in our docs and try it out:
runway app lockdown on/off
And that’s it for the month of October. :) Thanks for reading and following along!