<story><title>Managing my personnal servers in 2020 with K3s</title><url>https://github.com/erebe/personal-server/blob/master/README.md</url></story><parent_chain><item><author>dsr_</author><text>I&amp;#x27;m not deploying; this is &lt;i&gt;&lt;/i&gt;the server&lt;i&gt;&lt;/i&gt;. I do backups, and I keep config in git.&lt;p&gt;Reproducibility? This is &lt;i&gt;&lt;/i&gt;the server&lt;i&gt;&lt;/i&gt;. I will restore from backups. There is no point in scaling.&lt;p&gt;If you want to argue that containerization and VMs are portable and deployable and all that, I agree. This is not a reasonable place to do that extra work.</text></item><item><author>gavinray</author><text>Containerization and container orchestration platforms are only partly about scalability.&lt;p&gt;The primary appeal for me is ease of deployment and reproducibility. This is why I develop everything in Docker Compose locally.&lt;p&gt;Maybe the equivalent here would be something like Guix or Nix for declaratively writing the entire state of all the desired system packages and services + versions but honestly (without personal experience using these) they seem harder than containers.</text></item><item><author>dsr_</author><text>&amp;quot;When you try to CRAM everything (mail, webserver, gitlab, pop3, imap, torrent, owncloud, munin, ...) into a single machine on Debian, you ultimately end-up activating unstable repository to get the latest version of packages and end-up with conflicting versions between softwares to the point that doing an apt-get update &amp;amp;&amp;amp; apt-get upgrade is now your nemesis.&amp;quot;&lt;p&gt;This is not my experience.&lt;p&gt;My main house server runs:&lt;p&gt;mail: postfix, dovecot, clamav (SMTP, IMAP)&lt;p&gt;web: nginx, certbot, pelican, smokeping, dokuwiki, ubooquity, rainloop, privoxy  (personal pages, blog, traffic tracking, wiki, comic-book server, webmail, anti-ad proxy)&lt;p&gt;git, postgresql, UPS monitoring, NTP, DNS, and DHCPd.&lt;p&gt;Firewalling, more DNS and the other part of DHCPd failover is on the router.&lt;p&gt;Package update is a breeze. The only time I waste the overhead of a virtual machine is when I&amp;#x27;m testing out new configurations and don&amp;#x27;t want to break what I have.&lt;p&gt;&amp;quot;just having the Kubernetes server components running add a 10% CPU on my Intel(R) Atom(TM) CPU C2338 @ 1.74GHz.&amp;quot;&lt;p&gt;Containerization is not a win here. Where&amp;#x27;s the second machine to fail over to?</text></item></parent_chain><comment><author>lmilcin</author><text>Hey, do whatever floats your boat. Nobody said there is a single solution to every problem.&lt;p&gt;Don&amp;#x27;t pick up a fight because you are satisfied with &lt;i&gt;your&lt;/i&gt; solution that is different from somebody else&amp;#x27;s solution.&lt;p&gt;I personally like docker-compose and Vagrant for my private services and development environments.&lt;p&gt;I use Vagrant for when I need a complete VM. Think in terms of VM for doing embedded development where I need a large number of tools in very specific versions and I need them still working in 3 years without maintenance even if I change a lot about my PC setup (I run Linux &lt;i&gt;everywhere&lt;/i&gt;).&lt;p&gt;I create separate Vagrant for every project and this way I can reinstate complete environment at a moments notice, whenever I want.&lt;p&gt;I use docker-compose for most everything else. Work on an application that needs MongoDB, Kafka, InfluxDB, Graphana and so on and so forth? Docker Compose to rule them all. You type one command and everything&amp;#x27;s up. You type another and everything&amp;#x27;s down.&lt;p&gt;I use the same for my other services like mail, NAS, personal website, database, block storage, etc. Containers let me preserve the environment and switch between versions easily and I am not tied to the binary version of the Linux on the server.&lt;p&gt;I hate it when I run a huge amount of services and then a single upgrade causes some of them to stop working. I want to be able to be constantly updated and have my services working with minimum maintenance. Containers let me make decision on each of the services separately.</text></comment>
<story><title>Managing my personnal servers in 2020 with K3s</title><url>https://github.com/erebe/personal-server/blob/master/README.md</url></story><parent_chain><item><author>dsr_</author><text>I&amp;#x27;m not deploying; this is &lt;i&gt;&lt;/i&gt;the server&lt;i&gt;&lt;/i&gt;. I do backups, and I keep config in git.&lt;p&gt;Reproducibility? This is &lt;i&gt;&lt;/i&gt;the server&lt;i&gt;&lt;/i&gt;. I will restore from backups. There is no point in scaling.&lt;p&gt;If you want to argue that containerization and VMs are portable and deployable and all that, I agree. This is not a reasonable place to do that extra work.</text></item><item><author>gavinray</author><text>Containerization and container orchestration platforms are only partly about scalability.&lt;p&gt;The primary appeal for me is ease of deployment and reproducibility. This is why I develop everything in Docker Compose locally.&lt;p&gt;Maybe the equivalent here would be something like Guix or Nix for declaratively writing the entire state of all the desired system packages and services + versions but honestly (without personal experience using these) they seem harder than containers.</text></item><item><author>dsr_</author><text>&amp;quot;When you try to CRAM everything (mail, webserver, gitlab, pop3, imap, torrent, owncloud, munin, ...) into a single machine on Debian, you ultimately end-up activating unstable repository to get the latest version of packages and end-up with conflicting versions between softwares to the point that doing an apt-get update &amp;amp;&amp;amp; apt-get upgrade is now your nemesis.&amp;quot;&lt;p&gt;This is not my experience.&lt;p&gt;My main house server runs:&lt;p&gt;mail: postfix, dovecot, clamav (SMTP, IMAP)&lt;p&gt;web: nginx, certbot, pelican, smokeping, dokuwiki, ubooquity, rainloop, privoxy  (personal pages, blog, traffic tracking, wiki, comic-book server, webmail, anti-ad proxy)&lt;p&gt;git, postgresql, UPS monitoring, NTP, DNS, and DHCPd.&lt;p&gt;Firewalling, more DNS and the other part of DHCPd failover is on the router.&lt;p&gt;Package update is a breeze. The only time I waste the overhead of a virtual machine is when I&amp;#x27;m testing out new configurations and don&amp;#x27;t want to break what I have.&lt;p&gt;&amp;quot;just having the Kubernetes server components running add a 10% CPU on my Intel(R) Atom(TM) CPU C2338 @ 1.74GHz.&amp;quot;&lt;p&gt;Containerization is not a win here. Where&amp;#x27;s the second machine to fail over to?</text></item></parent_chain><comment><author>coldtea</author><text>&amp;gt;&lt;i&gt;I&amp;#x27;m not deploying; this is the server.&lt;/i&gt;&lt;p&gt;Err, that&amp;#x27;s the very definition of deploying. Putting stuff on &amp;quot;the server&amp;quot;.&lt;p&gt;What you mean is not that you&amp;#x27;re not deploying, you&amp;#x27;re not testing&amp;#x2F;staging -- you change things and test new stuff directly in your production server.</text></comment>