<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Debian on Miek Gieben</title>
    <link>https://miek.nl/tags/debian/</link>
    <description>Recent content in Debian on Miek Gieben</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© Copyright 2007-2024 Miek Gieben</copyright>
    <lastBuildDate>Sun, 10 Sep 2023 11:20:31 +0200</lastBuildDate>
    <atom:link href="https://miek.nl/tags/debian/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Nvim Debian Pkg</title>
      <link>https://miek.nl/2023/september/10/nvim-debian-pkg/</link>
      <pubDate>Sun, 10 Sep 2023 11:20:31 +0200</pubDate>
      <guid>https://miek.nl/2023/september/10/nvim-debian-pkg/</guid>
      <description>&lt;p&gt;NVIM stopped making Debian packages a while back, so here is a short note on how to&#xA;do this yourself. Had a hard time finding this info, hence reproduced here. Assuming you&amp;rsquo;ve&#xA;got the source.&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;code&gt;make CMAKE_BUILD_TYPE=Release&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;cd build &amp;amp;&amp;amp; cpack -G DEB&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;code&gt;sudo dpkg -i nvim-linux64.deb&lt;/code&gt;&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;&amp;hellip; and of course you then find the &lt;a href=&#34;https://github.com/neovim/neovim/wiki/Building-Neovim#quick-start&#34;&gt;authoritative&#xA;text&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;If you use &lt;code&gt;RelWithDebInfo&lt;/code&gt; an ever growing log file will be created in &lt;code&gt;~/.local/state/nvim/log&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Provisioning K3s and systemk</title>
      <link>https://miek.nl/2021/january/17/provisioning-k3s-and-systemk/</link>
      <pubDate>Sun, 17 Jan 2021 10:38:37 +0000</pubDate>
      <guid>https://miek.nl/2021/january/17/provisioning-k3s-and-systemk/</guid>
      <description>&lt;p&gt;Due to a previous job I&amp;rsquo;m calling &lt;em&gt;nodes&lt;/em&gt;, &amp;ldquo;machines&amp;rdquo;, also because this is about systemk, it&amp;rsquo;s more&#xA;likely you are actually using a real machine. So I&amp;rsquo;ll keep on using &amp;ldquo;machines&amp;rdquo; in this post.&lt;/p&gt;&#xA;&lt;p&gt;First up: I needed an easy way to build packages of the software I&amp;rsquo;m using. For this I&amp;rsquo;ve setup a&#xA;small CI using GitHub workflows that builds Debian packages for me: &lt;a href=&#34;https://github.com/miekg/debian&#34;&gt;https://github.com/miekg/debian&lt;/a&gt;.&#xA;(A Debian package repository would even be better, so I can more easily do upgrades).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Kubernetes Control Plane for Debian?</title>
      <link>https://miek.nl/2020/november/12/kubernetes-control-plane-for-debian/</link>
      <pubDate>Thu, 12 Nov 2020 07:38:37 +0000</pubDate>
      <guid>https://miek.nl/2020/november/12/kubernetes-control-plane-for-debian/</guid>
      <description>&lt;p&gt;The everything is a object in Kubernetes is a very nice abstraction. The ability to influence it&#xA;with just &lt;code&gt;kubectl&lt;/code&gt; makes for only one control plane (to learn).&lt;/p&gt;&#xA;&lt;p&gt;The networking, ingress, discovery, installation, etc. are all not that great. So I&amp;rsquo;m pondering&#xA;marrying the things I love: have a plain Debian system, &amp;ldquo;normal&amp;rdquo; networking (no&#xA;overlay/underlay/whatever), Debian packages, etc. &lt;em&gt;And&lt;/em&gt; controlling it all via kubectl.&lt;/p&gt;&#xA;&lt;p&gt;This should include a sane installation and allow for rollbacks. Metrics and observability should be&#xA;supported, but will probably be more of the same (install the binaries and push configuration =&#xA;k8s objects).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
