<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>1p Development ApS</title>
    <description>Thoughts of a freelance consultant, moving his way through the IT industry.
</description>
    <link>https://1pdevelopment.com/</link>
    <atom:link href="https://1pdevelopment.com/feed.xml" rel="self" type="application/rss+xml" />
    <pubDate>Mon, 16 May 2016 19:35:19 +0000</pubDate>
    <lastBuildDate>Mon, 16 May 2016 19:35:19 +0000</lastBuildDate>
    <generator>Jekyll v3.0.5</generator>
    
      <item>
        <title>Golang and time series databases - an explorative journey</title>
        <description>&lt;p&gt;Lately I’ve been reading and hearing a lot about time series databases, which seem to blossom up in various solutions. These types of databases are a nice fit to actually start using these in a small project, I’ve been nursing the last months in my head.&lt;/p&gt;

&lt;p&gt;I live in a home with numerous “smart home” devices like &lt;a href=&quot;https://www.netatmo.com/en-US/product/weather-station&quot;&gt;netatmo weather-station&lt;/a&gt;, &lt;a href=&quot;http://www.smappee.com/be_en/energy-monitor&quot;&gt;smappee energy-monitor&lt;/a&gt;, &lt;a href=&quot;http://homeowners.danfoss.dk/products/link/home/&quot;&gt;Danfoss Living&lt;/a&gt;, &lt;a href=&quot;https://www.elgato.com/en/eve/eve-energy&quot;&gt;Elgato Eve Energy&lt;/a&gt;. One thing that strikes me over and over again, is the diversity in how these appliances expose their data. Some of them sure has nice looking apps and web ui’s while other really lack this usability. One thing most of them have in common, is the exposure of some good APIs.
Data-points from all these devices are actually just plain time series, which can give hours of fun if accessible in an easy way.
This leads me to the small project I will start out in a 3 part blog series; collecting and visualizing time series using a time series database.&lt;/p&gt;

&lt;p&gt;As I’m doing this on a hobby basis, it’s important to me that I besides having fun also develop my personal skill set. Therefore I will move into a new language, namely &lt;a href=&quot;https://golang.org&quot;&gt;Golang&lt;/a&gt; and try out new products like [influxdb][influxdb].&lt;/p&gt;

&lt;p&gt;The series will be diveded into the before mentioned parts.&lt;/p&gt;

&lt;ol&gt;
  &lt;li&gt;&lt;a href=&quot;https://golang.org&quot;&gt;Golang&lt;/a&gt; and REST calls
    &lt;ul&gt;
      &lt;li&gt;Learning Golang in this post and getting to know how to communicate with REST endpoints.&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Setting up [influxdb][influxdb] and exploring API
    &lt;ul&gt;
      &lt;li&gt;Installation, configuration, API exploration and visualisation tools&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
  &lt;li&gt;Integrating &lt;a href=&quot;http://www.smappee.com/be_en/energy-monitor&quot;&gt;smappee-data&lt;/a&gt; into [influxdb][influxdb]
    &lt;ul&gt;
      &lt;li&gt;Finalising the solution and running it on my home server&lt;/li&gt;
    &lt;/ul&gt;
  &lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The final result should be an automated integration from &lt;a href=&quot;http://www.smappee.com/be_en/energy-monitor&quot;&gt;smappee&lt;/a&gt; to [influxdb][influxdb] and a simple dashboard in a visualisation tool to show the historis energy usage.&lt;/p&gt;

&lt;p&gt;Part 1 will be online in the coming weeks, as I get to learn &lt;a href=&quot;https://golang.org&quot;&gt;golang&lt;/a&gt; and experiment with it.&lt;/p&gt;

</description>
        <pubDate>Mon, 16 May 2016 18:55:07 +0000</pubDate>
        <link>https://1pdevelopment.com/go/influxdb/smappee/rest/tsdb/2016/05/16/getting-started-with-go.html</link>
        <guid isPermaLink="true">https://1pdevelopment.com/go/influxdb/smappee/rest/tsdb/2016/05/16/getting-started-with-go.html</guid>
        
        <category>go</category>
        
        <category>influxdb</category>
        
        <category>smappee</category>
        
        <category>rest</category>
        
        <category>tsdb</category>
        
        <category>tutorial</category>
        
        
        <category>go</category>
        
        <category>influxdb</category>
        
        <category>smappee</category>
        
        <category>rest</category>
        
        <category>tsdb</category>
        
      </item>
    
      <item>
        <title>Welcome to ...</title>
        <description>&lt;p&gt;Hi there!&lt;/p&gt;

&lt;p&gt;Welcome to the website, and this first post.
So what is this about ?&lt;br /&gt;
I could write a lot of stuff about why I’ve started this blog, but for now let us focus on the technical &lt;em&gt;why&lt;/em&gt;.
To learn something new, I decided to rewrite my website in Jekyll and host it on &lt;a href=&quot;https://github.com/&quot;&gt;Github&lt;/a&gt;. The result, is what you’re looking at.&lt;/p&gt;

&lt;p&gt;Initially, I had a good read &lt;a href=&quot;https://help.github.com/articles/setting-up-your-pages-site-locally-with-jekyll/&quot;&gt;here&lt;/a&gt;, where the basics of setting you up are described.
With an initial scaffold, I kept reading on the official &lt;a href=&quot;http://jekyllrb.com&quot;&gt;Jekyll documentation&lt;/a&gt; and acquired a good foundation.&lt;/p&gt;

&lt;p&gt;Basically, Jekyll is a static site generator, which renders a website based on templates. I’ve decided to use the Markdown engine for the the templates. A nice cheat sheet can be found &lt;a href=&quot;https://gist.github.com/jonschlinkert/5854601&quot;&gt;here&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;To conclude it all, I pushed my site to &lt;a href=&quot;gh&quot;&gt;Github&lt;/a&gt; and the result is what you’re looking at.&lt;/p&gt;

&lt;p&gt;// Jacob&lt;/p&gt;

</description>
        <pubDate>Sun, 27 Mar 2016 21:00:00 +0000</pubDate>
        <link>https://1pdevelopment.com/jekyll/update/2016/03/27/welcome-to-jekyll.html</link>
        <guid isPermaLink="true">https://1pdevelopment.com/jekyll/update/2016/03/27/welcome-to-jekyll.html</guid>
        
        <category>jekyll</category>
        
        <category>update</category>
        
        <category>markdown</category>
        
        
        <category>jekyll</category>
        
        <category>update</category>
        
      </item>
    
  </channel>
</rss>
