Is anyone else having issues using @railway CLI, specifically the `railway ssh` command? Is that something that's still disabled from the incident?
I’ve been overall satisfied with @railway but I’m finding it hard to believe there’s no concept of an application.
In Rails there should be one deployment across all services, and if a deploy fails on one service, the entire deploy should fail.
Railway does not work this way.
Also if the build fails on one service but not your others, it stays running on a your previous build.
As far as I can tell there is no remedy to this offered by Railway and there doesn’t seem to be an appetite to address it either when searching their support community.
I keep seeing them post about infinite/instant possibilities with all of the shiny Al features they are building, but to me none of that matters if I can’t trust my deployments to be properly handled.
Anyone know how to get this rolling on desktop? What's written to settings.json?
I’m now at over 12 hours of having @render without warning or recourse suspend my account. I had both of my production apps full speed ahead and was actually quite happy with the service. I emailed them, the only option they gave me, and have yet to hear back.
Enter @Railway to save the day. With a little help from my buddy Claude and their CLI I was able to migrate both apps and be back online within an hour.
I already hosted our databases with a third party, which made the switch much easier.
Kyle Keesling retweeted
nothing has caused as much internal rage this past week than what @amazon did to their delivery emails.
my hope and prayer is that whoever made this decision stumps their big toe an uncountable number of times today.
Is it me or does it seem pretty silly to be butt-hurt that they keep extending Fable usage?
What can you honestly be doing that would change so drastically based on you having Opus 4.8 versus Fable.










