<?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 Dominik Bittl on Medium]]></title>
        <description><![CDATA[Stories by Dominik Bittl on Medium]]></description>
        <link>https://medium.com/@dominik.bittl?source=rss-3050bc313338------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*GmvxqabkfEgtEGOfUphYmg.jpeg</url>
            <title>Stories by Dominik Bittl on Medium</title>
            <link>https://medium.com/@dominik.bittl?source=rss-3050bc313338------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:18:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dominik.bittl/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[Dear Sysadmin, time is over. Learn coding. Fast!]]></title>
            <link>https://medium.com/@dominik.bittl/dear-sysadmin-time-is-over-learn-coding-fast-335a920dfb71?source=rss-3050bc313338------2</link>
            <guid isPermaLink="false">https://medium.com/p/335a920dfb71</guid>
            <category><![CDATA[change]]></category>
            <category><![CDATA[sysadmin]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Dominik Bittl]]></dc:creator>
            <pubDate>Mon, 23 Oct 2017 17:48:20 GMT</pubDate>
            <atom:updated>2017-10-23T17:48:20.879Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j4oOOKFcBCmSOfVlAx5UTA.jpeg" /></figure><p>In my early Linux days over 20 years ago, all you had to do was setting up things in config files. And it worked all fine for me.</p><p>On some day there came something up called “virtualisation”. After that more and more systems were installed in less and even lesser time. The problem was to keep up all configs in sync, time was always to less and as always the team was understaffed. Sure you could copy configs or share them on the one or other way but it was not really satisfying to me. So I started to think about to code some solution for that but fast I gave it up. The barrier just seemed to high for me at that point. And overall I am a Sysadmin and no Software Developer if I had wanted to be a developer I had become one. ;-)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SAc84eMPcyrloVTsf-fEzA.jpeg" /></figure><p>But it did not last long and the next big thing for me was the configuration management via puppet about 8 or 9 years ago. Puppet was and still is such a great tool which solves a lot of problems in the modern sysadmin world. But as always new things come with new challenges. So I had to code almost the first time again after my technical schooling. OK, I must admit it was due to the puppet SDL on a very high level and a more descriptive way but it was a totally new way. You had to think about how to work on puppet with different people and teams, how you organize the code structure, where and how do you save and share it, what about versioning, code quality and all these things who come along with the new approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HJ-9kNoc8uQMyuSBxrgrkQ.jpeg" /></figure><p>Shortly after that, I became the opportunity to switch into a management role responsible for the IT infrastructure of an insurance company, what I accepted. So the technical part came over the years more and more in the background and the people and project management came in the foreground. We experimented with scrum and kanban to solve these both areas at once. And it worked very well in your team but struggled on the border to other teams. As the company was very conservative and slow this barrier could not be taken.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uFINNsYNbYuPIC3sUMyy6w.jpeg" /></figure><p>So I moved on and started as an System Architect in a big industry company. Packed with all my knowledge in tech <strong>and</strong> methods I came just in the right time as my new company is in a heavy digital transformation process and moving very fast and agile in this new direction. My mission is to automate all Linux installations and configurations in the on premise cloud and also in the public clouds as AWS and Azure. Unneeded to say that all machines have to stay compliant with the security and company guidelines. Here are really a lot of different APIs, manufactures and programming languages involved. In my team software developers and sysadmins work together very close. A lot of the coding tasks are only done by the software developers but they heavily hinge on the Sysadmins as wise versa they are from the developers. The cause is that the developers have far to less knowledge of the infrastructure behavior and the admins are often not yet able to code in that deep level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/715/1*XfWItT5WTrJgXIHOH9b3kQ.jpeg" /></figure><p>Almost another 10 years are gone since the first programming needs for Sysadmins and as the history profess that it is more and more important to be able to code. In my opinion it is almost on the verge of being to late. If you are not able to program in the future you won’t be able to do your job anymore. So I can only advice you to learn coding and that fast!</p><p>What can you do for a starting?</p><ul><li>Get an editor like <a href="https://code.visualstudio.com/">visual code</a> or <a href="https://atom.io/">atom</a></li><li>get an <a href="https://github.com/">github</a> account (but sure you already have one!)</li><li><a href="https://www.amazon.de/gp/product/B00DDZPC9S/ref=as_li_qf_sp_asin_il_tl?ie=UTF8&amp;tag=fruchtzuckera-21&amp;camp=1638&amp;creative=6742&amp;linkCode=as2&amp;creativeASIN=B00DDZPC9S&amp;linkId=efaf35d2e4a25338601c0310da729d7b">get some books</a>*</li><li>get online courses (<a href="http://shareasale.com/r.cfm?b=620905&amp;u=1634297&amp;m=53701&amp;urllink=&amp;afftrack=">pluralsight.com</a>*, <a href="https://www.udemy.com/">udemy.com</a>)</li><li>read the right sites (<a href="https://www.freecodecamp.org/">freecodecamp.org</a>)</li><li>just get started coding and learn by creating things!</li></ul><p>You have similar experience or you want to tell how you get started coding, just tell in the comments!</p><p>*this is an affiliate link</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=335a920dfb71" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get started with meteor and reactioncommerce within a vagrant box on MacOS]]></title>
            <link>https://medium.com/@dominik.bittl/how-to-get-started-with-meteor-and-reactioncommerce-within-a-vagrant-box-on-macos-771ef86c8398?source=rss-3050bc313338------2</link>
            <guid isPermaLink="false">https://medium.com/p/771ef86c8398</guid>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[reactioncommerce]]></category>
            <category><![CDATA[vagrant]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Dominik Bittl]]></dc:creator>
            <pubDate>Thu, 16 Feb 2017 17:50:54 GMT</pubDate>
            <atom:updated>2017-02-22T18:51:44.490Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>How to get started with meteor and Reaction Commerce within a vagrant box on MacOS</h3><h4>I will start at the very beginning and setup everything we need first</h4><h4>I want to give everyone a brief start, so if you have one or the other already just skip this part and go over to the more interesting things. I guess the same instructions should also work on any linux or windows system (beside choosing the right installation files…).</h4><h3>What is Reaction Commerce?</h3><p>Reaction Commerce is an open source ecommerce platform build on top of meteor JavaScript framework. It enables you to have instant updates without page reloads. And surely fits all your needs!</p><h3>Installing VirtualBox</h3><p>Go to <a href="http://virtualbox.org/wiki/Downloads">https://virtualbox.org/wiki/Downloads</a> and choose the right installation file. After downloading just open it and follow the installatioon instructions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*lj8DlRDSr_TVRAFPAqWu9Q.png" /><figcaption>Download VirtualBox and install</figcaption></figure><h3>Installing Vagrant</h3><p>Go to <a href="https://www.vagrantup.com/downloads.html">https://www.vagrantup.com/downloads.html</a>, download the right installation file, open it and follow the instructions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*p_IHAEmIeEBqseNiepB_cA.png" /><figcaption>Download Vagrant and install</figcaption></figure><h3>Setting up vagrant and getting Ubuntu Xenial run</h3><p>Now we are ready to initialize our first vagrant box and getting Ubuntu Xenial running on it. Start a terminal session, create a directory mkdir -p ~/Vagrant/ubuntu-xenial for your box, change into the directory cd ~/Vagrant/ubuntu-xenialand type vagrant init. Now edit the file “Vagrant” to have the following options like this.</p><pre>#which operating system to load<br>config.vm.box = &quot;ubuntu/xenial64&quot;</pre><pre>#configure the ram, minimum 2048 MB<br>   config.vm.provider &quot;virtualbox&quot; do |vb|<br>  #   # Display the VirtualBox GUI when booting the machine<br>  #   vb.gui = true<br>  #<br>  #   # Customize the amount of memory on the VM:<br>     vb.memory = &quot;2048&quot;<br>   end</pre><p>Let’s start now the box with vagrant up, this can last a littel time.</p><p>HINT: Beware of the actual kernel bug in Ubuntu Xenial, which could kill your processes. Just have a look at this article.</p><p><a href="https://blog.meteor.com/how-to-stop-ubuntu-xenial-from-randomly-killing-your-big-processes-4a3e2d09323f">How to stop Ubuntu Xenial from randomly killing your big processes</a></p><h3>Fulfill the prerequirements for meteor and Reaction Commerce</h3><p>In prior to get Reaction Commerce running you have to install nodejs, some build tools and meteor. Login to your newly created box with vagrant sshand do the following steps.</p><pre>#upate your repodata<br>sudo apt-get update</pre><pre>#update your system<br>sudo apt-get -u dist-upgrade</pre><pre>#install the build dependencies<br>sudo apt-get install -y --no-install-recommends build-essential \ bzip2 curl ca-certificates git graphicsmagick python</pre><pre>#install nodejs 4.x<br>sudo curl -sL <a href="https://deb.nodesource.com/setup_4.x">https://deb.nodesource.com/setup_4.x</a> | sudo -E bash -<br>sduo apt-get install -y nodejs</pre><pre>#install meteor to actual user only<br>curl <a href="https://install.meteor.com/">https://install.meteor.com/</a> | sh</pre><pre>#update meteor for eventually fixes<br>meteor update --patch</pre><pre>#install reaction-cli: the installer of Reaction Commerce<br>sudo npm install -g reaction-cli</pre><p>Let’s add this to the Vagrantfile for automation purposes.</p><pre>config.vm.provision “shell”, inline: &lt;&lt;-SHELL<br>     sudo apt-get update<br>     sudo apt-get -u dist-upgrade -y<br>     sudo apt-get install -y --no-install-recommends \ <br>     build-essential bzip2 curl ca-certificates git graphicsmagick \<br>     python<br>     sudo curl -sL <a href="https://deb.nodesource.com/setup_4.x">https://deb.nodesource.com/setup_4.x</a> | sudo -E \ <br>     bash -<br>     sudo apt-get install -y nodejs<br>     curl <a href="https://install.meteor.com/">https://install.meteor.com/</a> | sh<br>     meteor update --patch<br>     sudo npm install -g reaction-cli<br> SHELL</pre><p>Now we are ready to get Reaction Commerce up and running!</p><h3>Getting started with meteor and Reaction</h3><p>Before we start building reactioncommerce and launch it, I would like to configure a port forwaring for the vagrant box so that we can directly browse to our new created webstore . For this shutdown the box vagrant haltopen the Vagrantfile again and set the following line:</p><pre>config.vm.network &quot;forwarded_port&quot;, guest: 3000, host: 8080</pre><p>Why doing this? Because Reaction Commerce will get up on the port 3000 and I want it to listen on th eport 8080 on my localhost.</p><p>vagrant upyour box, vagrant sshinto it and do the rest of the magic withcd ~/run reaction-cli init, change the directory cd ~/reactionand start reaction reaction run.</p><pre>cd ~/<br>reaction init<br>cd ~/reaction<br>reaction run</pre><p>If all goes right, you will shortly see a console output like:</p><pre>dominik_bittl@ubuntu-xenial:~/reaction$ reaction run<br><br>Using settings file at settings/dev.settings.json<br><br>Setting up plugin imports...<br><br>Setting up style imports...<br><br>[[[[[ ~/reaction ]]]]]<br><br>=&gt; Started proxy.<br>=&gt; A patch (Meteor 1.4.2.7) for your current release is available!<br>   Update this project now with &#39;meteor update --patch&#39;.<br>=&gt; Started MongoDB.<br>cfs:gridfs: updating npm dependencies -- mongodb, gridfs-stream...<br>17:07:11.674Z  INFO Reaction: Load default data from /private/data/<br>17:07:12.982Z  INFO Reaction: JobServer started<br>17:07:12.992Z  WARN Reaction: Skipped loading settings from reaction.json.<br>17:07:22.333Z  INFO Reaction: Using meteor --settings to create admin user<br>17:07:24.977Z  WARN Reaction:<br>  <br>   *********************************<br>          <br>    IMPORTANT! DEFAULT ADMIN INFO<br>          <br>    EMAIL/LOGIN: xxxxxxxx@localhost<br>          <br>    PASSWORD: xx_XXXXX<br>          <br>   ********************************* <br>  <br>  <br>17:07:25.045Z  INFO Reaction: Migrating from version 0 -&gt; 2<br>17:07:25.046Z  INFO Reaction: Running up() on version 1<br>17:07:25.141Z  INFO Reaction: Running up() on version 2<br>17:07:25.180Z  INFO Reaction: Finished migrating.<br>17:07:25.280Z  WARN Reaction: OpenExchangeRates API not configured. Not adding fetchRates job<br>17:07:25.286Z  WARN Reaction: OpenExchangeRates API not configured. Not adding flushRates job<br>17:07:25.644Z  INFO Reaction: Reaction initialization finished.<br>=&gt; Started your app.<br><br>=&gt; App running at: http://localhost:3000/<br>17:07:54.251Z  INFO Reaction: ProductSearch collection (re)built successfully.</pre><p>Now open your browser and visit <a href="http://localhost:8080/">http://localhost:8080</a> and you will see your shop. If you want to get admin on the site login as customer with the credentials of your cosole output.</p><h3>Setting up Synced Folders</h3><p>At last we are setting up “Synced Folders”, so you can use your favourite Code-Editor on your local machine and change files without the need to login to your virtual host machine.</p><p>Add e.g. the following lines to your vagrant config.</p><pre>Vagrant.configure(“2”) do |config|<br> # other config here</pre><pre>config.vm.synced_folder “~/dev/reaction/”, “/home/vagrant/reaction”<br>end</pre><p>~/dev/reaction is on your local machine (you can create it with mkdir -p ~/dev/reaction) and it will show the files of the directoy /home/vagrant/reactionof the virtual box.</p><h3>Conclusion</h3><p>You can see that it easy and fast to install your first Reaction Commerce shopping site. And overall it is a lot of fun! :-)</p><p>One more thing:</p><p>You could also package your Vagrant box for reusing it if you want. Mostly I personally like it to get things done fresh, so it is up to you how you like it.</p><pre>#create the package of your box (I like to version it)<br>vagrant package — output ubuntu-xenial-reactioncommerce-v1.0.box<br>#create a place for storing your boxes<br>mkdir -p ~/Vagrant/boxes<br>#move your box into that place<br>mv ubuntu-xenial-reactioncommerce-v1.0.box ~/Vagrant/boxes<br>#initialize the box when ever you like<br>vagrant init ubuntu-xenial-reactioncommerce \ file:~/Vagrant/boxes/ubuntu-xenial-reactioncommerce-v1.0.box</pre><p>Here you can download the Vagrantfile, all packed together and easy to use: <a href="https://github.com/domi-nik-/VagrantExample">https://github.com/domi-nik-/VagrantExample</a></p><h3>My setup as writing this article</h3><ul><li>MacBook Pro: Mid 2009 with 8GB RAM</li><li>MacOS: v10.11.6</li><li>VirtualBox : v5.1.14</li><li>Vagrant: v1.9.1</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=771ef86c8398" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I came to meteor and reactioncommerce]]></title>
            <link>https://medium.com/@dominik.bittl/how-i-came-to-meteor-and-reactioncommerce-de380acec4c1?source=rss-3050bc313338------2</link>
            <guid isPermaLink="false">https://medium.com/p/de380acec4c1</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[mongodb]]></category>
            <category><![CDATA[reactioncommerce]]></category>
            <category><![CDATA[meteor]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Dominik Bittl]]></dc:creator>
            <pubDate>Thu, 16 Feb 2017 17:49:40 GMT</pubDate>
            <atom:updated>2017-02-16T17:49:40.467Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h4>Just a short story of mine</h4><p>As I am running an ecommerce business for quite some time now and was no more satisfied by my current shop solution (wp and woocommerce) I decided to search for an alternative.</p><p>Around the same time my interest in programming nodejs started. And it seems like I was not alone, as you can see when you have a look at the github statistics (1*). Javascript is getting more and more popular. So why not giving a try?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*gpvWzPJNkA1hrYmTzwBPSQ.png" /></figure><p>First I bought a book about the MEAN Stack (<a href="https://www.mongodb.com/">Mongo</a> <a href="http://expressjs.com/">Express</a> <a href="https://angularjs.org/">Angular</a> <a href="https://nodejs.org/">Node</a>) and felt quite confident after a short time. Although I’m a sysadmin and not a programmer it is for me very readable and easy understandable so far.</p><p>I really liked it and I still do!</p><p>But sure I did not want to write my own shopping solution and googled for an existing project which led me to <a href="https://reactioncommerce.com/">reactioncommerce</a> and so to <a href="https://www.meteor.com/">meteor</a>, which totaly match my favourite technologies.</p><p>As I told you that I am mainly a sydadmin I will show you how to get the things up and running.</p><p>Read my next article “How to get started with meteor and reactioncommerce within an vagrant box on MacOS”</p><p>1*: <a href="https://github.com/blog/2047-language-trends-on-github">https://github.com/blog/2047-language-trends-on-github</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de380acec4c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>