search

cubehouse / themeparks

Unofficial API for accessing ride wait times and schedules for Disneyland, Disney World, Universal Studios, and many more parks
MIT License
536 stars 126 forks source link

Documentation to create a REST from this api #286

Open buutqn opened 4 years ago

buutqn commented 4 years ago

If there is anything about this, i couldn't find.

I know about nothing of Node.js but I installed, followed the code in the README.md and it worked as a charm, but about accessing multiple parks in a nodejs server on localhost? Damn, thats hard for someone that don't know how Node.js works.

It would be nice if there was some documentation on how to create an REST from this api in docs folder.

migo315 commented 4 years ago

There are multiple ways to get the waiting times. One solution would be to save the waiting times in a database and create an application (php, node or whatever) to fetch the data from the database.

Or create an AWS lambda REST API which fetch the waiting times on every request.

If you don't want to create the solution yourself, check coaster.cloud / Fetching waiting times.

cubehouse commented 4 years ago

A "best practices" guide would be useful, but I don't really know where that example should sit between teaching people how to program, and how to build a specific web application correctly. Neither of these really sit within the scope of this library.

Already hosted solutions are probably a good direction if you are not familiar with the technologies involved, since you can use whatever language you are already well experienced with.

buutqn commented 4 years ago

A "best practices" guide would be useful, but I don't really know where that example should sit between teaching people how to program, and how to build a specific web application correctly. Neither of these really sit within the scope of this library.

Already hosted solutions are probably a good direction if you are not familiar with the technologies involved, since you can use whatever language you are already well experienced with.

No no no, i'm sorry if i sound something like that. What i was trying to say was have more documentation about that side, "using it as a rest", but not how to teach. Just a little more examples...