What’s good, what’s good, what’s good, the people?
This week is HUGE, we have A LOT to share, maybe even a WHALE-SIZED amount to share … shall we get into it?
Ok, let’s get into it then!
Deploy Docker Images to Priority Boarding
Priority Boarding users can now deploy an image directly from DockerHub or from GitHub GHCR!
That’s right, we’re talking ANY Docker image, running on Railway, right now (as long as you’re in Priority Boarding).
To get started, try creating a new service from a Docker image by opening the the command palette (CMD + K) and selecting Docker Image.
You can also connect to a Docker Hub image via the service settings.
Templates, like this MinIO one, also support Docker images as sources.
Some caveats:
- Only public images from DockerHub and GHCR are supported at this time
- You can only connect to the service with the public url over HTTP. This will limit the ability to deploy images like Postgres and connect to them externally. However, you can connect with any protocol via private networking
- You will not be able to listen for changes to the image
We are hoping that this opens up a whole new world of use cases on Railway and we can’t wait to see what you do with it.
As always please provide feedback by reaching out on Discord and letting us know what you think.
Welcome to the $5 Plan
On Monday we started rolling out the $5 plan which is something we’re super excited about. If you’re a current Railway subscriber, you should have received an email letting you know all about the new updates, but in case you missed them, we wrote a couple of blogposts to help you get acclimated:
If you run into trouble with the migration that you can’t solve on your own, send us a note and we’ll do our best to help you out.
Thanks!
Increased Volumes Limits
Due to popular demand, we’ve updated how the Volumes feature works on Railway. You no longer need to select the max size when creating a volume. Every volume can use the maximum amount of size depending on the plan AND we’ve also increased these limits as follows:
- Hobby plan: 5GB
- Pro plan: 50GB
We hope this makes using Volumes on Railway even smoother and more straightforward.
Be sure to read the docs for more information. And if a use case is not covered by these updates, please don’t hesitate to leave feedback — where? You guessed it. Discord.
See you over there.
Speedups
Want to see something crazy?
Railway Engineers Alberto and Greg were able to shave off some SERIOUS time from a whole bunch of db queries. We’re talking things that used to take ~4s - 5s now take ~200ms.
What this means for you is that you should now see a whole bunch of speed improvements in the Dashboard on a whole range of queries, like listing deployments, opening projects … pretty much everything that queries the database.
If you think we should write a blogpost about this … well, you’re right! We should. We’ll do that. Thank you.
Meanwhile please enjoy the turbocharged Dashboard. 🏄
Improvements and Fixes
- Nixpacks has been upgraded to v1.10 and now supports the Python PDM package manager. (Thanks buuro!)
- We fixed a bug with the template kickback workflow
- We fixed an issue with troublesome restart policies
- We fixed a visual bug with the services layout
- We fixed an issue with GitHub rate limiting Railway users while logging in
- We fixed an issue with team invites