-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local development version installation? #14
Comments
+1 would love to see a step by step setup for APis.io at some point. ;-) |
Vagrant or alike would be nice :) |
Is the idea to have one big apis.io used globally or is there possibly distributed approach in the long run? Having multiple apis.io services around and information harvested much like in Open Data CKAN systems seems interesting (to me). |
Tried...
kyyberi@kyyberi:~/Github/apis.io$ meteor => Started proxy. |
hey @kyyberi You are right, I should have published a step-by-step tutorial on how to deploy your own apis.io locally. To solve your problem you should put your on keys in the a Keen is http://keen.io for analytics I should also explain how to disable all of those in your local stuff. Let me know if it works. |
Thanks, I'll try this again later this week. |
Ok. Copied the tempate to "settings.json" and added ID imformation for each service. Then I ran "meteor", and meteor updates kicked in. After the update I'm getting kyyberi@kyyberi:~/Github/apis.io$ meteor => Started proxy. So far I haven't been able to run server at local host. I believe that the current error is due to update of meteor. |
Did you run That might help. |
Hi, I am seeing the following errors after updating the keys in settings_tpl.json and running meteor update
Any suggestions? |
Unless there's some other software out there for parsing APIs.json manifests, the lack of clear, repeatable steps to deploy this project is a barrier to considering the description format for internal APIs and a number of API brokering use cases. |
Parsing an APIs.json file is totally independent from the APIs.io project. You can use the json-schema schema to parse any APIs.json file and find if it is well formatted. Latest schema is available here apis-json/api-json#56 You can also use http://apis.io/lint to valide any file. We are working on the documentation to make it easier to deploy your own instance of APIs.io search engine. |
I appreciate parsing a clean JSON spec isn't hard, but I expect there are many internal evangelists that would like to roll out some tools for quick wins, and building an app seems like unnecessary friction if there's an open source project that will be more impressive. Maybe I misinterpreted the idea that this is intended for use as a private apis.io instance? |
Hi Adam, Thanks for your concerns--well received. To get where you wish, I think maybe you have to expand your understanding It is a brand new discovery / collection format for APIs. We understand This is why we created APIs.io, which is a public open source search engine. I'm also now working with WSO2 to create an internal, enterprise version of I'm also working on other embeddable, and other supporting tools on my own. I'm also working to generate thousands of APis.json for existing APIs out We fully get that practitioners will need easy to implement tools to make APIs.json + APIs.io is only about 10 months old. We are making progress You can't just snap your fingers and solve a problem like API discovery, Stay in tune, there is a lot coming down the pipes. Kin Lane (API Evangelist) @kinlane https://twitter.com/kinlaneapievangelist.com apistrategyconference.comOn Mon, Feb 9, 2015 at 9:21 AM, Adam Ross notifications@github.com wrote:
|
After updating Meteor to 1.1.0.2.: I'm still getting:
|
I would love to install this version 2 locally for development under apisuomi.fi community. How do I do that? Would it be possible to provide install instructions in the repo?
The text was updated successfully, but these errors were encountered: