 we’ve received this year is for persistent storage. Users are asking to persist data between deploys — essentially to deploy 

 database on Railway using a combination of a service and a persistent volume.

Well that day has come! We’re officially launching Volumes into Priority Boarding today.

Add a new volume to a service and start writing to persistent disk

Volumes is a feature that allows you to store persistent data for services on Railway — think any kind of service that requires file storage, like a CMS, SQLite, running your own S3-like object storage, etc.

We’ve introduced a trio of templates to help you get started:

To start using Volumes, create a new volume by right-clicking a service or using the Command Palette (

). You’ll then be asked to select the size of the volume as well as the directory to mount the volume to.

After that, you’ll be able to access your volume at the specified target. Easy! 

 and you’ll only be charged for the amount of storage you use. During Priority Boarding, the limits will be set at 1 GB for users and 20 GB for teams. Pricing and limits are subject to change in the future.

And let us know your feedback in the Priority Boarding channel in 

Add multiple webhooks from the Webhooks section of Project Settings

If you need to emit webhooks to multiple destinations, you’re now in luck!

We’ve turned on multi-destination webhooks in Project Settings, which means you can start firing webhooks to any destination that you’d like to notify of your application deployment status changes.

We fixed a bug that sometimes caused erratic log refresh behavior when resuming log subscriptions

 and are getting closer to being able to show them off

https://res.cloudinary.com/railway/image/upload/v1687568373/volumes-pb_pqxk4e.png

Volumes to Priority Boarding, Multiple Webhooks

Changelog #0139