<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Devops on Klaus Hebsgaard</title><link>https://khebbie.dk/tags/devops/</link><description>Recent content in Devops on Klaus Hebsgaard</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 21 Oct 2017 00:00:00 +0000</lastBuildDate><atom:link href="https://khebbie.dk/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker vs binary packages</title><link>https://khebbie.dk/posts/docker-vs-binary-packages/</link><pubDate>Sat, 21 Oct 2017 00:00:00 +0000</pubDate><guid>https://khebbie.dk/posts/docker-vs-binary-packages/</guid><description>&lt;hr&gt;
&lt;img src="https://images.unsplash.com/photo-1581092919530-0583a3a8216e?auto=format&amp;fit=crop&amp;w=1600&amp;q=80" alt="Container ship representing Docker containers" width="1600" height="1067" loading="lazy"&gt;
&lt;p&gt;&lt;em&gt;Published: Oct 21, 2017&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;The other day I had a conversation with a Operations Engineer who made a bold statement: &amp;ldquo;Sending us a docker container is not different from sending us a .deb package&amp;rdquo;&lt;br&gt;
I do not agree with that statement at all but didn&amp;rsquo;t have the time to counter it, so instead I will write this blog post.&lt;/p&gt;
&lt;p&gt;So what really is the difference between a deb package and a docker container?&lt;br&gt;
Just a sidenote that .deb is just one example of a binary package, rpms and packages for other linux systems, could be another example. And I suppose the Windows term would be a msi package.&lt;/p&gt;</description></item><item><title>Docker vs binary packages</title><link>https://khebbie.dk/posts-pages/docker-vs-binary-packages/</link><pubDate>Sat, 21 Oct 2017 00:00:00 +0000</pubDate><guid>https://khebbie.dk/posts-pages/docker-vs-binary-packages/</guid><description>&lt;h1 id="docker-vs-binary-packages"&gt;Docker vs binary packages&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;Published: Oct 21, 2017&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Source: &lt;a href="https://khebbie.dk/docker-vs-binary-packages/"&gt;https://khebbie.dk/docker-vs-binary-packages/&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;The other day I had a conversation with a Operations Engineer who made a bold statement: &amp;ldquo;Sending us a docker container is not different from sending us a .deb package&amp;rdquo;&lt;br&gt;
I do not agree with that statement at all but didn&amp;rsquo;t have the time to counter it, so instead I will write this blog post.&lt;/p&gt;
&lt;p&gt;So what really is the difference between a deb package and a docker container?&lt;br&gt;
Just a sidenote that .deb is just one example of a binary package, rpms and packages for other linux systems, could be another example. And I suppose the Windows term would be a msi package.&lt;/p&gt;</description></item><item><title>Heroku like deployment for your cloud host / VPS</title><link>https://khebbie.dk/posts/heroku-like-deployment-for-your-cloud-host/</link><pubDate>Mon, 12 May 2014 00:00:00 +0000</pubDate><guid>https://khebbie.dk/posts/heroku-like-deployment-for-your-cloud-host/</guid><description>&lt;p&gt;&lt;em&gt;Published: May 12, 2014&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;img src="https://images.unsplash.com/photo-1555949963-aa79dcee981c?auto=format&amp;fit=crop&amp;w=1600&amp;q=80" alt="Cloud server infrastructure representing Heroku deployment environment" width="1600" height="1067" loading="lazy"&gt;
For [Be My Eyes](http://www.bemyeyes.org) I have set up a heroku like deployment environment
&lt;p&gt;Basically I followed this approach:&lt;br&gt;
&lt;a href="https://www.digitalocean.com/community/articles/how-to-set-up-automatic-deployment-with-git-with-a-vps"&gt;https://www.digitalocean.com/community/articles/how-to-set-up-automatic-deployment-with-git-with-a-vps&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;But there is one problem with the above approach, and that is that I want to be able to push other branches than master to the server. Thats how I push to QA and staging.&lt;br&gt;
A gooogle search found this for me:&lt;br&gt;
&lt;a href="https://coderwall.com/p/oj5smw"&gt;https://coderwall.com/p/oj5smw&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Heroku like deployment for your cloud host / VPS</title><link>https://khebbie.dk/posts/heroku-like-deployment-for-your-cloud-host/</link><pubDate>Mon, 12 May 2014 00:00:00 +0000</pubDate><guid>https://khebbie.dk/posts/heroku-like-deployment-for-your-cloud-host/</guid><description>&lt;p&gt;&lt;em&gt;Published: May 12, 2014&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;img alt="Cloud server infrastructure representing Heroku deployment environment" loading="lazy" src="https://images.unsplash.com/photo-1555949963-aa79dcee981c?auto=format&amp;fit=crop&amp;w=1600&amp;q=80"&gt;&lt;br&gt;
For &lt;a href="http://www.bemyeyes.org"&gt;Be My Eyes&lt;/a&gt; I have set up a heroku like deployment environment&lt;/p&gt;
&lt;p&gt;Basically I followed this approach:&lt;br&gt;
&lt;a href="https://www.digitalocean.com/community/articles/how-to-set-up-automatic-deployment-with-git-with-a-vps"&gt;https://www.digitalocean.com/community/articles/how-to-set-up-automatic-deployment-with-git-with-a-vps&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;But there is one problem with the above approach, and that is that I want to be able to push other branches than master to the server. Thats how I push to QA and staging.&lt;br&gt;
A gooogle search found this for me:&lt;br&gt;
&lt;a href="https://coderwall.com/p/oj5smw"&gt;https://coderwall.com/p/oj5smw&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>