<?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 Rudiyanto Golife on Medium]]></title>
        <description><![CDATA[Stories by Rudiyanto Golife on Medium]]></description>
        <link>https://medium.com/@rudi.yanto?source=rss-48c4109ea2f8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Td2-8jV2Am_4e1SG</url>
            <title>Stories by Rudiyanto Golife on Medium</title>
            <link>https://medium.com/@rudi.yanto?source=rss-48c4109ea2f8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 14:48:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rudi.yanto/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[Modern Way Devops with CI]]></title>
            <link>https://medium.com/@rudi.yanto/modern-way-devops-with-ci-4999c4ea97e3?source=rss-48c4109ea2f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4999c4ea97e3</guid>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Rudiyanto Golife]]></dc:creator>
            <pubDate>Sun, 07 Apr 2019 01:38:41 GMT</pubDate>
            <atom:updated>2019-04-07T15:38:14.252Z</atom:updated>
            <content:encoded><![CDATA[<h3>CI in DevOps Way</h3><p>Some of you might hear of DevOps. <strong>DevOps is a culture</strong>, not a role!</p><blockquote>DevOps is a software development approach which involves continuous development, continuous testing, continuous integration, continuous deployment, and continuous monitoring of the software throughout its development life cycle.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xpK-237jQFKGUOTEnVaR6w.png" /></figure><p>Writing code is just one piece in the grand scheme of software development.</p><p>Software development evolves day by day and working with CI is one of the pillars of modern software development and the backbone of the modern DevOps Environment.</p><h3>What is Continuous Integration (CI)?</h3><p>Continuous Integration is a development methodology that involves frequent integration of code into a shared repository. Continuous Integration is essentially the repetition of the integration step with a high frequency to alleviate its pain, which is it has allowed us to solve a lot of problem that we used to deal with earlier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*4dEWHLfVDQIFlwykC81GNw.png" /></figure><p>The key goals of continuous integration are:</p><blockquote>Improve Developer Productivity</blockquote><p>Continuous integration helps your team be more productive by freeing developers from manual tasks (automated build) and encouraging behaviors that help reduce the number of errors and bugs released to customers.</p><blockquote>Find and Address Bugs Quicker</blockquote><p>With more frequent testing and slices the testing period into many periods where each feature is merged, your team can discover and address bugs earlier before they grow into larger problems laters.</p><blockquote>Deliver Updates Faster</blockquote><p>Continuous integration helps your team deliver updates to their customers faster and more frequently.</p><p>Delivery quality software quickly and efficiently isn’t easy, so it is important that developers have systems that support them, one of them is Continuous Integration (CI).</p><p>Source: <em>https://aws.amazon.com/devops/continuous-integration/</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4999c4ea97e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Working On with Vagrant]]></title>
            <link>https://medium.com/@rudi.yanto/working-on-with-vagrant-11dc709f485e?source=rss-48c4109ea2f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/11dc709f485e</guid>
            <category><![CDATA[vagrant]]></category>
            <dc:creator><![CDATA[Rudiyanto Golife]]></dc:creator>
            <pubDate>Wed, 03 Apr 2019 17:52:09 GMT</pubDate>
            <atom:updated>2019-04-03T17:59:23.918Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*AMiRYSmT6qxf2_Qurd4oHA.png" /></figure><h3><strong>What is Vagrant?</strong></h3><blockquote>Vagrant is a tool for managing virtual machines — Mitchell Hashimoto</blockquote><p>Vagrant can be installed by downloading from <a href="https://www.vagrantup.com/downloads.html">here</a>.</p><p>With Vagrant you can lowers the environment project setup time (by automation), minimize bug on production and increase development productivity.</p><h3>how we get started with Vagrant?</h3><p>after you already have installed it, you can download the box which is an base images in Vagrant from <a href="https://app.vagrantup.com/boxes/search">here</a>.</p><p>I’ll download the box named “<a href="https://app.vagrantup.com/ubuntu/boxes/xenial64"><em>ubuntu/xenial64</em></a>” and the one we’ll be using.</p><p>First, we should adding a box file that was downloaded in our directory by:</p><pre>vagrant box add xenial-server-cloudimg-amd64-vagrant.box — name=ubuntu</pre><p>and now, we can <em>initialize</em> unpacking box (ubuntu) in our virtual machines by</p><pre>vagrant init ubuntu</pre><p>After that, boot our first vagrant environment with</p><pre><em>vagrant up</em></pre><p>After vagrant runs in the virtual machine, you can SSH into the machine by do</p><pre>vagrant ssh</pre><blockquote>and now, you can do anything you want in your machine. The SSH session can be terminated with CTRL+D or typing exit. Note that your guest machine is still running. Open Virtual UI to see it.</blockquote><h3>Some others useful commands you should know:</h3><p><strong><em>Show list of all boxes added:</em></strong></p><pre>vagrant box list</pre><p><strong><em>remove vagrant box:</em></strong></p><pre>vagrant box remove &lt;box name&gt;</pre><p><strong><em>refresh/restart vagrant file (if you make any changes with the configuration vagrantFile)</em></strong></p><pre>vagrant reload</pre><p><strong><em>suspend vagrant state (it will resume your work):</em></strong></p><pre>vagrant suspend</pre><p>s<strong><em>top/shutdown vagrant running in machine:</em></strong></p><pre>vagrant halt</pre><p><strong><em>remove vagrant from your machine:</em></strong></p><pre>vagrant destroy</pre><h3>how to setting up Vagrant?</h3><p>after you run command vagrant init, it’ll generate <strong><em>VagrantFile</em></strong>, which it will be using for configure your project to use it as a base. When you open your <strong><em>vagrantFile</em></strong>, you’ll see:</p><pre>Vagrant.configure(“2”) do |config|</pre><pre>  config.vm.box = “ubuntu”</pre><pre>end</pre><blockquote>in this context, vagrant will using the ubuntu box by the box we was added before. If the box not added, Vagrant’ll automatically download and add the box when it is run.</blockquote><p>You can add explicit version of a box your are using by <strong>config.vm.box_version, </strong>like:</p><pre>Vagrant.<strong>configure</strong>(“2”) <strong>do</strong> <strong>|</strong>config<strong>|</strong></pre><pre>  config.<strong>vm</strong>.<strong>box</strong> <strong>=</strong> “ubuntu”</pre><pre>  config.<strong>vm</strong>.<strong>box_version</strong> <strong>=</strong> “1.0.0”</pre><pre><strong>end</strong></pre><p>Also with specify the URL to a box directly using <strong>config.vm.box_url</strong>,</p><pre>Vagrant.<strong>configure</strong>(“2”) <strong>do</strong> <strong>|</strong>config<strong>|</strong></pre><pre>  config.<strong>vm</strong>.<strong>box</strong> <strong>=</strong> “ubuntu”</pre><pre>  config.<strong>vm</strong>.<strong>box_version</strong> <strong>=</strong> “1.0.0”</pre><pre>  config.<strong>vm</strong>.<strong>box_url</strong> <strong>=</strong> “<a href="https://app.vagrantup.com/ubuntu/boxes/xenial64">https://app.vagrantup.com/ubuntu/boxes/xenial64</a>“</pre><pre><strong>end</strong></pre><p>By default, vagrant synced your directory vagrant folder on host machine in <strong><em>/vagrant</em></strong> on guest machine. if you want to change the synced folder with you other directory, you can use <strong>config.vm.synced_folder</strong>,</p><pre>Vagrant.<strong>configure</strong>(“2”) <strong>do</strong> <strong>|</strong>config<strong>|</strong></pre><pre>  config.<strong>vm</strong>.<strong>box</strong> <strong>=</strong> “ubuntu”</pre><pre>  config.<strong>vm</strong>.<strong>box_version</strong> <strong>=</strong> “1.0.0”</pre><pre>  config.<strong>vm</strong>.<strong>box_url</strong> <strong>=</strong> “<a href="https://app.vagrantup.com/ubuntu/boxes/xenial64">https://app.vagrantup.com/ubuntu/boxes/xenial64</a> “</pre><pre>  config.<strong>vm</strong>.<strong>synced_folder</strong> “src/”, “/srv/website”</pre><pre><strong>end</strong></pre><blockquote>note: the <strong>first parameter</strong> is a path of directory on the host machine and the <strong>second one</strong> is a path on the guest machine. The synced folder won’t be automatically reload, you have to boot the vagrant (<strong>vagrant up</strong>) or just refresh vagrant file when it still running (<strong>vagrant reload</strong>)</blockquote><p>On the other hand, you can disabled synced_folder by adding <strong>disable</strong> props :</p><pre>config.<strong>vm</strong>.<strong>synced_folder</strong> “.”, “/vagrant”, disabled: <strong>true</strong></pre><p>Vagrant can do automate the setup environment with <strong>provisioning</strong>. We can create a<em> shell script</em> to define what we want to install when booting the vagrant. For example, I was created a new <strong><em>setup.sh</em></strong> file and add a command for install <strong><em>apache :</em></strong></p><pre><em>#setup.sh</em></pre><pre>apt-get update</pre><pre>apt-get install -y apache2</pre><p>Next, we configure Vagrant to run this shell script when setting up our machine use <strong>config.vm.provision:</strong></p><pre>Vagrant.<strong>configure</strong>(“2”) <strong>do</strong> <strong>|</strong>config<strong>|</strong></pre><pre>  config.<strong>vm</strong>.<strong>box</strong> <strong>=</strong> “ubuntu”</pre><pre>  config.<strong>vm</strong>.<strong>box_version</strong> <strong>=</strong> “1.0.0”</pre><pre>  config.<strong>vm</strong>.<strong>box_url</strong> <strong>=</strong> “<a href="https://app.vagrantup.com/ubuntu/boxes/xenial64">https://app.vagrantup.com/ubuntu/boxes/xenial64</a> “</pre><pre>  config.<strong>vm</strong>.<strong>synced_folder</strong> “src/”, “/srv/website”</pre><pre>  config.<strong>vm</strong>.<strong>provision</strong> :shell, path: “setup.sh”</pre><pre><strong>end</strong></pre><blockquote><strong>note: </strong>The file path (<strong>setup.sh</strong>) is relative to the location of the project root (where the <strong>Vagrantfile</strong> is located).</blockquote><p>If the guest machine is already running from a previous step, refresh your machine by</p><pre><strong>vagrant reload --</strong>provision</pre><blockquote>which will quickly restart your virtual machine. The provision flag on the reload command instructs Vagrant to run the provisioners, since usually Vagrant will only do this on the first <strong>vagrant up</strong>.</blockquote><p>In this blog post, I only scratched the surface of step by step how to using Vagrant as there are so many use cases and features it can be applied to.</p><p>To be continue~</p><p><em>references : </em><a href="https://www.vagrantup.com/intro/getting-started/index.html"><em>https://www.vagrantup.com</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11dc709f485e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>