The devil is in the details
Have you ever wanted to automate Virtualbox VM’s using the vboxapi Python bindings? Then you might have also read the SDK documentation PDF (e.g. for 5.1.4 here). There are just some few lines on working with Python and sometimes not everything seems clear (at least not to me). So in this post I show some sample which provided me some troubles while working on a project lately.
Some time ago I wrote a blog post about exporting FitBit fitness data into a Sqlite3 database or exporting it as a CSV file for further processing. This was done using a simple Node.js javascript script called “fitbit_dumper”. The original dumper used OAuth version 1 to access the FitBit API.
Since 2016 the FitBit API is only accessible using OAuth2. So this post describes the differences to the original post.
[Read more…]
Sometimes you need a component for a project or some tests and there is no or at least no free implementation available. This happens to me when I wanted to translate a geographically position (lat/lon) into a corresponding service URN. RFC 5222 provides more information on that. After reading the RFC which looked not that complicated I decided to implement such a server myself. The goal was also that it should be lightweigt, easy to develop and to deploy into the cloud. So it was obvious to me that node.js and mongodb will be used.
[Read more…]
While working on a project which uses some Google API’s I came across Googles API registry. Under https://www.googleapis.com/discovery/v1/apis/ all API’s for Google services like Google Drive or Gmail are described. More infos can be found at the Google APIs Discovery Service page. From the API registry a client could discover services and automatically build proxy classes and methods based on the provided metadata. Thats what I have done for Pharo Smalltalk. Other companies like Microsoft also provide some form of service discovery for their service API’s (see https://msdn.microsoft.com/en-us/office/office365/api/discovery-service-rest-operations)
If you are using one of FitBit’s fitness tracker devices like the ‘One’ for some time you create a lot of data. When you synchronize your tracker all recorded data is sent to FitBit’s servers. The FitBit portal provides some features for graphically displaying and analyzing your data. It’s also possible to export it manually as CSV to process it further. But what if you want your data locally available without manual export to make own statistics. This is what the ‘fitbit_dumper’ is for.
Update: Since 2016 FitBit uses OAuth2. See this blog post for an update.
rss
atom