Marco Kamner

Given the recent rise in text-based language models, sometimes called AI tools, I wanted to share my thoughts and experiences in using them, especially in the context of blogging.

[Read More]

Now that we have talked about the benefits of running your own server and how to run your own server let’s take a look at some things you could run on your own personal server and some things you should better not. Host a code-server code-server is an open-source application that allows you to run VSCode on your server and access it from any browser. It’s perfect for taking notes or journaling from anywhere, as you can access it from any device with a browser. [Read More]

There are many ways to run your own server, from setting up a Raspberry Pi on your desk to renting a physical server at a provider.

In this post, we will focus on setting up a virtual server with DigitalOcean, which is one of the easiest ways to get started.

[Read More]

In the world of technology, we are moving further and further away from operating directly on servers, but there are still significant benefits to be gained from running a personal server.

I have been running some kind of personal server for many years now and I strongly believe anyone working in technology can benefit greatly from doing so. Here’s why:

[Read More]

In this post I will go over the MVP building phase of Honeypot Login, from idea to launched product and what my next steps will be.

[Read More]

Things I do to be a good code reviewee.

[Read More]

Setting up a new repository for YAML linting today I was running in a bit of an issue with yamllint. I was using a YAML list to specify ingores, as mentioned in the documentation: ignore: - "*.dont-lint-me.yaml" - "/bin/" - "!/bin/*.lint-me-anyway.yaml" This however did not work with the above mentioned error message. After a lot of debugging I found that they released a new version recently which introduced this feature. [Read More]

A simple Python client to interact with ArgoCD.

[Read More]

The problem

If you use ssh-agent with an encrypted ssh key it does not persist when you open a new terminal window.

The solution

Use keychain instead.

1. Install

   sudo apt install keychain
   

2. Add to your shells rc file, eg. .bashrc or .zshrc

   # Repeat this line for all keys you want to unlock and use this way
   /usr/bin/keychain -q --nogui $HOME/.ssh/id_rsa
   source $HOME/.keychain/wsl-sh
   

3. Unlock your keys on shell startup and enjoy

Running any kind of personal infrastructure sometimes requires your attention based on certain events or failure states, no matter how much you automate tasks.

Over the years I have used E-Mail, Telegram bots and a variety of other tools for this purpose. However all of them have the drawback that they mix with other kinds of information and are not easilly usable in scripts.

[Read More]