<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rafał bluszcz Zawadzki on Medium]]></title>
        <description><![CDATA[Stories by Rafał bluszcz Zawadzki on Medium]]></description>
        <link>https://medium.com/@bluszcz?source=rss-1f9a4530caf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*J8C-tA1ptbSUUTt9.png</url>
            <title>Stories by Rafał bluszcz Zawadzki on Medium</title>
            <link>https://medium.com/@bluszcz?source=rss-1f9a4530caf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:23:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bluszcz/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Static Site Generator with Strapi 4 and Jekyll]]></title>
            <link>https://medium.com/@bluszcz/static-site-generator-with-strapi-4-and-jekyll-4c5404cc9715?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c5404cc9715</guid>
            <category><![CDATA[blog]]></category>
            <category><![CDATA[portfolio]]></category>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[jekyll]]></category>
            <category><![CDATA[strapi]]></category>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Wed, 22 Jun 2022 22:01:59 GMT</pubDate>
            <atom:updated>2022-09-03T20:15:09.358Z</atom:updated>
            <content:encoded><![CDATA[<h3>So I guess you heard about Headless CMS?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RHeqkUHc4peW8EbcolHJKw.jpeg" /></figure><p>If you are not familiar with the concept — there is a handy Wikipedia page <a href="https://en.wikipedia.org/wiki/Headless_content_management_system">https://en.wikipedia.org/wiki/Headless_content_management_system</a>. To read about Static Site Generators I do recommend Cloudflare article: <a href="https://www.cloudflare.com/en-gb/learning/performance/static-site-generator/">https://www.cloudflare.com/en-gb/learning/performance/static-site-generator/</a>.</p><p><em>In this article I am going to describe how to use Jekyll as Static Site Generator using Strapi version 4 as Headless CMS backend.</em></p><h4>Requirements</h4><p>To perform exercises described in this article you are going need following:</p><ul><li>Ruby <a href="https://www.ruby-lang.org/en/documentation/installation/">https://www.ruby-lang.org/en/documentation/installation/</a></li><li>Jekyll <a href="https://jekyllrb.com/docs/installation/">https://jekyllrb.com/docs/installation/</a></li><li>NodeJS and npm <a href="https://docs.npmjs.com/downloading-and-installing-node-js-and-npm">https://docs.npmjs.com/downloading-and-installing-node-js-and-npm</a></li><li>Python3 (but you can use any other http server)</li></ul><h3>Current state of jekyll-strapi plugin</h3><p>Whatever you are working on — a blog, a portfolio or a landing page — Strapi and Jekyll seems be a good duo to help you deliver your solution. There is a Jekyll plugin: <a href="https://github.com/strapi/jekyll-strapi/">https://github.com/strapi/jekyll-strapi/</a> which allows to use Strapi as source for Jekyll’s <a href="https://jekyllrb.com/docs/collections/">Collections</a>. However, there are some little issues with it:</p><ul><li>It does not support authentication</li><li>It does not work well with media files</li><li>It does not work with the new Strapi version 4</li><li>It is not maintained anymore (there is a discussion in Strapi community about the future of this and another repos, however for today the topic is still not solved)</li></ul><p>During last few months there were few contributions of volunteers to make plugin compatible with Strapi version 4. Unfortunately, none of them have been merge — on one side there was not maintainer of the repo, on the second — pull requests seemed a bit incomplete for me.</p><p>This sounded for me like a good challenge, so I refreshed a bit of my knowledge of Ruby, and after around one week I had plugin not only working with Strapi 4, but also adding some missing features like authentication, unit tests and proxy filters.</p><p><a href="https://github.com/bluszcz/jekyll-strapi">GitHub - bluszcz/jekyll-strapi: Jekyll plugin to retrieve content from any Strapi v4 API.</a></p><h3>Simple portfolio website</h3><p>In this example, we are creating a very simple Photography portfolio page, where users can upload a photo with a title and a simple description.</p><h4>Strapi Configuration — CMS Setup</h4><p>Create a new Strapi project:</p><pre>npx create-strapi-app@latest my-project-photo --quickstart</pre><p>And then to start the project:</p><pre>cd my-project-photo<br>npm run develop</pre><p>Or if you are using yarn:</p><pre>yarn create-strapi-app@latest my-project-photo --quickstart<br>cd my-project-photo<br>yarn run develop</pre><p>Now you should have a reachable Strapi instance here: <a href="http://localhost:1337/">http://localhost:1337/</a>.</p><h4>Strapi Configuration — Collection setup</h4><p>Go to Content-Type Build in your admin instance <a href="http://localhost:1337/admin/plugins/content-type-builder/">http://localhost:1337/admin/plugins/content-type-builder/</a> and then create Collection as below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*yyKuqyq_to0WM5S-v_hr-g.jpeg" /></figure><p>To create the fields choose:</p><p><strong>Text field</strong> for the <em>Title</em>, type of <em>Short text:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q2-K5cjFgj8CL3Znxb4_Ag.jpeg" /></figure><p><strong>Media field</strong> with a name <em>Image</em>, type <em>Single media</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*09SljyT906OHtOCietsg3Q.jpeg" /></figure><p><strong>Text</strong> field with a name <em>Comment</em>, type <em>Long text</em>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*K-jkTv7dHHYepFXwvCvEYg.jpeg" /></figure><p>Finally, you should have something similar to:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v-OFV2fZtWRuvva2Y2Mdnw.jpeg" /></figure><p>Now go to Content Manager and add your first object to the database:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RWNhZjXHvK27sxtqYC3w0g.jpeg" /></figure><p>Auth token generation<br>Go to: <a href="http://localhost:1337/admin/settings/api-tokens/create">http://localhost:1337/admin/settings/api-tokens/create</a> and create a new token:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2gWzDEEnDPoKSLSdcmM4YA.jpeg" /></figure><p>After the creation — save the token aside — you will need it later. Some password manager is recommended.</p><h4>Plugin installation</h4><p>In your Jekyll project add to Gemfile:</p><pre>gem “jekyll-strapi-4”, “~&gt; 1.0.11”</pre><p>and install bundle:</p><pre>bundle install</pre><h4>Jekyll project configuration</h4><p>Add jekyll-strapi-4 to the plugins in _config.yml:</p><pre>plugins:<br>  - jekyll-feed<br>  - jekyll-strapi-4</pre><p>and following at the end of _config.yml:</p><pre>strapi:<br>    # Your API endpoint (optional, default to http://localhost:1337)<br>    endpoint: http://localhost:1337<br>    # Collections, key is used to access in the strapi.collections<br>    # template variable<br>    collections:<br>        # Example for a &quot;Photo&quot; collection<br>        photos:<br>            # Collection name (optional)<br>            # type: photos<br>            # Permalink used to generate the output files (eg. /articles/:id).<br>            permalink: /photos/:id/<br>            # Layout file for this collection<br>            layout: photo.html<br>            # Generate output files or not (default: false)<br>            output: true</pre><p>We install the plugin:</p><pre>gem install $MAIN_PATH/jekyll-strapi/jekyll-strapi-0.4.1.pre.dev.gem<br>rm Gemfile.lock<br>bundle install</pre><p><strong>Edited 2022–07–21</strong>: <em>I have created a GitHub packages </em><a href="https://github.com/bluszcz/jekyll-strapi/packages/1554094"><em>https://github.com/bluszcz/jekyll-strapi/packages/1554094</em></a><em> which can help you to install the necessary gem.</em></p><p>Then in _layouts directory create two files, home.html:</p><pre>---<br>layout: default<br>---<br><br>&lt;div class=&quot;home&quot;&gt;<br>  &lt;h1 class=&quot;page-heading&quot;&gt;Photos&lt;/h1&gt;<br>  {%- if strapi.collections.photos.size &gt; 0 -%}<br>  &lt;ul&gt;<br>    {%- for photo in strapi.collections.photos -%}<br>    &lt;li&gt;<br>      &lt;a href=&quot;{{ photo.url }}&quot;&gt;{{ photo.strapi_attributes.Titlle }}&lt;/a&gt;<br>    &lt;/li&gt;<br>    {%- endfor -%}<br>  &lt;/ul&gt;<br>  {%- endif -%}<br>&lt;/div&gt;</pre><p>and photo.html:</p><pre>---<br>layout: default<br>---<br><br>&lt;div class=&quot;home&quot;&gt;<br>  &lt;h1 class=&quot;page-heading&quot;&gt;{{ page.strapi_attributes.TestDescription }}&lt;/h1&gt;<br>  &lt;h2&gt;{{ page.document.strapi_attributes.Title }}&lt;/h2&gt;<br>  &lt;p&gt;{{ page.document.strapi_attributes.Comment }}&lt;/p&gt;<br>  &lt;img src=&quot;{{ page.document.strapi_attributes.Image.data.attributes.formats.thumbnail| asset_url }}&quot;/&gt;<br>&lt;/div&gt;</pre><p>Now you must set the environmental variable with auth token (you need to use the previously saved token here):</p><pre>export STRAPI_TOKEN=328438953489534...345423053895</pre><p>and now you can generate your page:</p><pre>bundle exec jekyll build --trace</pre><p>And after that you can check your website:</p><pre>cd _site<br>python3 -m http.server</pre><p>and opening <a href="http://localhost:8000/">http://localhost:8000</a> in your browser.</p><h3>Deployed example — demo</h3><p>Here you can see the page from the previous example deployed to GitHub pages: <a href="https://jekyll-strapi-v4-example.bluszcz.net/">https://jekyll-strapi-v4-example.bluszcz.net/</a></p><p>It is using the following GitHub repository: <a href="https://github.com/bluszcz/jekyll-strapi-v4-example.github.io/">https://github.com/bluszcz/jekyll-strapi-v4-example.github.io/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c5404cc9715" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Planning your next vegan trip with Nextcloud]]></title>
            <link>https://medium.com/@bluszcz/planning-your-next-vegan-trip-with-nextcloud-85c1c70f2ed3?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/85c1c70f2ed3</guid>
            <category><![CDATA[nextcloud]]></category>
            <category><![CDATA[vegan]]></category>
            <category><![CDATA[travel]]></category>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Sat, 16 Nov 2019 17:40:29 GMT</pubDate>
            <atom:updated>2019-11-16T18:31:20.544Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xwwgWjwK_CLWfNhNV5ZumA.png" /><figcaption>Carnet — web side with some todos before the trip</figcaption></figure><blockquote>So you saved some money and you plan to take some days off soon. Traveling seems to be a great opportunity to spend this time. However, time is precious, so it is better to prepare yourself before — you will enjoy more a well organized trip.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*3-Cj01SdWDGhnElU" /></figure><h3>What kind of challenges are in front of you?</h3><ol><li>Buying plane/transport tickets.</li><li>Preparing list of places to see/visit.</li><li>Organizing schedule when to go where.</li><li>Storing digital copy of your passport/id (can be useful if you lost your real documents).</li><li>Having all previously collected documents and data easily available during the whole journey, and during your trip your are going very like to have your smartphone as main digital device.</li><li>Storing photos taken during the trip.</li><li>Data privacy — you would like to avoid other companies, unwanted people and third parties knowing all your plans and following all your steps.</li><li>Sharing with friends and families your experiences (“look, such lovely deer”).</li><li>Sharing your vegan experiences with community.</li><li>Some place to keep new contacts — you may meet new friends during your trip and you would like to have their phone or email address stored.</li></ol><h3>What is the solution?</h3><p>It appears that self hosted instance of <a href="https://nextcloud.com/">Nextcloud</a> can address all the problems :) Let’s try to answer point-by-point:</p><ol><li>Try to buy all the tickets in advance — usually it brings some good deals and cheaper prices. Get all the boarding cards and other documents as pdf and save them in Nextcloud.</li><li>There is a great app <a href="https://apps.nextcloud.com/apps/carnet">Carnet</a> for Nextcloud, it comes as due of web and mobile app.</li><li>There is <a href="https://apps.nextcloud.com/apps/calendar">Calendar</a> app where you can make your schedule to the minute.</li><li>Nextcloud with <a href="https://nextcloud.com/blog/encryption-in-nextcloud/">encrypted storage</a> seems be perfect to store these documents. With mobile Nextcloud app you can access all the document any moment.</li><li>Check point 4 :).</li><li>Photos which you make during the trip you can upload almost instantly to your Nextcloud.</li><li>Since your Nextcloud is selfhosted —number of people access your data is minimized.</li><li>Nextcloud has great sharing options — you can share your photos in several ways, starting to regular share to other Nextcloud users in same instance, to share over HTTP with password, or to social share via <a href="https://apps.nextcloud.com/apps/social">federated networks</a>!</li><li>This will be an advertise of my open (Creative Commons licensed content) vegan platform <a href="https://veggiesailor.com/">Veggie Sailor</a> — please share your experience with community and allow others to reuse it :-)</li><li>Nextcloud allows to synchronize your smartphone contacts — the best app for it is <a href="https://www.davx5.com/">DavX5</a>.</li></ol><p>Enjoy your holidays!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85c1c70f2ed3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing Elasticsearch with MicroK8s]]></title>
            <link>https://medium.com/@bluszcz/installing-elasticsearch-with-microk8s-c02293f5c296?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/c02293f5c296</guid>
            <category><![CDATA[elasticsearch]]></category>
            <category><![CDATA[django]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[microk8s]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Sun, 07 Jul 2019 09:32:56 GMT</pubDate>
            <atom:updated>2019-07-07T09:32:56.095Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B-6LbJWdtesCodCepCco9w.jpeg" /><figcaption>Philipp Krenn @devopsbarcelona 2018</figcaption></figure><p>This weekend I was updating one of my legacy Django projects to the latest version of the framework. During the refactoring I found myself very quickly in a need to setup local instance of Elasticsearch. Recently I am getting most my personal work done on lovely Thinkpad T480, and as far I have already installed running MicroK8s setup — I wanted to utilize most out of it and avoid installing regular daemons/services on the laptop.</p><p>Elasticsearch guys provides installation manual for the docker: <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html">https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html</a> which is a basically one liner:</p><pre>docker run -p 9200:9200 -p 9300:9300 -e &quot;discovery.type=single-node&quot; docker.elastic.co/elasticsearch/elasticsearch:7.2.0</pre><p>I “adapted” it and created following <strong>elastic.yaml</strong> file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fd305e289c0bf7b0383385581d071343/href">https://medium.com/media/fd305e289c0bf7b0383385581d071343/href</a></iframe><p>and applied this configuration, following with an exposing of my freshly created deployment:</p><pre>$ kubectl apply -f elastic.yaml<br>$ kubectl expose deployment/elastic-deployment<br>$ kubectl describe svc elastic-deployment     <br>Name:              elastic-deployment<br>Namespace:         default<br>Labels:            app=elastic<br>Annotations:       &lt;none&gt;<br>Selector:          app=elastic<br>Type:              ClusterIP<br>IP:                10.152.183.229<br>Port:              port-1  9200/TCP<br>TargetPort:        9200/TCP<br>Endpoints:         10.1.1.61:9200<br>Port:              port-2  9300/TCP<br>TargetPort:        9300/TCP<br>Endpoints:         10.1.1.61:9300<br>Session Affinity:  None<br>Events:            &lt;none&gt;</pre><p>After that, I have adjusted my <a href="https://github.com/django-haystack/django-haystack">django-haystack</a> settings:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/73003742d67a4019fde2f641e84e20a1/href">https://medium.com/media/73003742d67a4019fde2f641e84e20a1/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c02293f5c296" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Last Week Summary — 2019–03–31]]></title>
            <link>https://medium.com/@bluszcz/last-week-summary-2019-03-31-4e8305928610?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e8305928610</guid>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Sun, 31 Mar 2019 20:41:23 GMT</pubDate>
            <atom:updated>2019-03-31T20:41:23.205Z</atom:updated>
            <content:encoded><![CDATA[<h3>Last Week Summary — 2019–03–31</h3><h3>DiRT 4 Released For Linux</h3><p>After Wikipedia, Dirt 4 is a rally-themed racing video game developed by Codemasters. It is the twelfth game in the Colin McRae Rally series and the sixth title to carry the Dirt name. And it was just released on Linux :-)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FGprbbXnOn_M%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DGprbbXnOn_M&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FGprbbXnOn_M%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9e3c11b806e1760b01f327c4544b1ef5/href">https://medium.com/media/9e3c11b806e1760b01f327c4544b1ef5/href</a></iframe><h3>Slovakia gets first female president</h3><p><a href="https://www.bbc.com/news/world-europe-47756368">Slovakia gets first female president</a></p><h3>Keith Flint Funeral</h3><p><a href="https://www.theguardian.com/music/2019/mar/29/prodigy-fans-from-around-world-gather-for-keith-flint-funeral">Prodigy fans from around world gather for Keith Flint&#39;s funeral</a></p><h3>Python 3.7.3 Reeleased</h3><p><a href="https://www.python.org/downloads/release/python-373/">Python Release Python 3.7.3</a></p><h3>Sailfish SDK 2.0 Released</h3><p>Since there is better availability of SailfishOS mobiles (several Sony Xperia models), new released of SailfishOS SDK is definitely worth to check.</p><p><a href="https://blog.jolla.com/sdk-2-0/">New enhanced Sailfish SDK is here | Jolla Blog</a></p><h3>Gitlab patch release</h3><p>Delivering fixes for several bugs and regression release.</p><p><a href="https://about.gitlab.com/2019/03/26/gitlab-11-9-1-released/">GitLab Patch Release: 11.9.1</a></p><h3>Commando VM — Windows based VM for Security Researches</h3><p>Perhaps not really first, but one of few Windows based Offensive Distribution.</p><p><a href="https://www.fireeye.com/blog/threat-research/2019/03/commando-vm-windows-offensive-distribution.html">Commando VM: The First of Its Kind Windows Offensive Distribution</a></p><h3>Wine 4.5 with Vulkan 1.1 available</h3><p><a href="https://www.winehq.org/announce/4.5">The Wine development release 4.5 is now available.</a></p><h3>Go 2018 Survey Results</h3><p>Results are very interesting around 70% surveyed used Go in both, at work and after work work scenarios. Also, every fith user of Go manage some tech teaem ;-)</p><p><a href="https://blog.golang.org/survey2018-results">The Go Blog</a></p><h3>Nintendo Switch Online free for Amazon Prime users</h3><p><a href="https://twitch.amazon.com/prime/loot/nintendo">Twitch Prime | Nintendo</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e8305928610" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Last Week Summary — 2019–03–24]]></title>
            <link>https://medium.com/@bluszcz/last-week-summary-2019-03-24-4bd2b719271a?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bd2b719271a</guid>
            <category><![CDATA[gitlab]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Sun, 24 Mar 2019 21:08:09 GMT</pubDate>
            <atom:updated>2019-03-24T22:53:49.019Z</atom:updated>
            <content:encoded><![CDATA[<h3>Last Week Summary — 2019–03–24</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eO_LQbf_BcpKPgoibnTfvw.jpeg" /><figcaption>Most important news which caught my attention.</figcaption></figure><h3>Cloud Native Conference in Warsaw</h3><p>Cloud Native Conference In Warsaw is an of event coders, developers, architects, and technical leaders, CIOs, CTOs, influencers, and enthusiasts to exchange knowledge and together shape the development of cloud native computing. And Call For Papers started!</p><p><a href="http://cloudnativewarsaw.com/">Cloud Native Warsaw Conference, September 9-10, 2019</a></p><p>There will be four separate tracks where you can submit proposal of your talk:</p><ul><li>Kubernetes</li><li>Cloud</li><li>Serverless</li><li>Cloud native</li></ul><h3>Charlotte de Witte played in Barcelona</h3><h3>Charlotte de Witte on Twitter</h3><p>📍Barcelona</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o85HmaU6Si3B5O2In_OQ9Q.jpeg" /><figcaption>Me with Charlotte down the stage</figcaption></figure><h3>Summary of the attacks origin</h3><p>I have started extracting data of attacks which had happened on our infrastructure last week. Peak of “activities” from China, Poland and US.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*_ETu25c1NPzNv4zWsY12pQ.png" /></figure><h3>AWS IoT Core port 443 support</h3><p>This is something what many customers with corporate strict firewall networking setup were awaiting:</p><p><a href="https://aws.amazon.com/about-aws/whats-new/2019/03/aws-iot-core-now-supports-http-rest-apis-with-x509-client-certificate-based-authentication-on-port-443/">AWS IoT Core Now Supports HTTP REST APIs with X.509 Client Certificate-Based Authentication On Port 443</a></p><h3>Battle For Wesnoth is being ported to Godot Engine</h3><p>Developers of the Open Source game Battle For Wesnoth tweeted recently information about porting the game from C++ to <a href="https://godotengine.org/">Godot Engine</a>.</p><h3>Battle for Wesnoth on Twitter</h3><p>Are we working on a thing? We might be working on a thing. #gamedev #GodotEngine</p><h3>Gitlab Upgrades</h3><p>There have been released two versions of Gitlab, one is full of new features and improvements:</p><p><a href="https://about.gitlab.com/2019/03/22/gitlab-11-9-released/">GitLab 11.9 released with secrets detection and multiple MR approval rules</a></p><ul><li>Gitlat chatops is open sourced now</li><li>secrets dections</li><li>more project templates</li><li>improvements in WebIDE</li></ul><p>and more.</p><p>Even if you are more conservative — you should definitely consider this critical update:</p><p><a href="https://about.gitlab.com/2019/03/20/critical-security-release-gitlab-11-dot-8-dot-3-released/">GitLab Critical Security Release: 11.8.3 and 11.7.7</a></p><h3>Facebook Open Sources ptr —multiple tests in paraller for Python</h3><p>Something definitely to look into if you want to speed up your tests, and if you want on big project with several commits and pushes per day — you want :-)</p><p><a href="https://code.fb.com/open-source/python-test-runner/">Python Test Runner: Open sourced for parallel tests - Facebook Code</a></p><h3>Google announces new gaming platform built on Linux — Stadia</h3><p>Streaming Games As a Service seems be a hot topic in 2019, and we have a strong player, Google.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAffodEEF4ho%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAffodEEF4ho&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FAffodEEF4ho%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c9ce927e6b39ff6e752a91f02fe15c4e/href">https://medium.com/media/c9ce927e6b39ff6e752a91f02fe15c4e/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bd2b719271a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MicroK8s and Fission]]></title>
            <link>https://medium.com/@bluszcz/microk8s-and-fission-407eadce8ab8?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/407eadce8ab8</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[fission]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[microk8s]]></category>
            <category><![CDATA[ubuntu]]></category>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Sun, 27 Jan 2019 17:54:12 GMT</pubDate>
            <atom:updated>2019-01-27T17:54:12.337Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*9Y4k7GXCusieEHuvIoGHpA.png" /><figcaption>An another Kubernetes tale from the Laptop world.</figcaption></figure><p>A few weeks ago I wrote a following article:</p><p><a href="https://medium.com/@bluszcz/serverless-microk8s-kubernetes-fcd6b875cd33">Serverless MicroK8s Kubernetes</a></p><p>where I described a process of an installation Kubeless and Fission on MicroK8s Kubernetes cluster. Unfortunately, Fission did not work as expect, but on the other side I really did enjoy Kubeless.</p><p>This week I was contacted by the developers team of Fission with the suggestion that I was not using a correct image and there is a <em>bugfix </em>for documentation to make the error message more readable:</p><p><a href="https://github.com/fission/fission/issues/952">Router should reply meaningful message back to CLI when encountering environment error · Issue #952 · fission/fission</a></p><p>With this new information I have decided to give an another shot and installed Fission latest 1.0-rc2 using helm:</p><pre>$ helm install --name fission --namespace fission <a href="https://github.com/fission/fission/releases/download/1.0-rc2/fission-core-1.0-rc2.tgz">https://github.com/fission/fission/releases/download/1.0-rc2/fission-core-1.0-rc2.tgz</a></pre><p>Next step was to install Fission command line interface:</p><pre>$ curl -Lo fission https://github.com/fission/fission/releases/download/1.0-rc2/fission-cli-linux <br>$ chmod +x fission <br>$ sudo mv fission /usr/local/bin/</pre><p>After verifying that Fission CLI works I have created an environment using correct image name:</p><pre>$ fission -v<br>client:<br>  fission/core:<br>    gitcommit: 12f6d91224c95e9e60da4adddd9922a273ace060<br>    builddate: 2019-01-14T17:02:51Z<br>    version: 1.0-rc2<br>server:<br>  fission/core:<br>    gitcommit: 12f6d91224c95e9e60da4adddd9922a273ace060<br>    builddate: 2019-01-14T17:02:51Z<br>    version: 1.0-rc2<br>$ fission env create --name python --image fission/python-env:1.0-rc2</pre><p>I have uploaded the example function:</p><pre>$ cat test2.py <br>def main():<br>    return &quot;Hello, world!\n&quot;</pre><pre>$ fission function create --name hello --env python --code test2.py</pre><p>And tested it:</p><pre>$ fission function test --name hello<br>Error calling function hello: 502 Fatal error: Error querying logs: Post <a href="http://127.0.0.1:35049/proxy/influxdb?db=fissionFunctionLog&amp;params=%7B%22funcuid%22%3A%2213aa96f1-21b1-11e9-8f43-8c1645bca5b9%22%2C%22time%22%3A0%7D&amp;q=select+%2A+from+%22log%22+where+%22funcuid%22+%3D+%24funcuid+AND+%22time%22+%3E+%24time+LIMIT+1000">http://127.0.0.1:35049/proxy/influxdb?db=fissionFunctionLog&amp;params=%7B%22funcuid%22%3A%2213aa96f1-21b1-11e9-8f43-8c1645bca5b9%22%2C%22time%22%3A0%7D&amp;q=select+%2A+from+%22log%22+where+%22funcuid%22+%3D+%24funcuid+AND+%22time%22+%3E+%24time+LIMIT+1000</a>: net/http: request canceled (Client.Timeout exceeded while awaiting headers)</pre><p>Timeout nature of the error pointed me to investigate my iptables rules and it appeared that I was rejecting forwarded packets. I have adjusted a firewall rule:</p><pre>$ sudo iptables -P FORWARD ACCEPT</pre><p>And tried again:</p><pre>$  fission function test --name hello<br>Hello, world!</pre><p>Ok, it works! Thank you very much guys for contacting me and helping me to make it work.</p><p>What is a next step? My favorite feature of Fission is <a href="https://docs.fission.io/workflows/">Workflows,</a> framework to orchestrate set of functions, a very powerful concept which I am going to test soon and write more about it. Cheers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=407eadce8ab8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Files upload from Kubeless on MicroK8s to Minio]]></title>
            <link>https://itnext.io/files-upload-from-kubeless-on-microk8s-to-minio-607e06598a4b?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/607e06598a4b</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[kubeless]]></category>
            <category><![CDATA[microk8s]]></category>
            <category><![CDATA[serverless]]></category>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 21:48:22 GMT</pubDate>
            <atom:updated>2019-01-08T19:51:35.229Z</atom:updated>
            <content:encoded><![CDATA[<p>Serverless upload to the object storage</p><p>In this article I will demonstrate how to write a simple python function which will download an image from <a href="https://unsplash.com/"><strong>Unsplash</strong></a> and upload to <a href="https://github.com/minio/minio"><strong>Minio</strong>,</a> S3 compatible object storage.</p><p>To follow and execute code in this article you will need MicroK8s, Kubeless and Python3. You can read introduction to serverless on MicroK8s in my article here:</p><p><a href="https://medium.com/@bluszcz/serverless-microk8s-kubernetes-fcd6b875cd33">Serverless MicroK8s Kubernetes</a></p><h3>Unsplash</h3><p>Unsplash is a very popular marketing service ;-) — providing thousands of royalty free photos for free.</p><p>If you do not have Unsplash account, please <a href="https://unsplash.com/join">create one</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Ukb3eWBZMf9Bd3Ss-s25A.png" /></figure><p>Next, register a new application: <a href="https://unsplash.com/oauth/applications/new.">https://unsplash.com/oauth/applications/new.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/773/1*wnnkdNb1xEfJy_f2Q9uCJw.png" /><figcaption>Register new app in Unsplash</figcaption></figure><p>After this you will receive your access key (which we will use later):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*aGHD7HAZP_JZpUIq5pkh5g.png" /><figcaption>API Credentials.</figcaption></figure><p>We can verify is the key if working by executing <strong><em>curl</em></strong> command followed by <strong><em>jq</em></strong>:</p><pre>$ export UNSPLASH_ACCESS_KEY=&quot;...&quot;<br>$ curl -s <a href="https://api.unsplash.com/photos//?client_id\=$UNSPLASH_ACCESS_KEY">https://api.unsplash.com/photos/\?client_id\=$UNSPLASH_ACCESS_KEY</a> |jq &#39;.[0] |{desc: .description}&#39;<br>{<br>  &quot;desc&quot;: &quot;5 bottles of DOSE Juice on a shelf&quot;<br>}</pre><h3>Minio</h3><p>Minio is an open source object storage server, compatible with S3. An interesting feature is that it can also act as a gateway between other objects storage systems.</p><p>We can install Minio using Kubernetes, but before we need to prepare a Persistent Volume:</p><pre>$ cat pv.yaml <br>kind: PersistentVolume<br>apiVersion: v1<br>metadata:<br>  name: task-pv-volume<br>  labels:<br>    type: local<br>spec:<br>  storageClassName: standard<br>  capacity:<br>    storage: 10Gi<br>  accessModes:<br>    - ReadWriteOnce<br>  hostPath:<br>    path: &quot;/tmp/data&quot;</pre><p>Next, I generated yaml file for here: Minio <a href="https://www.minio.io/kubernetes.html">https://www.minio.io/kubernetes.html</a>. What you need to do is to uncomment storageClassName and fill it with correct value, in my case it was standard (same as in above <em>pv.yaml</em> file):</p><pre>storageClassName: standard</pre><p>and enter values into the Minio<em> </em><strong><em>access key</em></strong><em> </em>and<em> </em><strong><em>secret key</em></strong>.</p><pre>$ kubectl create -f minio-deployment.yaml</pre><p>To verify:</p><pre>$ kubectl get services                                                                                                               <br>NAME            TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE<br>kubernetes      ClusterIP      10.152.183.1     &lt;none&gt;        443/TCP          4d<br>minio-service   LoadBalancer   10.152.183.228   &lt;pending&gt;     9000:32302/TCP   72m</pre><h3>Python function for Kubeless</h3><p>Now, most interesting part is coming — we are going to write some code :) To do it there are two helpful apis:</p><ul><li><a href="https://unsplash.com/developers">https://unsplash.com/developers</a></li><li><a href="https://docs.minio.io/docs/python-client-quickstart-guide">https://docs.minio.io/docs/python-client-quickstart-guide</a></li></ul><p>As we can see in Minio docs, it is using special python package. Let’s see if this package is available in Kubeless by trying to execute a function with simply importing minio:</p><pre>$ cat /tmp/up.py             <br>import minio</pre><pre>def hello(event, context):<br>    print (event)<br>    return event[&#39;data&#39;]</pre><pre>$ kubeless function deploy up --runtime python3.6 --from-file up.py --handler up.hello</pre><pre>INFO[0000] Deploying function...                        <br>INFO[0000] Function up submitted for deployment         <br>INFO[0000] Check the deployment status executing &#39;kubeless function ls up&#39; <br>$ kubeless function  ls                                                               <br>NAME  NAMESPACE HANDLER    RUNTIME   DEPENDENCIES STATUS       <br>hello default   test.hello python3.6              1/1 READY    <br>up    default   up.hello   python3.6              0/1 NOT READY<br>$ kubeless function  ls<br>NAME  NAMESPACE HANDLER    RUNTIME   DEPENDENCIES STATUS   <br>hello default   test.hello python3.6              1/1 READY<br>up    default   up.hello   python3.6              1/1 READY<br>$ kubeless function call up --data &quot;Let&#39;s pray...&quot;<br>ERRO[0000] {&quot;kind&quot;:&quot;Status&quot;,&quot;apiVersion&quot;:&quot;v1&quot;,&quot;metadata&quot;:{},&quot;status&quot;:&quot;Failure&quot;,&quot;message&quot;:&quot;no endpoints available for service \&quot;up:http-function-port\&quot;&quot;,&quot;reason&quot;:&quot;ServiceUnavailable&quot;,&quot;code&quot;:503}<br> <br>FATA[0000] the server is currently unable to handle the request</pre><p>It does not have, which was expected :) Everyone who used to work with AWS Lambda for sure does remember building python packages, fitting them into specific size and uploading along with Lambda. Here, we can skip it and provide the dependencies as extra parameter:</p><pre>$ cat requirements.txt <br>minio<br>requests<br>$ kubeless function  deploy up --runtime python3.6 --from-file /tmp/up.py --dependencies requirements.txt --handler up.hello</pre><p>Now, when we list our function we will see our packages on the list of the dependencies:</p><pre>$ kubeless function ls up      <br>NAME NAMESPACE HANDLER  RUNTIME   DEPENDENCIES STATUS       <br>up   default   up.hello python3.6 minio        0/1 NOT READY<br>                                  requests<br>$ kubectl get pods<br>NAME                  READY   STATUS             RESTARTS   AGE<br><br>up-5f6cbd8bb7-957ls   0/1     Init:1/2           0          2m5s</pre><p>Describe the pod to see that it is building new docker image:</p><pre>$ kubectl describe pod up-5f6cbd8bb7-957ls</pre><pre>...Events:<br>  Type    Reason     Age                   From               Message<br>  ----    ------     ----                  ----               -------<br>  Normal  Scheduled  6m26s                 default-scheduler  Successfully assigned default/up-5f6cbd8bb7-957ls to t480<br>  Normal  Pulled     6m25s                 kubelet, t480      Container image &quot;kubeless/unzip@sha256:f162c062973cca05459834de6ed14c039d45df8cdb76097f50b028a1621b3697&quot; already present on machine<br>  Normal  Created    6m25s                 kubelet, t480      Created container<br>  Normal  Started    6m25s                 kubelet, t480      Started container<br>  Normal  Pulling    6m24s                 kubelet, t480      pulling image &quot;python:3.6&quot;<br>  Normal  Pulled     4m36s                 kubelet, t480      Successfully pulled image &quot;python:3.6&quot;<br>  Normal  Created    2m3s (x2 over 4m34s)  kubelet, t480      Created container<br>  Normal  Started    2m3s (x2 over 4m33s)  kubelet, t480      Started container<br>  Normal  Pulled     2m3s                  kubelet, t480      Container image &quot;python:3.6&quot; already present on machine</pre><p>Quick check if the dependencies are working (in the code we are importing <strong>minio</strong> module):</p><pre>$ kubeless function call up --data &quot;Let&#39;s pray...&quot;<br>Let&#39;s pray...</pre><p>Since dependencies are working, I prepared simple python script to get an image from Unsplash — which I uploaded <a href="https://github.com/Devcarpet/microk8s-kubeless-minio/blob/master/up.py">here</a>, I do not copy paste it here due to the a poor monospace font support in Medium — where the most important parts namely are, downloading the image:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/443/1*NhBO7NX_jGvAoEowhtkfQw.png" /></figure><p>and uploading it to deployed in Kubernetes Minio:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*P_fNFNTjkURniOa7v9mnjA.png" /></figure><p>This code I deployed as a function:</p><pre>$ kubeless function delete up<br>$ kubeless function  deploy up \ <br> --runtime python3.6 --from-file up.py \ <br> --dependencies requirements.txt --handler up.hello \ <br> --env MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY \ <br> --env MINIO_SECRET_KEY=$MINIO_SECRET_KEY \ <br> --env MINIO_API_URL=$MINIO_API_URL \  <br> --env UNSPLASH_ACCESS_KEY=$UNSPLASH_ACCESS_KEY</pre><p>Final call of the function (which will output name of the file after successful upload):</p><pre>$ kubeless function call up                                                                                                           Deer_1546895482.jpg</pre><p>And check in the <a href="http://localhost:9000/">Minio web panel</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/680/1*hlEG8WIYD0cd7M9cT2MI8A.png" /></figure><p>Everything works :) I hope you enjoyed reading this.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=607e06598a4b" width="1" height="1" alt=""><hr><p><a href="https://itnext.io/files-upload-from-kubeless-on-microk8s-to-minio-607e06598a4b">Files upload from Kubeless on MicroK8s to Minio</a> was originally published in <a href="https://itnext.io/">ITNEXT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Serverless MicroK8s Kubernetes]]></title>
            <link>https://medium.com/@bluszcz/serverless-microk8s-kubernetes-fcd6b875cd33?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/fcd6b875cd33</guid>
            <category><![CDATA[fission]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[kubeless]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[microk8s]]></category>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Sun, 06 Jan 2019 10:14:50 GMT</pubDate>
            <atom:updated>2019-01-07T22:04:35.231Z</atom:updated>
            <content:encoded><![CDATA[<h3>Happy New Year!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aWSdMCIh6uFTaaf3TD0Z_g.jpeg" /><figcaption>Thinkpad, Code Keyboard and Novation Launchpap — my Christmas Setup 2015</figcaption></figure><p>At the end of the year 2018 I have discovered something what had blew my mind. Let’s see what is this.</p><p><strong>MicroK8s from Ubuntu</strong></p><p>What is this? Webpage says “<em>Kubernetes in a </em><a href="https://snapcraft.io/"><em>snap</em></a><em> that you can run locally</em>”. This short description definitely sparked my attention, so I started to read more and following features attracted me even more:</p><ul><li><a href="https://github.com/cncf/k8s-conformance/tree/master/v1.12/microk8s">Compliant</a> (certified) with Kubernetes</li><li>Can be used in VM for CI/CD to tests Kubernetes</li><li>Allows to quick (below minute) setup on your workstation or laptop</li><li>You can launch <a href="https://www.kubeflow.org/docs/started/getting-started-multipass/">Kubeflow on it</a></li></ul><p>As a follow up of the last point, assuming that you have snap installed (which is a case by default in Ubuntu 18.04) you can install MicroK8s in a following way:</p><pre>$ sudo snap install microk8s --classic`</pre><p>which gives you access to the command kubectl with prefix microk8s (this is in purpose to avoid conflict:</p><pre>$ microk8s.kubectl</pre><p>If you do not have installed kubectl yet, you may simplify your life by making alias to kubectl command:</p><pre>$ sudo snap alias microk8s.kubectl kubectl<br>$ kubectl auth can-i create pods <br>yes</pre><p>Let’s test some available serverless solutions based on Kubernetes. Two most popular are Kubeless and Fission.</p><h3><strong>Kubeless</strong></h3><p>Kubeless, developed by Bitnami looks like a very robust solution with several very convincing features:</p><ul><li>CLI compatible with AWS Lambda</li><li>Support for Python, Node.js, Ruby, PHP, Golang, .NET, Ballerina and custom routines</li><li>Plugin for Serverless framework</li></ul><p>Installation process is described here: <a href="https://kubeless.io/docs/quick-start/#installation">https://kubeless.io/docs/quick-start/#installation,</a> and since MicroK8s by definition does not come with RBAC support, I picked non-RBAC Kubernetes cluster one.</p><p>Installation starts with creating namespace for kubeless:</p><pre>$ kubectl create ns kubeless<br>namespace/kubeless created</pre><p>For now everything is good :)</p><pre>$ export RELEASE=$(curl -s <a href="https://api.github.com/repos/kubeless/kubeless/releases/latest">https://api.github.com/repos/kubeless/kubeless/releases/latest</a> | grep tag_name | cut -d &#39;&quot;&#39; -f 4) <br>$ kubectl create -f <a href="https://github.com/kubeless/kubeless/releases/download/$RELEASE/kubeless-non-rbac-$RELEASE.yaml">https://github.com/kubeless/kubeless/releases/download/$RELEASE/kubeless-non-rbac-$RELEASE.yaml</a><br>configmap/kubeless-config created<br>deployment.apps/kubeless-controller-manager created<br>serviceaccount/controller-acct created<br>customresourcedefinition.apiextensions.k8s.io/functions.kubeless.io created<br>customresourcedefinition.apiextensions.k8s.io/httptriggers.kubeless.io created<br>customresourcedefinition.apiextensions.k8s.io/cronjobtriggers.kubeless.io created</pre><p>Good so far.</p><pre>$ kubectl get pods -n kubeless<br>NAME                                           READY   STATUS    RESTARTS   AGE<br>kubeless-controller-manager-7c7bcb8db4-blww9   3/3     Running   0          50s<br>$ kubectl get deployment -n kubeless<br>NAME                          READY   UP-TO-DATE   AVAILABLE   AGE<br>kubeless-controller-manager   1/1     1            1           6m15s<br>$ kubectl get customresourcedefinition<br>NAME                          CREATED AT<br>cronjobtriggers.kubeless.io   2019-01-04T21:35:37Z<br>functions.kubeless.io         2019-01-04T21:35:37Z<br>httptriggers.kubeless.io      2019-01-04T21:35:37Z</pre><p>Still good. Time to install kubeless CLI:</p><pre>$ curl -OL <a href="https://github.com/kubeless/kubeless/releases/download/$RELEASE/kubeless_$OS-amd64.zip">https://github.com/kubeless/kubeless/releases/download/$RELEASE/kubeless_$OS-amd64.zip</a> &amp;&amp; \<br>  unzip kubeless_$OS-amd64.zip &amp;&amp; \<br>  sudo mv bundles/kubeless_$OS-amd64/kubeless /usr/local/bin/<br>  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current<br>                                 Dload  Upload   Total   Spent    Left  Speed<br>100   614    0   614    0     0    951      0 --:--:-- --:--:-- --:--:--   951<br>100 7559k  100 7559k    0     0  3311k      0  0:00:02  0:00:02 --:--:-- 12.0M<br>Archive:  kubeless_linux-amd64.zip<br>   creating: bundles/kubeless_linux-amd64/<br>  inflating: bundles/kubeless_linux-amd64/kubeless  <br>[sudo] password for bluszcz: </pre><p>And then installing first function (I am using python3.6):</p><pre>$ cat test.py <br>def hello(event, context):<br>    print (event)<br>    return event[&#39;data&#39;]<br>$ kubeless function deploy hello --runtime python3.6 --from-file test.py --handler test.hello</pre><pre>FATA[0000] Can not get kubernetes config: stat /home/bluszcz/.kube/config: no such file or directory </pre><p>Right… Let’s try to generate config:</p><pre>$ microk8s.kubectl config view &gt; $HOME/.kube/config$                                                                                </pre><p>and rerun:</p><pre>$ kubeless function deploy hello --runtime python3.6 --from-file test.py --handler test.hello<br>INFO[0000] Deploying function...                        <br>INFO[0000] Function hello submitted for deployment      <br>INFO[0000] Check the deployment status executing &#39;kubeless function ls hello&#39; </pre><p>Voilà! Check if my function is available:</p><pre>$ kubectl get functions<br>NAME    AGE<br>hello   6m</pre><p>So, let’s test if it works:</p><pre>$ kubeless function call hello --data &quot;Let&#39;s pray...&quot;                                                                                 <br>Let&#39;s pray...</pre><p>Yes, It works!. Any thought? In 5 minutes we have on our laptop running (based on Kubernetes) serverless platform! <strong>Fracking amazing</strong>. Simplicity and compatibility with AWS Lambda and Serverless framework will definitely make me spending more time with Kubeless.</p><p>Time to test the another solution.</p><h3>Fission</h3><p>Fission, competitive (provided by <a href="https://platform9.com/">Platform8</a>) solution has following features:</p><ul><li>Supports for Python, NodeJS, Go, C#, PHP</li><li>Support Workflows is an open source framework that allows you to orchestrate a set of serverless functions without directly dealing with networking, message queues, (feature is still missing in <a href="https://github.com/kubeless/kubeless/issues/342"><strong>Kubeless</strong></a>).</li><li>At the time writing of the article (first week of 2019) it does need RBAC installed, <a href="https://github.com/fission/fission/issues/993">link to Githu</a>b issue</li></ul><p>Following a hint from the <a href="https://github.com/ubuntu/microk8s/issues/84#issuecomment-423134519">opened issue for the MicroK8s,</a> I have “simulated” RBAC in my MicroK8s and started installation with helm:</p><pre>$ helm install --name fission --namespace fission --set serviceType=NodePort,routerServiceType=NodePort <a href="https://github.com/fission/fission/releases/download/1.0-rc1/fission-all-1.0-rc1.tgz">https://github.com/fission/fission/releases/download/1.0-rc1/fission-all-1.0-rc1.tgz</a></pre><pre>NAME:   fission<br>LAST DEPLOYED: Sat Jan  5 00:44:31 2019<br>NAMESPACE: fission<br>STATUS: DEPLOYED</pre><pre>RESOURCES:<br>==&gt; v1beta2/StatefulSet<br>NAME   DESIRED  CURRENT  AGE<br>redis  1        1        54s</pre><pre>==&gt; v1beta1/ClusterRole<br>NAME                                   AGE<br>fission-prometheus-kube-state-metrics  54s<br>fission-prometheus-server              54s</pre><pre>==&gt; v1/ClusterRole<br>NAME                     AGE<br>secret-configmap-getter  54s<br>package-getter           54s</pre><pre>==&gt; v1beta1/RoleBinding<br>NAME           AGE<br>fission-admin  54s</pre><pre>==&gt; v1beta1/DaemonSet<br>NAME                              DESIRED  CURRENT  READY  UP-TO-DATE  AVAILABLE  NODE SELECTOR  AGE<br>fission-prometheus-node-exporter  1        1        1      1           1          &lt;none&gt;         54s<br>logger                            1        1        1      1           1          &lt;none&gt;         54s</pre><pre>==&gt; v1/Pod(related)<br>NAME                                                  READY  STATUS             RESTARTS  AGE<br>fission-prometheus-node-exporter-dg6dk                1/1    Running            0         54s<br>logger-rv485                                          1/1    Running            0         54s<br>fission-prometheus-alertmanager-7dd8795d65-f6897      0/2    Pending            0         54s<br>fission-prometheus-kube-state-metrics-6748f7d8-2nh26  1/1    Running            0         54s<br>fission-prometheus-pushgateway-66db5b98c9-wnfbl       1/1    Running            0         54s<br>fission-prometheus-server-7d85cf4fcb-pqgbh            0/2    Pending            0         54s<br>executor-759785c444-kmzzv                             1/1    Running            0         54s<br>mqtrigger-nats-streaming-7f55678558-t292l             1/1    Running            0         54s<br>storagesvc-7d94dbbc8b-zq24k                           0/1    Pending            0         54s<br>buildermgr-7857f48f78-8bc79                           1/1    Running            0         53s<br>router-6564f6b95-xprg7                                1/1    Running            0         53s<br>influxdb-868d78d79-bqxsp                              0/1    ContainerCreating  0         53s<br>controller-66b9559c8f-4xcdz                           1/1    Running            0         53s<br>timer-5cd5886755-kll2k                                0/1    ContainerCreating  0         53s<br>kubewatcher-5584b7bd77-qggz2                          0/1    ContainerCreating  0         53s<br>nats-streaming-576964bb64-k2nww                       0/1    ContainerCreating  0         52s<br>redis-0                                               1/1    Running            0         54s</pre><pre>==&gt; v1/Namespace<br>NAME              STATUS  AGE<br>fission-builder   Active  54s<br>fission-function  Active  54s</pre><pre>==&gt; v1/PersistentVolumeClaim<br>NAME                             STATUS   VOLUME  CAPACITY  ACCESS MODES  STORAGECLASS  AGE<br>fission-prometheus-alertmanager  Pending  54s<br>fission-prometheus-server        Pending  54s<br>fission-storage-pvc              Pending  54s</pre><pre>==&gt; v1/ServiceAccount<br>NAME                                   SECRETS  AGE<br>fission-prometheus-alertmanager        1        54s<br>fission-prometheus-kube-state-metrics  1        54s<br>fission-prometheus-node-exporter       1        54s<br>fission-prometheus-pushgateway         1        54s<br>fission-prometheus-server              1        54s<br>fission-svc                            1        54s<br>fission-fetcher                        1        54s<br>fission-builder                        1        54s</pre><pre>==&gt; v1beta1/ClusterRoleBinding<br>NAME                                   AGE<br>fission-prometheus-kube-state-metrics  54s<br>fission-prometheus-server              54s<br>fission-crd                            54s</pre><pre>==&gt; v1beta1/Deployment<br>NAME                                   DESIRED  CURRENT  UP-TO-DATE  AVAILABLE  AGE<br>fission-prometheus-alertmanager        1        1        1           0          54s<br>fission-prometheus-kube-state-metrics  1        1        1           1          54s<br>fission-prometheus-pushgateway         1        1        1           1          54s<br>fission-prometheus-server              1        1        1           0          54s<br>executor                               1        1        1           1          54s<br>mqtrigger-nats-streaming               1        1        1           1          54s<br>storagesvc                             1        1        1           0          54s<br>buildermgr                             1        1        1           1          54s<br>router                                 1        1        1           1          54s<br>influxdb                               1        1        1           0          54s<br>controller                             1        1        1           1          54s<br>timer                                  1        1        1           0          54s<br>kubewatcher                            1        1        1           0          54s<br>nats-streaming                         1        1        1           0          54s</pre><pre>==&gt; v1/Secret<br>NAME      TYPE    DATA  AGE<br>influxdb  Opaque  2     54s</pre><pre>==&gt; v1/ConfigMap<br>NAME                             DATA  AGE<br>fission-prometheus-alertmanager  1     54s<br>fission-prometheus-server        3     54s<br>feature-config                   1     54s</pre><pre>==&gt; v1/Service<br>NAME                                   TYPE       CLUSTER-IP      EXTERNAL-IP  PORT(S)         AGE<br>fission-prometheus-alertmanager        ClusterIP  10.152.183.168  &lt;none&gt;       80/TCP          54s<br>fission-prometheus-kube-state-metrics  ClusterIP  None            &lt;none&gt;       80/TCP          54s<br>fission-prometheus-node-exporter       ClusterIP  None            &lt;none&gt;       9100/TCP        54s<br>fission-prometheus-pushgateway         ClusterIP  10.152.183.149  &lt;none&gt;       9091/TCP        54s<br>fission-prometheus-server              ClusterIP  10.152.183.128  &lt;none&gt;       80/TCP          54s<br>influxdb                               ClusterIP  10.152.183.87   &lt;none&gt;       8086/TCP        54s<br>executor                               ClusterIP  10.152.183.57   &lt;none&gt;       80/TCP          54s<br>redis                                  ClusterIP  10.152.183.195  &lt;none&gt;       6379/TCP        54s<br>nats-streaming                         NodePort   10.152.183.98   &lt;none&gt;       4222:31316/TCP  54s<br>router                                 NodePort   10.152.183.30   &lt;none&gt;       80:31314/TCP    54s<br>controller                             NodePort   10.152.183.93   &lt;none&gt;       80:31313/TCP    54s<br>storagesvc                             ClusterIP  10.152.183.104  &lt;none&gt;       80/TCP          54s</pre><pre>NOTES:<br>1. Install the client CLI.</pre><pre>[...]</pre><pre>Linux:<br>  $ curl -Lo fission <a href="https://github.com/fission/fission/releases/download/1.0-rc1/fission-cli-linux">https://github.com/fission/fission/releases/download/1.0-rc1/fission-cli-linux</a> &amp;&amp; chmod +x fission &amp;&amp; sudo mv fission /usr/local/bin/</pre><pre>2. You&#39;re ready to use Fission!</pre><pre>[...]</pre><pre># Run this function<br>  $ fission function test --name hello<br>  Hello, world!</pre><p>Looks promising for now. Next step, create an environment and create python function inside this environment:</p><pre>$ fission env create --name python --image fission/python                                                                           environment &#39;python&#39; created<br>$ vim test2.py                                                                                                                      $ cat test2.py <br>def main():<br>    return &quot;Hello, world!\n&quot;<br>$ fission function create --name hello --env python --code test2.py                                                                 <br>Package &#39;test2-py-29ep&#39; created<br>package &#39;test2-py-29ep&#39; created<br>function &#39;hello&#39; created</pre><p>Function created. Let’s test it.</p><pre>$ fission function test --name hello                                                                                                  </pre><pre>Error calling function hello: 500 Post <a href="http://executor.fission/v2/getServiceForFunction">http://executor.fission/v2/getServiceForFunction</a>: dial tcp: i/o timeoutFatal error: Error querying logs: Post <a href="http://127.0.0.1:42057/proxy/influxdb?db=fissionFunctionLog&amp;params=%7B%22funcuid%22%3A%22137c1481-107d-11e9-b057-8c1645bca5b9%22%2C%22time%22%3A0%7D&amp;q=select+%2A+from+%22log%22+where+%22funcuid%22+%3D+%24funcuid+AND+%22time%22+%3E+%24time+LIMIT+1000">http://127.0.0.1:42057/proxy/influxdb?db=fissionFunctionLog&amp;params=%7B%22funcuid%22%3A%22137c1481-107d-11e9-b057-8c1645bca5b9%22%2C%22time%22%3A0%7D&amp;q=select+%2A+from+%22log%22+where+%22funcuid%22+%3D+%24funcuid+AND+%22time%22+%3E+%24time+LIMIT+1000</a>: net/http: request canceled (Client.Timeout exceeded while awaiting headers)</pre><p>So, it does not work, unfortunately. I could try to investigate error more, but at this moment I have decided to give up and make another approach to MicroK82+Fission in some time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fcd6b875cd33" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PySide2, Tray Icon and PyInstaller]]></title>
            <link>https://medium.com/@bluszcz/pyside2-tray-icon-and-pyinstaller-9a0abf046b4f?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a0abf046b4f</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[installation]]></category>
            <category><![CDATA[pyinstaller]]></category>
            <category><![CDATA[qt]]></category>
            <category><![CDATA[pyside2]]></category>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Thu, 13 Sep 2018 22:20:52 GMT</pubDate>
            <atom:updated>2018-09-13T22:20:52.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*KKiicjQjOQwg2GCpyGVDdg.png" /></figure><p>I love to code in Python, and I really like Qt library. Since I have discovered that <a href="http://wiki.qt.io/Qt_for_Python">Pyside2</a> <a href="https://groups.google.com/forum/#!topic/pyside-dev/pqwzngAGLWE">became part</a> of the Qt family I have decided to choose Pyside2 as my main GUI tool.</p><p>To facilitate a distribution of Python application (create one binary package) there are several helpful utilities, and I <a href="https://www.pyinstaller.org/">PyInstaller</a> seems be the most popular.</p><p>For Today, PyInstaller contains a bug <a href="https://github.com/pyinstaller/pyinstaller/issues/3327">https://github.com/pyinstaller/pyinstaller/issues/3327</a> which introduces some problems during onefile mode when distributing binary files along with PySide2 projects. It seems ignoring a rcc files — not including them in the package. However, before bug will be fixed there is quick workaround. There is a <strong>pyrcc5</strong> command, which is being distributed together with PyQT. You should install it (easy with Ubuntu):</p><pre># apt install pyqt5-dev-tools</pre><p>And you are ready to create Python resource file:</p><pre>$ pyrcc5 resources.qrc -o resources_rc.py</pre><p>However, file contains an import referring to PyQT, not PySide2:</p><pre>from PyQt5 import QtCore</pre><p>you should change it to:</p><pre>from PySide2 import QtCore</pre><p>and now you can import new created file in your python application:</p><pre>import resources_rc</pre><p>and we are ready to package:</p><pre>pyinstaller --onefile desktop.py</pre><p>and to test:</p><pre>cd dist<br>./desktop</pre><p>Enjoy :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a0abf046b4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vegan hacker #2 casserole.v01 Tortilla]]></title>
            <link>https://medium.com/@bluszcz/vegan-hacker-2-casserole-v01-tortilla-80e8b983ed83?source=rss-1f9a4530caf------2</link>
            <guid isPermaLink="false">https://medium.com/p/80e8b983ed83</guid>
            <category><![CDATA[vegan]]></category>
            <category><![CDATA[recipe]]></category>
            <category><![CDATA[tortillas]]></category>
            <category><![CDATA[potato]]></category>
            <category><![CDATA[casseroles]]></category>
            <dc:creator><![CDATA[Rafał bluszcz Zawadzki]]></dc:creator>
            <pubDate>Sat, 14 Apr 2018 19:10:31 GMT</pubDate>
            <atom:updated>2018-04-14T19:10:31.204Z</atom:updated>
            <content:encoded><![CDATA[<p>So I made another casserole, this time Spanish Omelette a.k.a <em>Tortilla</em>.</p><p><em>Time spending on preparing: 25m, time awaiting for baking: 60m</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E2LaUNm3b_2g3YMh_0wbkA.jpeg" /><figcaption>Tortilla just after cooling down</figcaption></figure><p>Another recipe, another casserole. And actually another one is in the oven. Let’s assume that I am a casserole geek :)</p><h3>Ingredients</h3><ul><li>1.5g potato</li><li>200g mushrooms</li><li>1 onion</li><li>carrot</li><li>red pepper spice</li><li>salt</li><li>1 cube of mushroom brooth</li></ul><h3>Recipe</h3><p>Chop potato into the medium cubes. Cook them till they will be very soft (puree style) in water with salt. While cooking potato — chop mushrooms and onion and fry together adding salt and red pepper. At the end of frying add 1L of water to pan and cube of broth. Boil it and cook next 10 minutes which will leave you with aromatic gulash on the frying pan.</p><p>Soak cooked potato, smash them into pure style and then add to gulsh.</p><p>Mix together everything, put into oven and bake for 60 minutes in 200 degree. <strong>Enjoy!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80e8b983ed83" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>