Support pushing the webserver to fly.io instead of heroku#919
Support pushing the webserver to fly.io instead of heroku#919tresni wants to merge 1 commit intojson-path:masterfrom
Conversation
|
@tresni thank you for posting this. It was helpful to see what the server actually uses. Things don't work in jsonpath.com vs javainuse, but I see the same issues with jsonpath.fly.dev, inconsistent results on what I would expect. I am willing to bet your site is the closest. Is it still the most recent? As an aside, |
|
There have been no updates to JsonPath since I pushed that image to fly.io, so what you see there matches the master branch. The code for the site and everything was already in place, I just put a new deployment method in place., |
|
|
The old jsonpath.herokuapp.com appears to have gone offline when Heroku discontinued free services. Fly.io still offers a basic free service that is perfect for running this app.
I've set that up an organization on fly.io that I'm happy to move over to someone elses control. The benefit is that it has the domain https://jsonpath.fly.dev mirroring as close as possible the old herokuapp.com domain.