How to set up development environment for yql and open table development? How to check it locally? (best practice)

Question

I develop - from time to time - open yahoo tables for accessing various resources on the Internet. I am currently using the JavaScript editor, and when I want to check if my open table is working, I upload the description of the xml table to the server to check it with the yql client application. However, this approach is rather slow, and sometimes - I am blocked by yahoo due to an error in the description of the open table. Therefore, I would like to learn about the best practices for testing and developing an open yahoo table locally. What does your setup look like for open table development?

To clarify my question, I'm looking for a convenient way (best practice) to develop and test yql tables, for example, to run the Java Script part inside Rhino .

Answer 1

First of all: I agree that I do not see a really convenient way to test local local YQL definitions. However, here is how I approach this issue.

Github hosting

YQL conditional definitions are often used in very open scripts, for example. when there is an existing API that you want to wrap through YQL. Therefore, I usually work on the YQL community table fork, and I just add my own definitions there. The hosting of the .xml files occurs on github in this case: https://github.com/yql/yql-tables

Another advantage of this approach is that it’s easy for me to share my data with the community if I feel that it can be valuable to others.

Private hosting

A free github account has only free repositories, so everyone can see and use your data. If this is not good for you, you can either buy a github pro account to get private repositories, or post your data yourself.

To do this, you can upload them to your own server, as you already did, or you can also set up a web server, such as Apache, on your computer, and then get a dynamic hostname from dyndns.com or similar so that you can point to this definition from YQL. I have not tried this because github worked well enough for me, but I'm sure it is possible.

Answer 2

Why don't you just put the file you are editing in the Dropbox public folder? This is what I do and it works very well.