Announcements, Development

teowaki Developers Centre

You have heard me say —probably many times— teowaki has a nice, usable, RESTful API. But you had to trust me on that, because we hadn’t had the time to document it properly.

From today you don’t need to trust me anymore, since you can play with the API by yourself following the documentation we have published at teowaki Developers Centre.

If you are already familiar with REST, you can proceed directly to our API overview, or to our hypermedia documentation. If you want to know more about REST you can try the REST basic concepts tutorial. And if you like APIs, you probably want to take a look at our Developer Tools section.

A few examples from our API using cURL from the command line:

Get the public contents about redis
curl -H "accept:application/json" https://api.teowaki.com/search?q=redis

Get the profile of the user Ada
curl -H "accept:application/json" "https://api.teowaki.com/people/ada"

Or directly from your browser:

https://api.teowaki.com/search.json?q=redis
https://api.teowaki.com/people/ada.json

If you want to access private contents, you will need to Authenticate using OAuth2 first. But with the OAuth2 intro in the Developers Centre that should be a breeze.

Give it a try, and tell us about all the awesome things you are building with it at hello@teowaki.com or @teowaki. We will feature in our blog the coolest uses of the API.

Advertisements
Standard
Announcements, Development

Announcing our engineering blog

Teowaki is a tool for developers. And it’s done by developers. So it was the high time to start writing about the technology that powers teowaki. I am proud to announce today teowaki’s engineering blog.

In the first post Diego tells us how he upgrades our servers with Ansible. Stay tuned for insights, tricks and new posts on how we use NoSQL, big data, AngularJS, hypermedia APIs, cloud services and everything that keeps teowaki up and running.

We hope you will enjoy our new blog as much as we enjoy writing it.

If you have any suggestions for new articles or you want to be featured as a guest engineer please write us at engineering@teowaki.com

Standard
Announcements, Development

Get hooked to the web

The internet is a busy place. As a developer you need to check a lot of services to know what’s going on with your teams. Has anyone pushed new changes to my repositories? Did my boss enter any new tasks for me? Have my latest changes broken the build? Keeping up to date is time consuming. Wouldn’t it be great to see all your updates on a single feed? We thought so.

Yesterday we released teowaki’s webhooks. You can listen to events happening elsewhere in the internet and show them in your team stream. Click on an event to see the details or navigate directly to the page where the event happened. You can even use teowaki’s to search through your received webhooks.

webhooks_stream

You don’t need to do anything special to start receiving webhooks. All you need is your team’s secret URL. Go to the list of teams and click on the team settings icon of any team you admin. You will notice a new section called Webhooks. In that section you will find a secret URL for your project, such as

incoming_uri

At the moment we have integrated GitHub, Pivotal Tracker and Bitbucket.  Here is what you need to configure on those tools to send webhooks into teowaki:

GitHub

Go to your project settings and navigate to the Settings menu. Select the Webhooks & Services option and simply paste your teowaki’s secret URL into the Payload URL input box*.

github

Bitbucket

Click on the Settings icon of your project and then select the Hooks option. From the dropdown list of integrations choose POST and simply paste your teowaki’s secret URL into the URL input box.

Bitbucket

Pivotal Tracker

Select Configure integrations from the Project menu. Scroll down to the Activity Web Hook section and simply paste your teowaki’s secret URL into the input box.

PivotalTracker

Getting Hooks from any other service

If you want to send webhooks into your project from any other service, all you need to do is POST a XML, JSON or x-www-form-urlencoded request to your secret endpoint. The POST should include at least a field called name and a field called description. You can also send a field called url and a field called origin_name. As long as your POST contains those field, teowaki will display the information into your team stream.

The use cases for custom webhooks are endless.  As an idea, you can send webhooks from scripts running in your servers every time a new version is deployed or a service is restarted. Everybody in your team will receive the notification on teowaki.

Future integrations

We are already working on integrations for Jira and Trello. We will keep adding new services we think are interesting for developers. If you are using teowaki and you are missing any integrations, please let us know.

For any suggestions or any questions you might have, we are always available at hello@teowaki.com

* at the moment we only recognise GitHub push events. We will be adding more GitHub events in the following weeks

Standard
Community, Development

How we are using redis, as shown at Arrrrcamp

Last week I had the privilege of speaking at arrrrcamp 2013, an amazing conference for Ruby, Rails, Radiant and Rum. I met a lot of fascinating developers, listened to many inspiring talks and had  a great time in Ghent. If you still haven’t attended any edition of Arrrrcamp, save the date for next year.

My contribution to the conference, was an introductory talk to redis and how you can use it when building your ruby applications. For the first minutes I gave a quick overview of redis, explaining the key features and passing very quickly over a few commands so people could get a taste of how it feels working with it. Then I proceeded to explain how other people are successfully using redis (twitter, pinterest, viacom and openredis) and how some companies misused it and got into production issues (instagram and twilio). Finally I explained our use cases of redis in teowaki, which cover aspects such as background processing, API analytics, generating sequences, removing duplication from lists, calculating API usage quotas, or detecting duplicate values.

You can find the slides of my talk below. They are better understood with the video, so I’ll update this post as soon as the awesome arrrrcamp organizers make it available.

Thanks to everyone involved in organizing arrrrcamp and a warm greeting for everyone I met over there. I hope to see you all soon!

Standard