Search results

I fixed an issue with the www subdomain, that might caused the issue you saw.

Ah, right you are!

Odd: At any rate, this is a client-side display issue and not a fundamental flaw in the data we are getting from Amtrak (thankfully). The route list is broken, however: This makes me wonder if @tikkisean is accidently caching the routes from past searches (the Pacific Surfliner makes no sense...

I'm not seeing any issues in the logs. It's possible that you tried to use it during the five minutes of downtime I needed to update the Docker images. This seems to work:

So far, this has not been the case! Searching for a single trip is bugged if Round Trip is selected, as it is impossible for Railforless to find a round-trip pairing for two LD trips on the same day (that is, it is impossible to leave CHI on the Chief on 09/04 and also return to CHI on the...

Given the hype surrounding the TCMC train and that I live near MSP, I'm tempted to book tickets and ride it from MSP to CHI to celebrate it! (Maybe even do a little RailForLess meetup 😀).

@trimetbusfan I've had similar issues on mobile - the UI is @tikkisean's department so I will leave that to him to work out. As for specific searches that failed, do you mean that they failed after multiple retries or did they fail after a single attempt? The former would suggest an edge case...

Over the past 6 months, we have spent countless hours redesigning RailForLess from the ground up. RailForLess is the spiritual successor to Amsnag, a service which makes planning Amtrak trips much more convenient with flexible scheduling and interactive visualizations. Since last fall, the site...

Check back on March 1st for the official launch of the new version of Railforless!

You should be able to include an image by clicking the "insert image" button at the top of the text editor.

The last time I flew I was only two and a half years old. Trains are all I know. :)

@trimetbusfan This is a step in the right direction but is still limited because it only allows searching one date at a time. I'm still happy to see Google integrating Amtrak data in any form, though. I won't give any expected dates, but Sean and I are both working as fast as our time...

I don't have the old percent full numbers that were removed but I do have precise inventory numbers for each accommodation type, which I think is better anyway.

I have not had major issues with Captcha due to using a different method of accessing the data. We are currently planning on using my API/backend to power Railforless instead of his current method that has Captcha issues (and is slower).

Good to know, I snapped a quick photo of it as I passed the depot on the highway earlier.

I have officially joined forces with RailForLess.us so I can focus on perfecting the backend while Sean, the creator of RailForLess, can focus on frontend. 😀

Well, the September estimate has come and gone. :/

Given that's it's been a month, I decided it was time to post an update. Progress has been slower for a variety of reasons: I've had issues finding a reliable proxy service Amtrak has made this exceedingly difficult by not including the prices of bedrooms and family rooms in the trip response...

The issue is not the cost of licensing but the cost of hosting. Both SQL sever and MySQL are relatively expensive compared to Azure CosmosDb which is a NOSQL service with a (optional) serverless model. So in theory, I will pay virtually nothing to run my database and API because of how generous...

I've had a major breakthrough today - I won't get into details, but it is easily scalable and relatively inexpensive to operate ($35-40/month). I can host the front-end for free with Cloudflare and am looking at Azure Functions as a cheap way of providing a serverless API. The main question mark...