<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Flask on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/flask/</link>
        <description>Recent content in Flask on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Tue, 16 May 2017 14:55:50 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/flask/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>[resinOS] Dockerize your own Flask GUI with resinOS</title>
            <link>https://www.nico-maas.de/posts/2017-05-16-resinos-dockerize-your-own-flask-gui-with-resinos/</link>
            <pubDate>Tue, 16 May 2017 14:55:50 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2017-05-16-resinos-dockerize-your-own-flask-gui-with-resinos/</guid>
            <description>&lt;p&gt;I have been working with Docker and &lt;a class=&#34;link&#34; href=&#34;http://resin.io&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;resin.io&lt;/a&gt; as well as &lt;a class=&#34;link&#34; href=&#34;http://resinos.io&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;resinOS&lt;/a&gt; for quite some time now and I am actively using those services actively for different projects: The possibility to just throw away a container and build it anew in record breaking time is just awesome and also the fact that I can now just ship images to some device, deploy it there - and it will just work. As some of you know, I am working as volunteer in different NPOs, i.e. the RepairCafé Trier in which I repair Computers and Mobile phones for free, the PiAndMore / CMD e.V. on which I teach interessted guys and gals about Raspberry Pi and Linux (and even did two presentations on &lt;a class=&#34;link&#34; href=&#34;https://www.nico-maas.de/posts/2016-06-12-piandmore-resin-io-presentation/&#34; &gt;resin.io&lt;/a&gt; and &lt;a class=&#34;link&#34; href=&#34;https://www.nico-maas.de/posts/2017-01-14-piandmore-resinos-presentation/&#34; &gt;resinOS&lt;/a&gt;, both linked on this blog - and as &lt;a class=&#34;link&#34; href=&#34;https://www.nico-maas.de/videos&#34; &gt;video&lt;/a&gt; :)) - and also one other NPO which is trying to give information about Japanese Culture. For those events I already created an Tickting System called JCTixx, which uses QR Codes to sell and check tickets for those named festivals. However, I created the Scanner Hardware in 2010, just starting my second year in an Apprenticeship as IT Systemselectronics guy, without anything as a Raspberry Pi available. However, being a bit creative, I just took some old Linux routers, threw the good old OpenWRT on those and soldered directly to the its testpoints / CPU to get the GPIO pins I needed ;). That worked very well - however, nowadays, TLS 1.2 and such eat away those small MIPS cores - and I could - with a lot of work - just get them working with said crypto in 2015. However, being 7 years old now, I need new Scanners - and more flexible way of delivery software as well. So resinOS it is! 🙂&lt;/p&gt;</description>
        </item><item>
            <title>[Talk] Docker Grundlagen</title>
            <link>https://www.nico-maas.de/posts/2016-06-04-talk-docker-grundlagen/</link>
            <pubDate>Sat, 04 Jun 2016 20:55:22 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-06-04-talk-docker-grundlagen/</guid>
            <description>&lt;p&gt;My Docker 101 presentation @ SaarCamp 2016 (04.06.2016).&lt;/p&gt;&#xA;&lt;p&gt;&lt;a class=&#34;link&#34; href=&#34;Docker_Saarcamp2016.pdf&#34; &gt;Docker_Saarcamp2016.pdf&lt;/a&gt; (0,56 MB, PDF).&lt;/p&gt;&#xA;&lt;p&gt;Sourcecode / Example can be found on &lt;a class=&#34;link&#34; href=&#34;https://github.com/nmaas87/docker-demo&#34;  target=&#34;_blank&#34; rel=&#34;noopener&#34;&#xA;    &gt;https://github.com/nmaas87/docker-demo&lt;/a&gt;&lt;/p&gt;</description>
        </item></channel>
</rss>
